[Gluster-users] Rebalance times in 3.2.5 vs 3.4.2
viktor.villafuerte at optusnet.com.au
Tue Feb 25 04:21:40 UTC 2014
I have distributed replicated set with 2 servers (replicas) and am
trying to add another set of replicas: 1 x (1x1) => 2 x (1x1)
I have about 23G of data which I copy onto the first replica, check
everything and then add the other set of replicas and eventually
rebalance fix-layout, migrate-data.
Gluster v3.2.5 this took about 30 mins (to rebalance + migrate-data)
Gluster v3.4.2 this has been running for almost 4 hours and it's still
As I may have to do this in production, where the amount of data is
significantly larger than 23G, I'm looking at about three weeks of wait
to rebalance :)
Now my question is if this is as it's meant to be? I can see that v3.4.2
gives me more info about the rebalance process etc, but that surely
cannot justify the enormous time difference.
Is this normal/expected behaviour? If so I will have to stick with the
v3.2.5 as it seems way quicker.
Please, let me know if there is any 'well known' option/way/secret to
speed the rebalance up on v3.4.2.
Optus Internet Engineering
t: 02 808-25265
More information about the Gluster-users