Hi Emmanuel, Restarting a already running daemon is based on restarting volume, restarting glusterd, change in topology of volfile for eg: removing/adding bricks, by performing these thing it should not restart brick, it should only restart daemon's.
could you tell me the name of the option which did brick restart?? Thanx, Gaurav ----- Original Message ----- From: "Emmanuel Dreyfus" <m...@netbsd.org> To: gluster-devel@gluster.org Sent: Thursday, July 23, 2015 1:42:45 PM Subject: [Gluster-devel] volfile change Hello While testing, I noticed that some gluster volume set operations caused a brick restart whil other did not. Comparing the code around both options, I see no difference. How does it decides to restart a daemon? -- Emmanuel Dreyfus m...@netbsd.org _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
