[fix](routine-load) fix routine load pause when Kafka data deleted after TTL (#37288) #37983
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pick (#37288)
When using routine load, After the data load is completed, the lag is still a positive number:
and the routing load is paused when the Kafka data reaches TTL and is deleted, the error is
out of range
.The reason why this happened is EOF has it offset which needed statistics.
note(important):
After the bug is fixed, if you set
in your routine load job, it will meet the problem. For EOF has offset, and the config is true in Doris default.