Yes, copy the ring out to the nodes, wait an hour, rebalance, and copy the new ring out.

The reason for this is that only one replica of a given partition will move at a time, and this is done to ensure availability of your data even during a rebalance. To see why, imagine that there were no such protection; if all three replicas of a partition moved in a rebalance, then objects in that partition would be unavailable until the replicators moved the objects to their new homes.

on the node you have completed the swift-ring-builder (account/container/object).builder rebalance

run scp /etc/swift/*.ring.gz user@otherhosts:/etc/swift

this will copy the rings out to the other nodes.

bassicly all proxy and storage nodes require the rings to be copied to them so they know what is going on:)

you need to wait an hour between each time you do this minimum as that is what it appears(by default) your ring is set to. not this is the time it takes for a full replication of a partition to take so it might be that it takes less or more time on your deployment, so if you are in a position to wait over night between each time you run this you might be better to wait

I have the same problem,how can i do with this?