I created a 2 node distribute volume with rdma transport type. I added on more brick to the volume. Now I mounted and pushed in some data to the volume. Now When I run the 'rebalance', it says "rebalance failed". The same thing happens with rebalance 'fix-layout' and 'data-migration' options. glusterd logs says that "transport endpoint is not connected". [2011-06-27 12:49:17.60034] W [socket.c:1494:__socket_proto_state_machine] 0-socket.management: reading from socket failed. Error (Transport endpoint is not connected), peer (127.0.0.1:1013) [2011-06-27 12:49:17.60055] D [socket.c:1768:socket_event_handler] 0-transport: disconnecting now
PATCH: http://patches.gluster.com/patch/7697 in master (mount/fuse: wait till CHILD_UP event is recieved to do the first lookup.)
PATCH: http://patches.gluster.com/patch/7698 in master (rpc-transport/rdma: call ibv_fork_init to make rdma work with fork.)
PATCH: http://patches.gluster.com/patch/7706 in master (mnt/fuse: Do a pthread_cond_broadcast for both CHILD_UP and CHILD_DOWN events.)
PATCH: http://patches.gluster.com/patch/7702 in release-3.1 (rpc-transport/rdma: call ibv_fork_init to make rdma work with fork.)
PATCH: http://patches.gluster.com/patch/7703 in release-3.1 (mount/fuse: wait till CHILD_UP event is recieved to do the first lookup.)
PATCH: http://patches.gluster.com/patch/7704 in release-3.1 (mnt/fuse: Do a pthread_cond_broadcast for both CHILD_UP and CHILD_DOWN events.)
PATCH: http://patches.gluster.com/patch/7695 in release-3.2 (rpc-transport/rdma: call ibv_fork_init to make rdma work with fork.)
PATCH: http://patches.gluster.com/patch/7696 in release-3.2 (mount/fuse: wait till CHILD_UP event is recieved to do the first lookup.)
PATCH: http://patches.gluster.com/patch/7707 in release-3.2 (mnt/fuse: Do a pthread_cond_broadcast for both CHILD_UP and CHILD_DOWN events.)
PATCH: http://patches.gluster.com/patch/7772 in release-3.2 (client-handshake: skip CHILD_DOWN notifications when client is querying port using different volume names in the presence of rdma.)
PATCH: http://patches.gluster.com/patch/7774 in master (client-handshake: skip CHILD_DOWN notifications when client is querying port using different volume names in the presence of rdma.)
PATCH: http://patches.gluster.com/patch/7773 in release-3.1 (client-handshake: skip CHILD_DOWN notifications when client is querying port using different volume names in the presence of rdma.)
This issue is fixed now in 3.2.2qa8. Checked with rebalance start and also with fix-layout and migrtae-data. Both the options are working fine,
tested on 3.1.6qa3 and it's working fine. Rebalance succeeds and also 'fix-layout' and 'migrate-data' succeeds.