-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
base: main
Are you sure you want to change the base?
Conversation
@@ -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; | |||
} | |||
|
There was a problem hiding this comment.
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
Quality Gate passedIssues Measures |
[Java-Extensions Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[FE Incremental Coverage Report]❌ fail : 10 / 14 (71.43%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
Why I'm doing:
What I'm doing:
Fixes #issue
https://github.com/StarRocks/StarRocksTest/issues/8844
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: