Uh oh!
There was an error while loading. Please reload this page.
[fix](cloud) fix routine load loss data when fe master node restart - #46149
Merged
Conversation
Thearas
commented
Dec 30, 2024
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
sollhui
commented
Dec 30, 2024
ContributorAuthor
run buildall |
doris-robot
commented
Dec 30, 2024
TPC-H: Total hot run time: 32467 ms |
doris-robot
commented
Dec 30, 2024
TPC-DS: Total hot run time: 198101 ms |
doris-robot
commented
Dec 30, 2024
ClickBench: Total hot run time: 31.64 s |
sollhuiforce-pushed
the
fix_rl_loss_data
branch
from
December 30, 2024 12:20
dfb56df to
548d59bComparesollhuiforce-pushed
the
fix_rl_loss_data
branch
from
December 30, 2024 13:13
548d59b to
f44548aComparesollhui
commented
Dec 30, 2024
ContributorAuthor
run buildall |
doris-robot
commented
Dec 30, 2024
TPC-H: Total hot run time: 33033 ms |
doris-robot
commented
Dec 30, 2024
TPC-DS: Total hot run time: 191287 ms |
doris-robot
commented
Dec 30, 2024
ClickBench: Total hot run time: 31.23 s |
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
github-actionsBot
pushed a commit
that referenced
this pull request
Jan 7, 2025
…46149) In cloud mode, routine load loss data when fe master node restart. When updating progress, in order to avoid small values covering large values, we introduced pr #39313, Due to the pr that the routine load replays progress metadata by first obtaining the set default offset and then pulling metadata from meta service to update the local value, if the metadata pulled from meta service is not larger than the set default offset, the correct value cannot be assigned to memory. To solve this problem, pulling metadata from meta service when restart, determine whether to obtain default offset from Kafka based on the pulled value.
This file contains hidden or 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
Sign up for freeto 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.
What problem does this PR solve?
Problem Summary:
In cloud mode, routine load loss data when fe master node restart.
When updating progress, in order to avoid small values covering large values, we introduced pr #39313, Due to the pr that the routine load replays progress metadata by first obtaining the set default offset and then pulling metadata from meta service to update the local value, if the metadata pulled from meta service is not larger than the set default offset, the correct value cannot be assigned to memory.
To solve this problem, pulling metadata from meta service when restart, determine whether to obtain default offset from Kafka based on the pulled value.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)