On Sun, May 7, 2017 at 10:06 PM, Tahereh Fattahi <[email protected]> wrote:
> Thanks a lot > For gv2, I have two bricks, second peer is in peer list from node I want > to delete. > But there are other nodes for other volumes, not gv2, that are in peer > list but are not connected. How can I remove these nodes from peer list? > Please note in existing GlusterD's design the configuration of all volumes (irrespective of which nodes the bricks are hosted) are stored across all the nodes and hence it becomes mandatory to have all the nodes to be up if a volume has to be deleted. Even when it comes detaching a peer, you can't detach a peer having bricks hosted for the volumes. So you'd have to bring in the nodes first, delete all the unwanted volumes and then detach them. With GlusterD2, this problem will automatically be solved as every nodes need not to participate in the transaction. > > On Sun, May 7, 2017 at 9:00 PM, Atin Mukherjee <[email protected] > > wrote: > >> Can you please paste the output of 'gluster peer status' from the node >> where volume delete CLI failed? Also during this failure did you find out >> which node(s) are down (as per the command) from the glusterd logs? >> >> On Sun, 7 May 2017 at 21:53, Tahereh Fattahi <[email protected]> >> wrote: >> >>> Hi >>> >>> When I want to delete my test volume I get error: >>> volume delete: gv2: failed: Some of the peers are down >>> >>> But all nodes are up (service glsterd, connetion, ip , .. all things are >>> ok ) and before stop or after start (after trying for deletion) work >>> correctly. >>> >>> So how can I delete the volume? it is necessary for me. >>> _______________________________________________ >>> Gluster-users mailing list >>> [email protected] >>> http://lists.gluster.org/mailman/listinfo/gluster-users >> >> -- >> --Atin >> > >
_______________________________________________ Gluster-users mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-users
