when min_part_hours is zero composite rebalance may move same partition in multiple cobuilders
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
High
|
Alistair Coles |
Bug Description
CompositeRingBu
The proposd patch will include a test that illustrates the bug.
[1] It might be argued that zero min_part_hours suggests it is ok for multiple co-builders to move the same partition - "it is fine to move this part again in a subsequent rebalance with no delay". However, IMO that is not the design goal of composite rebalance, where each component rebalance is not a "subsequent rebalance". Users may have other means of preventing subsequent rebalance of single or composite rings occurring too often, which makes the use of zero min_part_hours simply a convenience. Composite rebalance must enforce single partition movement regardless of min_part_hours.
Changed in swift: | |
importance: | Undecided → High |
Fix proposed here https:/ /review. openstack. org/#/c/ 499634/ 1