Description of problem: On 3 node cluster, On this cluster in-service upgrade from 3.4.4 live(3.12.2-47.2) to 3.5.0(6.0.7) is performed 1000 volumes and it is successful. Bumped up the op-version to 70000. Created 300 new volumes and started them all daemons are running fine. Stopped glusterd on one node say N1. Performed a volume set operation 'performance.readdir-ahead on' from node N2 on all the volumes old and newly created volumes and the operation is successful. Started glusterd on node n1. shd and brick process are offline on node N1 for all the volumes. Version-Release number of selected component (if applicable): glusterfs-6.0-7 How reproducible: 2/2 Steps to Reproduce: 1. Create 1000 volumes and start them 2. Perform in-service upgrade on the cluster. 3. Create 300 more volumes (1X3 replicate) and start them 4. Stop glusterd on node N1. 5. Perform volume set operation on all volumes from n2 'performance.readdir-ahead on' and it is successful. 6. Start glusterd on node N1. Actual results: shd and brick process are offline. Expected results: shd and brick process should be online and running. Additional info: