<p dir="ltr"><br>
On Oct 1, 2019 15:40, ML <lists@websiteburo.com> wrote:<br>
><br>
> Hi there,<br>
><br>
> I'm looking for the community's opinion on a gluster volume rebalance <br>
> I'm hestitating to start :)<br>
><br>
> Here is my config :<br>
><br>
> Volume Name: nas-3<br>
> Type: Distributed-Replicate<br>
> Status: Started<br>
> Number of Bricks: 2 x 2 = 4<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: <a href="http://192.168.0.1">192.168.0.1</a>:/home/nas-3<br>
> Brick2: <a href="http://192.168.0.2">192.168.0.2</a>:/home/nas-3<br>
> Brick3: <a href="http://192.168.0.3">192.168.0.3</a>:/home/nas-3<br>
> Brick4: <a href="http://192.168.0.4">192.168.0.4</a>:/home/nas-3<br>
> Options Reconfigured:<br>
> performance.quick-read: off<br>
> performance.cache-size: 500MB<br>
> <a href="http://performance.io">performance.io</a>-thread-count: 32<br>
> transport.address-family: inet<br>
> performance.readdir-ahead: on<br>
><br>
> The bricks are constitued of 4 gluster servers version 3.10.12 :<br>
><br>
> <a href="http://192.168.0.1">192.168.0.1</a> + <a href="http://192.168.0.2">192.168.0.2</a> = 2 x 22 TiB (global usage : 86%)<br>
> <a href="http://192.168.0.3">192.168.0.3</a> + <a href="http://192.168.0.4">192.168.0.4</a> = 2 x 7   TiB (global usage : 40%) (this 2 <br>
> bricks came 1 year after the 2 first ones, without rebalance after went <br>
> live)<br>
><br>
> Actual usage :<br>
><br>
> on <a href="http://192.168.0.1">192.168.0.1</a> + <a href="http://192.168.0.2">192.168.0.2</a> : /home/nas-3 = 2 x 14,5TiB (Items: 49327658)<br>
> on <a href="http://192.168.0.3">192.168.0.3</a> + <a href="http://192.168.0.4">192.168.0.4</a> : /home/nas-3 = 2 x 2,8TiB (Items: 10343981)<br>
><br>
> I need advice regarding :<br>
><br>
> - Should I rebalance to fill the 2 x 7.2TiB servers ? (I need space on <br>
> the 22TiB servers)</p>
<p dir="ltr">I would say - yes.</p>
<p dir="ltr">> - Is rebalance process dividing files based on disk usage for each <br>
> connected brick ? (I'm afraid to see my 7.2 TiB servers become full)<br>
Nah... Gluster is way smarter than that.Still, distribution is calculated via an algorithm which we can easily call hashing.Each brick has a hash range and when a file is not on it's hashed location - you should rebalance.</p>
<p dir="ltr">By the way, this should have been done when you added the new bricks.</p>
<p dir="ltr">For details, check: <a href="https://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/dht">https://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/dht</a>/<br></p>
<p dir="ltr">> - Given the number of files stored, how to get an idea of the time <br>
> needed for the rebalance process to be complete ?</p>
<p dir="ltr">You can't estimate that with high accuracy as you got plenty of variables -> number of files that should be balanced,size of the files that should be balanced, network bandwidth, load on the volume from your clients, speed of the underlying disks, etc.</p>
<p dir="ltr">It could take a week , maybe less .</p>
<p dir="ltr">> Thank you for reading me & considering answering :))<br>
><br>
> (If there's a gluster consultant you would recommand for these <br>
> questions, please let me know)<br>
><br>
> Quentin<br>
><br>
> ________<br>
><br>
> Community Meeting Calendar:<br>
><br>
> APAC Schedule -<br>
> Every 2nd and 4th Tuesday at 11:30 AM IST<br>
> Bridge: <a href="https://bluejeans.com/118564314">https://bluejeans.com/118564314</a><br>
><br>
> NA/EMEA Schedule -<br>
> Every 1st and 3rd Tuesday at 01:00 PM EDT<br>
> Bridge: <a href="https://bluejeans.com/118564314">https://bluejeans.com/118564314</a><br>
><br>
> Gluster-users mailing list<br>
> Gluster-users@gluster.org<br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br></p>
<p dir="ltr">Best Regards,<br>
Strahil Nikolov</p>