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 migrate storage medium miss auto-bucket partition bug #53101

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

HangyuanLiu
Copy link
Contributor

@HangyuanLiu HangyuanLiu commented Nov 21, 2024

Why I'm doing:

What I'm doing:

Fixes #issue
https://github.com/StarRocks/StarRocksTest/issues/8844

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.4
    • 3.3
    • 3.2
    • 3.1
    • 3.0

@HangyuanLiu HangyuanLiu requested a review from a team as a code owner November 21, 2024 12:15
@github-actions github-actions bot added the 3.4 label Nov 21, 2024
@@ -1515,7 +1525,7 @@ protected static void handleMigration(ListMultimap<TStorageMedium, Long> tabletM
continue;
}

if (!migratableTablet(db, table, tabletMeta.getPhysicalPartitionId(), tabletMeta.getIndexId(), tabletId)) {
if (!migrateTablet(db, table, tabletMeta.getPhysicalPartitionId(), tabletMeta.getIndexId(), tabletId)) {
continue;
}

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The most risky bug in this code is:
There seems to be a logical inconsistency with using physicalPartitionId instead of partitionId when fetching the storage medium for migration, which might lead to incorrectly determining whether a tablet needs migration.

You can modify the code like this:

// In the context where storage medium is being checked for migration
TStorageMedium storageMedium = storageMediumMap.get(physicalPartitionId); // Change from .getParentId() to use the correct id

Copy link

sonarcloud bot commented Nov 21, 2024

Copy link

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[FE Incremental Coverage Report]

fail : 10 / 14 (71.43%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 com/starrocks/clone/TabletScheduler.java 0 1 00.00% [1553]
🔵 com/starrocks/leader/ReportHandler.java 10 13 76.92% [680, 688, 703]

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants