Actions
Bug #42691
closedBucket instance obj can't be removed after resharding completed
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
mimic, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
BucketInfoReshardUpdate will update the objv_tracker when setting resharding status. But the outside bucket_info's objv_tracker is not updated and remove_bucket_instance_info will fail.
Updated by Abhishek Lekshmanan over 4 years ago
- Status changed from New to Pending Backport
- Backport set to mimic, nautilus
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43575: mimic: Bucket instance obj can't be removed after resharding completed added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43576: nautilus: Bucket instance obj can't be removed after resharding completed added
Updated by Nathan Cutler about 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions