<html v="urn:schemas-microsoft-com:vml" o="urn:schemas-microsoft-com:office:office" w="urn:schemas-microsoft-com:office:word" m="http://schemas.microsoft.com/office/2004/12/omml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><meta name="Generator" content="Microsoft Word 14 (filtered medium)" /><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Texte brut Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.TextebrutCar
{mso-style-name:"Texte brut Car";
mso-style-priority:99;
mso-style-link:"Texte brut";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="FR" link="blue" vlink="purple">Actually, "gluster volume add-brick vol_name server3:/export/brick1/1" would fail because you have to add bricks in multiples of replica count, ie "gluster volume add-brick vol_name server3:/export/brick1/1 server4:/export/brick1/1" and rebalance.<br>
<br>
The bricks on server1 and server2 will be replicas and server3 and server4. Files will be distributed across those two replica pairs according to filename hashes according to the dht algorithm. <br><br><div class="gmail_quote">On April 22, 2014 8:17:24 AM PDT, "COCHE Sébastien" <SCOCHE@sigma.fr> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US">Sorry if my question is not clear.<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">When I create a new replicated volume, using only 2 nodes, I use this command line : ‘gluster volume create
<i>vol_name</i> replica 2 transport tcp <i>server1</i>:/export/brick1/1 <i>server2</i>:/export/brick1/1’<p></p></span></p>
<p class="MsoPlainText"><i><span lang="EN-US">server1 </span></i><span lang="EN-US">and<i> server2</i> are in 2 different datacenters.
<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Now, if I want to expand gluster volume, using 2 new servers (ex :
<i>server3 </i>and<i> server4)</i> , I use those command lines : <p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">‘gluster volume add-brick <i>vol_name</i> server3: /export/brick1/1’<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">‘gluster volume add-brick <i>vol_name</i> server4: /export/brick1/1’<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">‘gluster volume rebalance <i>vol_name</i> fix-layout start’<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">‘gluster volume rebalance <i>vol_name </i>
start’<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">How the rebalance command work ?<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US">How to be sure that replicated data are not stored on servers hosted in the same datacenter ?<p></p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><p> </p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Sébastien<p></p></span></p>
<p class="MsoPlainText"></p><p> </p>
<p class="MsoPlainText"><span style="mso-fareast-language:FR">-----Message d'origine-----<br />
De : Jeff Darcy [mailto:jdarcy@redhat.com] <br />
Envoyé : vendredi 18 avril 2014 18:52<br />
À : COCHE Sébastien<br />
Cc : gluster-users@gluster.org<br />
Objet : Re: [Gluster-users] Glusterfs Rack-Zone Awareness feature...</span></p>
<p class="MsoPlainText"></p><p> </p>
<p class="MsoPlainText">> I do not understand why it could be a problem to place the data's
</p><p></p>
<p class="MsoPlainText">> replica on a different node group.</p><p></p>
<p class="MsoPlainText">> If a group of node become unavailable (due to datacenter failure, for</p><p></p>
<p class="MsoPlainText">> example) volume should remain online, using the second group.</p><p></p>
<p class="MsoPlainText"></p><p> </p>
<p class="MsoPlainText">I'm not sure what you're getting at here. If you're talking about initial placement of replicas, we can place all members of each replica set in different node groups (e.g. racks). If you're talking about adding new replica members
when a previous one has failed, then the question is *when*.</p><p></p>
<p class="MsoPlainText">Re-populating a new replica can be very expensive. It's not worth starting if the previously failed replica is likely to come back before you're done.</p><p></p>
<p class="MsoPlainText">We provide the tools (e.g. replace-brick) to deal with longer term or even permanent failures, but we don't re-replicate automatically. Is that what you're talking about?</p><p></p>
</div>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />Gluster-users mailing list<br />Gluster-users@gluster.org<br /><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>