[Gluster-users] Re-balancing after expansion

Jon Tegner tegner at renget.se
Mon Apr 29 12:36:37 UTC 2013

On 04/29/2013 01:08 PM, Hans Lambermont wrote:
> Jon Tegner wrote on 20130429:
>> On 04/26/2013 12:03 PM, Hans Lambermont wrote:
>>> Jon Tegner wrote on 20130426:
>>>> Hi, I have a system using 3.2.6-1, running ext4. I recently expanded
>>>> the system from 4 to 5 servers. I have NOT yet done re-balancing of
>>>> the system - so at the moment most of the writing of new files goes to
>>>> the new server.
>>>> My impression is that it would be possible to re balance while the
>>>> system is in use, is this correct?
>>> Yes.
>> went ahead and did
>> gluster volume rebalance glusterNoriko migrate-data start
>> and seemed to start OK. However, when running
>> gluster volume rebalance glusterNoriko status
>> system reports
>> rebalance not started. Should I be worried here?
> Yes, search the gluster logs for the abort reason and work from there.
gluster volume info gives:

Name: glusterNoriko
Type: Distribute
Status: Started
Number of Bricks: 5
Transport-type: tcp,rdma
Brick1: n01-noriko:/mnt/raid10
Brick2: n02-noriko:/mnt/raid10
Brick3: n03-noriko:/mnt/raid10
Brick4: n04-noriko:/mnt/raid10
Brick5: n05-noriko:/mnt/raid10
Options Reconfigured:
nfs.disable: off

However, when running "gluster volume info"  (or other gluster commands) 
I get stuff like

0-rpc-transport: missing 'option transport-type', defaulting to "socket"
geo-replication not installed

Seems to be infiniband related?



More information about the Gluster-users mailing list