Support replicating objects in handoff partitions first
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Swift Storage Charm |
Fix Released
|
Undecided
|
Drew Freiberger |
Bug Description
In extreme cases of object rebalance or node failure, swift environments with millions of objects may have a hard time with objects landing in handoff or misplaced partitions and the operator of the cloud may need to prioritize migrating data in handoff partitions back to primary partitions over the 3 primary partitions replicating amongst each other.
To allow for this, the object-server.conf configuration can have handoffs_first set to True which will force the object-replicators to focus on handoff partitions before syncing primary partitions for any given object partition.
This will priorize draining the 4th, 5th, 6th, ... nth copy of objects from incorrect locations back to the 3 primary disks for that object's partition over copying that object from one primary copy to the other 2 primary disks.
This is an extreme setting as noted by the product documentation, but is needed for environments where multiple swift-ring rebalances have been performed before the prior replications have had a chance to complete.
Changed in charm-swift-storage: | |
assignee: | nobody → Drew Freiberger (afreiberger) |
Changed in charm-swift-storage: | |
milestone: | none → 20.05 |
Changed in charm-swift-storage: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: stable/18.08 /review. opendev. org/726939
Review: https:/