Re: [Gluster-devel] volfile change

2015-07-23 Thread Gaurav Garg
Hi Emmanuel,

ssl.dh-param (not yet committed) seems to restart the daemon while
ssl.cipher-list does not.

ss.dh-param is the option that you are adding additionally based on your 
requirement in current gluster code. 

So we need to check your patch first then only we can say how brick is 
restarting. As of now restarting brick is not plausible after executing volume 
set command.

Thanx,
~Gaurav


- Original Message -
From: Emmanuel Dreyfus m...@netbsd.org
To: Gaurav Garg gg...@redhat.com
Cc: gluster-devel@gluster.org
Sent: Thursday, July 23, 2015 11:08:39 PM
Subject: Re: [Gluster-devel] volfile change

Gaurav Garg gg...@redhat.com wrote:

 could you tell me the name of the option which did brick restart?



-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] volfile change

2015-07-23 Thread Emmanuel Dreyfus
Gaurav Garg gg...@redhat.com wrote:

 could you tell me the name of the option which did brick restart?

ssl.dh-param (not yet committed) seems to restart the daemon while
ssl.cipher-list does not.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] volfile change

2015-07-23 Thread Gaurav Garg
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