[Gluster-devel] volfile change
ggarg at redhat.com
Thu Jul 23 10:58:20 UTC 2015
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??
----- Original Message -----
From: "Emmanuel Dreyfus" <manu at netbsd.org>
To: gluster-devel at gluster.org
Sent: Thursday, July 23, 2015 1:42:45 PM
Subject: [Gluster-devel] volfile change
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?
manu at netbsd.org
Gluster-devel mailing list
Gluster-devel at gluster.org
More information about the Gluster-devel