Re: Restricting add-brick when volume is stopped.

[Joe Julian <joe@xxxxxxxxxxxxxxxx>]

I know of at least one user that created a volume then added bricks afterword before starting it as part of his scripted deployment method. Not sure if he was changing replica count. They did that because of command line length limitations. I'm not sure why they couldn't use stdin.

On February 22, 2016 11:27:24 PM PST, Anuradha Talur <atalur@xxxxxxxxxx> wrote:

Hi,

AFR has a requirement that when replica count is changed while adding bricks to a volume, e.g., converting a replica 2 to replica 3, afr pending xattrs are marked to indicate this change. (To prevent potential data-loss)

This is possible only when the volume is not stopped, which is a deviation from the present behaviour that allows add-brick even when the volume is stopped. I sent a patch : http://review.gluster.org/#/c/12451/ , if this change is included, only such add-brick operations that change replica count will be forbidden when the volume is stopped. I would like to know if there are any objections to this.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel