Hi John,
Thanks for the explanation. Have a couple of more questions on this subject
though.
1. "pretend_min_hours_passed" sounds like something that I could use. I'm
okay if there is a chance of interruption in services to the user at this
time, as long as it does not cause any data-loss or data
On May 1, 2014, at 10:32 AM, Shyam Prasad N wrote:
> Hi Chuck,
> Thanks for the reply.
>
> The reason for such weight distribution seems to do with the ring rebalance
> command. I've scripted the disk addition (and rebalance) process to the ring
> using a wrapper command. When I trigger the
Hi Chuck,
Thanks for the reply.
The reason for such weight distribution seems to do with the ring rebalance
command. I've scripted the disk addition (and rebalance) process to the
ring using a wrapper command. When I trigger the rebalance after each disk
addition, only the first rebalance seems to
Hi Shyam,
If I am reading your ring output correctly, it looks like only the devices
in node .202 have a weight set, and thus why all of your objects are going
to that one node. You can update the weight of the other devices, and
rebalance, and things should get distributed correctly.
--
Chuck
Hi,
I created a swift cluster and configured the rings like this...
swift-ring-builder object.builder create 10 3 1
ubuntu-202:/etc/swift$ swift-ring-builder object.builder
object.builder, build version 12
1024 partitions, 3.00 replicas, 1 regions, 4 zones, 12 devices, 300.00
balance
The min
