Akarsha Rai

@atinmu, yes we had. Volume info and status of testvol: ``` glustercli volume info Volume Name: testvol Type: Distributed-Replicate Volume ID: 464b4ef2-e933-4c1f-b839-1143f13c513d State: Stopped Transport-type: tcp Options: cluster/replicate.self-heal-daemon: on performance/io-cache:...

@atinmu There is one test case on gd1 https://github.com/gluster/glusto-tests/blob/master/tests/functional/glusterd/test_volume_delete.py#L102 I tried running this manually on glusterd version: glusterfs-3.8.4-52.el7rhgs.x86_64 ``` gluster volume status vol1 Status of volume: vol1 Gluster process TCP...

@aravindavk , after volume is stopped and when the node 10.70.43.156 is down: ``` ps aux | grep gluster root 25802 0.1 0.1 1022820 15076 ? Ssl 01:59 0:00 /usr/sbin/glusterfsd...

Initial ps output on node 10.70.43.156 ``` ps aux | grep gluster root 25468 0.5 0.0 604872 5496 ? Ssl 01:53 0:00 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO root 25686 0.0...

I tried giving peer addresses = "0.0.0.0:24008" in config file and was able to peer add with backend network. But I faced few issues: 1. Suppose node n1 has 2...