[Gluster-users] Rebalancing newly added bricks

[Strahil]

Hi Nithya,

Thanks for the detailed explanation.
It makes sense.

Best Regards,
Strahil NikolovOn Sep 12, 2019 08:18, Nithya Balachandran <nbalacha at redhat.com> wrote:
>
>
>
> On Wed, 11 Sep 2019 at 09:47, Strahil <hunter86_bg at yahoo.com> wrote:
>>
>> Hi Nithya,
>>
>> I just reminded about your previous  e-mail  which left me with the impression that old volumes need that.
>> This is the one 1 mean:
>>
>> >It looks like this is a replicate volume. If >that is the case then yes, you are >running an old version of Gluster for >which this was the default
>
>
> Hi Strahil,
>
> I'm providing a little more detail here which I hope will explain things.
> Rebalance was always a volume wide operation - a rebalance start operation will start rebalance processes on all nodes of the volume. However, different processes would behave differently. In earlier releases, all nodes would crawl the bricks and update the directory layouts. However, only one node in each replica/disperse set would actually migrate files,so the rebalance status would only show one node doing any "work" (scanning, rebalancing etc). However, this one node will process all the files in its replica sets. Rerunning rebalance on other nodes would make no difference as it will always be the same node that ends up migrating files.
> So for instance, for a replicate volume with server1:/brick1, server2:/brick2 and server3:/brick3 in that order, only the rebalance process on server1 would migrate files. In newer releases, all 3 nodes would migrate files.
>
> The rebalance status does not capture the directory operations of fixing layouts which is why it looks like the other nodes are not doing anything.
>
> Hope this helps.
>
> Regards,
> Nithya
>>
>> behaviour. 
>>
>> >
>> >
>>
>> >Regards,
>>
>> >
>>
>> >Nithya
>>
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On Sep 9, 2019 06:36, Nithya Balachandran <nbalacha at redhat.com> wrote:
>>>
>>>
>>>
>>> On Sat, 7 Sep 2019 at 00:03, Strahil Nikolov <hunter86_bg at yahoo.com> wrote:
>>>>
>>>> As it was mentioned, you might have to run rebalance on the other node - but it is better to wait this node is over.
>>>>
>>>
>>> Hi Strahil,
>>>
>>> Rebalance does not need to be run on the other node - the operation is a volume wide one . Only a single node per replica set would migrate files in the version used in this case .
>>>
>>> Regards,
>>> Nithya
>>>
>>>> Best Regards,
>>>> Strahil Nikolov
>>>>
>>>> В петък, 6 септември 2019 г., 15:29:20 ч. Гринуич+3, Herb Burnswell <herbert.burnswell at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190912/8df2f997/attachment.html>