<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 27, 2018 at 4:18 PM, Dave Sherohman <span dir="ltr"><<a href="mailto:dave@sherohman.org" target="_blank">dave@sherohman.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Feb 27, 2018 at 03:20:25PM +0530, Karthik Subrahmanya wrote:<br>
> If you want to use the first two bricks as arbiter, then you need to be<br>
> aware of the following things:<br>
> - Your distribution count will be decreased to 2.<br>
<br>
</span>What's the significance of this? I'm trying to find documentation on<br>
distribution counts in gluster, but my google-fu is failing me.<br></blockquote><div>More distribution, better load balancing.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> - Your data on the first subvol i.e., replica subvol - 1 will be<br>
> unavailable till it is copied to the other subvols<br>
> after removing the bricks from the cluster.<br>
<br>
</span>Hmm, ok. I was sure I had seen a reference at some point to a command<br>
for migrating data off bricks to prepare them for removal.<br>
<br>
Is there an easy way to get a list of all files which are present on a<br>
given brick, then, so that I can see which data would be unavailable<br>
during this transfer?<br></blockquote><div>The easiest way is by doing "ls" on the back end brick. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> Since arbiter bricks need not be of same size as the data bricks, if you<br>
> can configure three more arbiter bricks<br>
> based on the guidelines in the doc [1], you can do it live and you will<br>
> have the distribution count also unchanged.<br>
<br>
</span>I can probably find one or more machines with a few hundred GB free<br>
which could be allocated for arbiter bricks if it would be sigificantly<br>
simpler and safer than repurposing the existing bricks (and I'm getting<br>
the impression that it probably would be).</blockquote><div>Yes it is the simpler and safer way of doing that. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Does it particularly matter<br>
whether the arbiters are all on the same node or on three separate<br>
nodes?<br></blockquote><div> No it doesn't matter as long as the bricks of same replica subvol are not on the same nodes.<br><br></div><div>Regards,<br></div><div>Karthik<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dave Sherohman<br>
</font></span></blockquote></div><br></div></div>