container-replicator only use one cpu resource to do DB replication

Bug #1729380 reported by Charles Hsu
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
New
Undecided
Unassigned

Bug Description

Container-replicator only consume one CPU resource to do DB replication, if I have 10m container DBs, the container-replicator always busy (100% cpu usage). And the one replication cycle will take few days to finish.
Is there a way to speed it up?

Revision history for this message
clayg (clay-gerrard) wrote :

Multiple worker processes would be the way to go, similar to what was done for the reconstructor [1] and is planned to be added to the replicator [2].

1. https://github.com/openstack/swift/commit/701a172afac37229b85ea762f20428f6f422d29b
2. https://etherpad.openstack.org/p/swift-replicator-handoff-only-workers

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.