[Gluster-users] rebalance and volume commit hash

Piotr Misiak pmisiak at cloudferro.com
Tue Jan 17 16:40:26 UTC 2017

17 sty 2017 17:10 Jeff Darcy <jdarcy at redhat.com> napisał(a):
> > Do you think that is wise to run rebalance process manually on every 
> > brick with the actual commit hash value? 
> > 
> > I didn't do anything with bricks after previous rebalance run and I have 
> > cluster.weighted-rebalance=off. 
> > 
> > My problem is that I have a very big directory structure (millions of 
> > directories and files) and I haven't ever completed rebalance process 
> > once, because it will take I guess weeks or months. I'd like to speed it 
> > up a bit by not generating new commit hash for volume during new 
> > rebalance run. Then directories rebalanced in the previous run will be 
> > untouched during the new run. Is it possible? 
> I'm pretty sure that trying to rebalance on each brick separately will 
> not work correctly.  Rebalancing smaller pieces of the directory 
> hierarchy separately, by issuing the appropriate setxattr calls on them 
> instead of using the CLI, *might* work.  Either way, I think the DHT 
> experts could provide a better answer. 

Is it possible to start rebalancing from a particular subdirecory? Do you know how? It would be very useful for me.

More information about the Gluster-users mailing list