[fix](routine-load) fix routine load pause when Kafka data deleted after TTL #37288
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 39569 ms |
TPC-DS: Total hot run time: 170548 ms |
ClickBench: Total hot run time: 30.76 s |
|
PR approved by at least one committer and no changes requested. |
github-actions
bot
added
the
approved
|
PR approved by anyone and no changes requested. |
yiguolei
pushed a commit
that referenced
this pull request
Jul 17, 2024
…ter TTL (#37288) (#37983) pick (#37288) When using routine load, After the data load is completed, the lag is still a positive number: ``` Lag: {"0":16,"1":15,"2":16,"3":16,"4":16,"5":16,"6":15,"7":16,"8":16,"9":16,"10":15,"11":16,"12":15,"13":15,"14":16,"15":16,"16":17,"17":15,"18":16,"19":15,"20":16,"21":16,"22":16,"23":16,"24":15,"25":17,"26":17,"27":16,"28":16,"29":16,"30":16,"31":17,"32":14,"33":16,"34":17,"35":16,"36":15,"37":15,"38":15,"39":16,"40":16,"41":16,"42":15,"43":15,"44":17,"45":16,"46":15,"47":15,"48":16,"49":17,"50":16,"51":15,"52":16,"53":15,"54":15,"55":17,"56":16,"57":17,"58":16,"59":16,"60":15,"61":15,"62":16,"63":16,"64":17,"65":16,"66":15,"67":16,"68":17,"69":16,"70":15,"71":17} ``` 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 ``` "property.enable.partition.eof" = "false" ``` in your routine load job, it will meet the problem. For EOF has offset, and the config is true in Doris default.
dataroaring
pushed a commit
that referenced
this pull request
Jul 17, 2024
…ter TTL (#37288) When using routine load, After the data load is completed, the lag is still a positive number: ``` Lag: {"0":16,"1":15,"2":16,"3":16,"4":16,"5":16,"6":15,"7":16,"8":16,"9":16,"10":15,"11":16,"12":15,"13":15,"14":16,"15":16,"16":17,"17":15,"18":16,"19":15,"20":16,"21":16,"22":16,"23":16,"24":15,"25":17,"26":17,"27":16,"28":16,"29":16,"30":16,"31":17,"32":14,"33":16,"34":17,"35":16,"36":15,"37":15,"38":15,"39":16,"40":16,"41":16,"42":15,"43":15,"44":17,"45":16,"46":15,"47":15,"48":16,"49":17,"50":16,"51":15,"52":16,"53":15,"54":15,"55":17,"56":16,"57":17,"58":16,"59":16,"60":15,"61":15,"62":16,"63":16,"64":17,"65":16,"66":15,"67":16,"68":17,"69":16,"70":15,"71":17} ``` 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 ``` "property.enable.partition.eof" = "false" ``` in your routine load job, it will meet the problem. For EOF has offset, and the config is true in Doris default.
dataroaring
pushed a commit
that referenced
this pull request
Aug 11, 2024
…ter TTL(#37288) (#39183) pick (#37288) When using routine load, After the data load is completed, the lag is still a positive number: ``` Lag: {"0":16,"1":15,"2":16,"3":16,"4":16,"5":16,"6":15,"7":16,"8":16,"9":16,"10":15,"11":16,"12":15,"13":15,"14":16,"15":16,"16":17,"17":15,"18":16,"19":15,"20":16,"21":16,"22":16,"23":16,"24":15,"25":17,"26":17,"27":16,"28":16,"29":16,"30":16,"31":17,"32":14,"33":16,"34":17,"35":16,"36":15,"37":15,"38":15,"39":16,"40":16,"41":16,"42":15,"43":15,"44":17,"45":16,"46":15,"47":15,"48":16,"49":17,"50":16,"51":15,"52":16,"53":15,"54":15,"55":17,"56":16,"57":17,"58":16,"59":16,"60":15,"61":15,"62":16,"63":16,"64":17,"65":16,"66":15,"67":16,"68":17,"69":16,"70":15,"71":17} ``` 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 ``` "property.enable.partition.eof" = "false" ``` in your routine load job, it will meet the problem. For EOF has offset, and the config is true in Doris default.
GoGoWen
pushed a commit
to GoGoWen/incubator-doris
that referenced
this pull request
Aug 27, 2024
…ter TTL(apache#37288) (apache#39183) pick (apache#37288) When using routine load, After the data load is completed, the lag is still a positive number: ``` Lag: {"0":16,"1":15,"2":16,"3":16,"4":16,"5":16,"6":15,"7":16,"8":16,"9":16,"10":15,"11":16,"12":15,"13":15,"14":16,"15":16,"16":17,"17":15,"18":16,"19":15,"20":16,"21":16,"22":16,"23":16,"24":15,"25":17,"26":17,"27":16,"28":16,"29":16,"30":16,"31":17,"32":14,"33":16,"34":17,"35":16,"36":15,"37":15,"38":15,"39":16,"40":16,"41":16,"42":15,"43":15,"44":17,"45":16,"46":15,"47":15,"48":16,"49":17,"50":16,"51":15,"52":16,"53":15,"54":15,"55":17,"56":16,"57":17,"58":16,"59":16,"60":15,"61":15,"62":16,"63":16,"64":17,"65":16,"66":15,"67":16,"68":17,"69":16,"70":15,"71":17} ``` 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 ``` "property.enable.partition.eof" = "false" ``` in your routine load job, it will meet the problem. For EOF has offset, and the config is true in Doris default.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
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.