<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 8, 2016 at 4:37 PM, David Gossage <span dir="ltr"><<a href="mailto:dgossage@carouselchecks.com" target="_blank">dgossage@carouselchecks.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div>On Mon, Aug 8, 2016 at 4:23 PM, Joe Julian <span dir="ltr"><<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a>></span> wrote:<br></div></div></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div>On 08/08/2016 01:39 PM, David Gossage
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">So now that I have my cluster on 3.7.14 and sharded
and working I am of course looking for what to break next.
<div><br>
</div>
<div>Currently each of 3 nodes is on a 6 disk (WD Red 1TB)
raidz6 (zil on mirrored ssd), which I am thinking is more
protection than I may need with a 3 way replica. I was going
to one by one change them to basically raid10 letting it heal
in between.</div>
<div><br>
</div>
<div>Is best way to do that a systemctl stop glusterd, should I
just kill the brick process to simulate a brick dying, or is
their an actual brick maintenance command? <br>
</div>
</div>
</blockquote>
<br>
Just kill (-15) the brick process. That'll close the TCP connections
and the clients will just go right on functioning off the remaining
replica. When you format and recreate your filesystem, it'll be
missing the volume-id extended attributes so to start it you'll need
to force it:<br></div></blockquote></div></div></div></blockquote><div><br></div><div>Also could I just do this from different node?</div><div><br></div><div>getfattr -n trusted.glusterfs.volume-id /srv/.bricks/www</div><div><br></div><div>Then on node with new raid10 backed disks</div><div><br></div><div>setfattr -n trusted.glusterfs.volume-id -v 'value_from_other_brick' /srv/.bricks/www<br></div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
gluster volume start $volname start force<br></div></blockquote><div><br></div><div>If I left volume started when brick process is killed and clients are still (in theory) connected to volume wouldn't that just give me an error that volume is already started?</div><div><br></div><div><br></div><div>Likely I would shut down the volume and do downtime for this anyway though letting heals go on with VM's off.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>If /etc/glusterfs is unchanged and /var/lib/glusterd is
unchanged will doing a heal full after reboot or restarting
glusterd take care of everything if I recreate the expected
brick path first?</div>
</div>
</blockquote>
<br>
Once started, perform a full heal to re-replicate.<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Are the improvements in 3.8 for sharding significant enough
I should first look at updating to 3.8.2 when released in few
days?</div>
</div>
</blockquote>
<br>
Yes.<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div><br clear="all">
<div>
<div data-smartmail="gmail_signature">
<div dir="ltr"><span><font color="#888888"><span style="color:rgb(0,0,0)"><b><i>David Gossage</i></b></span><font><i><span style="color:rgb(51,51,51)"><b><br>
</b></span></i></font></font></span>
<div><span><font color="#888888"><font><i><span style="color:rgb(51,51,51)"></span></i><font size="1"><b style="color:rgb(153,0,0)">Carousel
Checks Inc.<span style="color:rgb(204,204,204)"> | System
Administrator</span></b></font></font><font style="color:rgb(153,153,153)"><font size="1"><br>
</font></font><font><font size="1"><span style="color:rgb(51,51,51)"><b style="color:rgb(153,153,153)">Office</b><span style="color:rgb(153,153,153)"> <a value="+17086132426">708.613.2284<font color="#888888"><font size="1"><br>
</font></font></a></span></span></font></font></font></span></div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>______________________________<wbr>_________________
Gluster-users mailing list
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/mailman<wbr>/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman<wbr>/listinfo/gluster-users</a><br></blockquote></div><br></div></div>
</blockquote></div><br></div></div>