Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BugFix] fix enable sync publish when clone #37398

Merged
merged 2 commits into from
Dec 21, 2023

Conversation

luohaha
Copy link
Contributor

@luohaha luohaha commented Dec 19, 2023

Why I'm doing:
In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable.

But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet.

What I'm doing:
Using max_readable_version instead of version to update replica version when clone finish.

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.2
    • 3.1
    • 3.0
    • 2.5

@luohaha luohaha changed the title [Bugfix] fix enable sync publish when clone [BugFix] fix enable sync publish when clone Dec 19, 2023
sevev
sevev previously approved these changes Dec 20, 2023
decster
decster previously approved these changes Dec 20, 2023
sevev
sevev previously approved these changes Dec 21, 2023
Signed-off-by: luohaha <[email protected]>
Copy link

sonarcloud bot commented Dec 21, 2023

Copy link

[FE Incremental Coverage Report]

pass : 4 / 4 (100.00%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 com/starrocks/clone/TabletSchedCtx.java 4 4 100.00% []

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

@decster decster merged commit 575e644 into StarRocks:main Dec 21, 2023
45 checks passed
Copy link

@Mergifyio backport branch-3.2

@github-actions github-actions bot removed the 3.1 label Dec 21, 2023
Copy link

@Mergifyio backport branch-3.0

Copy link
Contributor

mergify bot commented Dec 21, 2023

backport branch-3.2

✅ Backports have been created

@github-actions github-actions bot removed the 3.0 label Dec 21, 2023
Copy link
Contributor

mergify bot commented Dec 21, 2023

backport branch-3.1

✅ Backports have been created

Copy link

@Mergifyio backport branch-2.5

@github-actions github-actions bot removed the 2.5 label Dec 21, 2023
Copy link
Contributor

mergify bot commented Dec 21, 2023

backport branch-3.0

✅ Backports have been created

Copy link
Contributor

mergify bot commented Dec 21, 2023

backport branch-2.5

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Dec 21, 2023
Why I'm doing:
In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable.

But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet.

What I'm doing:
Using max_readable_version instead of version to update replica version when clone finish.

Signed-off-by: luohaha <[email protected]>
(cherry picked from commit 575e644)
mergify bot pushed a commit that referenced this pull request Dec 21, 2023
Why I'm doing:
In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable.

But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet.

What I'm doing:
Using max_readable_version instead of version to update replica version when clone finish.

Signed-off-by: luohaha <[email protected]>
(cherry picked from commit 575e644)
mergify bot pushed a commit that referenced this pull request Dec 21, 2023
Why I'm doing:
In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable.

But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet.

What I'm doing:
Using max_readable_version instead of version to update replica version when clone finish.

Signed-off-by: luohaha <[email protected]>
(cherry picked from commit 575e644)
mergify bot pushed a commit that referenced this pull request Dec 21, 2023
Why I'm doing:
In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable.

But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet.

What I'm doing:
Using max_readable_version instead of version to update replica version when clone finish.

Signed-off-by: luohaha <[email protected]>
(cherry picked from commit 575e644)
@sevev
Copy link
Contributor

sevev commented Dec 21, 2023

@mergify backport branch-2.5-bx

Copy link
Contributor

mergify bot commented Dec 21, 2023

backport branch-2.5-bx

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Dec 21, 2023
Why I'm doing:
In previous PR #27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable.

But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet.

What I'm doing:
Using max_readable_version instead of version to update replica version when clone finish.

Signed-off-by: luohaha <[email protected]>
(cherry picked from commit 575e644)
sevev pushed a commit that referenced this pull request Dec 21, 2023
luohaha added a commit that referenced this pull request Dec 21, 2023
wanpengfei-git pushed a commit that referenced this pull request Dec 21, 2023
wanpengfei-git pushed a commit that referenced this pull request Dec 21, 2023
wanpengfei-git pushed a commit that referenced this pull request Dec 21, 2023
Zhangg7723 pushed a commit to Zhangg7723/starrocks that referenced this pull request Dec 26, 2023
Why I'm doing:
In previous PR StarRocks#27055 , we add config enable_sync_publish. When it is true, BE will return publish version request success until all version is queryable.

But when clone happen, BE report both version and max_readable_version to FE in finish clone request, and FE will use version instead of max_readable_version to update replica version, so it will broken the rule that enable_sync_publish define, because version may not queryable yet.

What I'm doing:
Using max_readable_version instead of version to update replica version when clone finish.

Signed-off-by: luohaha <[email protected]>
Signed-off-by: 张敢 <[email protected]>
mergify bot added a commit that referenced this pull request Jan 2, 2024
andyziye pushed a commit that referenced this pull request Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants