multiple runs of swift-dispersion-populate create duplicate partitions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
it seems that multiple runs of swift-dispersio
root@swiftn4:~# swift-dispersio
Queried 982 containers for dispersion reporting, 1s, 0 retries
There were 4 overlapping partitions
99.59% of container copies found (2934 of 2946)
Sample represents 2.98% of the container partition space
Queried 981 objects for dispersion reporting, 1s, 0 retries
There were 9 overlapping partitions
99.08% of object copies found (2916 of 2943)
Sample represents 2.97% of the object partition space
should swift-dispersio
Changed in swift: | |
status: | New → Fix Released |
Once swift-dispersio n-populate is run once, do we even want it to be able to run a second time? Running it twice, should in theory double the partition coverage required in the dispersion.conf file (is this desired behaviour) but as pointed out in this bug, there can be overlaps with partitions.
Could a potential solution here be to add an "--override" option to the swift-dispersio n-populate tool which would remove all the containers/objects from the previous populate run and keep the coverage percentage consistent with the dispersion.conf file.
As an adition or alternative to this, a check could be added to the code where if "swift- dispersion- populate" has been run before, it will not populate again.