On 06/20/2016 08:27 AM, Rodolfo Gonzalez wrote: > Hi, > > I have a volume with these characteristics: > > # gluster volume info > > Volume Name: data > Type: Distributed-Replicate > Volume ID: 7775b714-45ae-4a68-bdf6-8c3c2e4fbfae > Status: Started > Number of Bricks: 2 x 2 = 4 > Transport-type: tcp > Bricks: > Brick1: data1:/volume/data > Brick2: data2:/volume/data > Brick3: data3:/volume/data > Brick4: data4:/volume/data > Options Reconfigured: > server.allow-insecure: on > > The partitions holding the bricks in the 4 servers got full, so I'm > trying to add 2 brand new bricks (just the partitions created with the > same size, empty by now). From data1: > > # gluster peer probe data5 > # gluster peer probe data6 > > # gluster volume add-brick data data5:/volume/data data6:/volume/data > volume add-brick: failed: Host data5 is not in 'Peer in Cluster' state > > When I check: > > # gluster peer status > Number of Peers: 5 > > Hostname: data2 > Uuid: 155d0250-a748-4df2-a46a-f724570d15ee > State: Peer in Cluster (Connected) > > Hostname: data3 > Uuid: c9dab2e1-2da5-4d75-9eae-475acb3d0f2e > State: Peer in Cluster (Connected) > > Hostname: data4 > Uuid: d3df7e79-22cf-459f-8349-8321dd1da59c > State: Peer in Cluster (Connected) > > Hostname: data5 > Uuid: 26755e17-2584-4152-b838-0145f9886087 > State: Peer Rejected (Connected) > > Hostname: data6 > Uuid: a053cf52-93bd-41bc-bf4f-df49bef10c32 > State: Peer in Cluster (Connected) > > I see that data 5 is "peer rejected" in this data1 server, but also in > the other 4 original servers. And in data5: It does look like either data5 is not an empty node and part of an cluster or already holds a volume (recently added) or the gluster version on data5 is not compatible. The way to check which one it is to have a look at glusterd log in data1. You should be able to see an error log entry for this. Once you provide me the exact log, I can come back with the workaround here. Also do mention the gluster version you are using. ~Atin > > root@data5:/var/lib/glusterd# gluster peer status > Number of Peers: 5 > > Hostname: data6 > Uuid: a053cf52-93bd-41bc-bf4f-df49bef10c32 > State: Peer in Cluster (Connected) > > Hostname: data2 > Uuid: 155d0250-a748-4df2-a46a-f724570d15ee > State: Peer Rejected (Connected) > > Hostname: data3 > Uuid: c9dab2e1-2da5-4d75-9eae-475acb3d0f2e > State: Peer Rejected (Connected) > > Hostname: data1 > Uuid: 48f3fe1a-cb89-45af-9e48-c16f99b5d756 > State: Peer Rejected (Connected) > > Hostname: data4 > Uuid: d3df7e79-22cf-459f-8349-8321dd1da59c > State: Peer Rejected (Connected) > > I have tried this proposed solution several times: > > http://www.gluster.org/community/documentation/index.php/Resolving_Peer_Rejected > > , but I keep getting the same result for peer status. > > I also found this, but I don't dare to apply it without knowing it it > applies to my case: > > http://comments.gmane.org/gmane.comp.file-systems.gluster.user/12547 > > Any help is appreciated, thanks in advanced. > > # dpkg -l | grep gluster > ii glusterfs-client 3.6.9-ubuntu1~trusty1 > amd64 clustered file-system (client package) > ii glusterfs-common 3.6.9-ubuntu1~trusty1 > amd64 GlusterFS common libraries and translator modules > ii glusterfs-server 3.6.9-ubuntu1~trusty1 > amd64 clustered file-system (server package) > > Ubuntu 14.04 > > Regards. > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
