<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Gluster relies on DNS and/or /etc/hosts to determine the IP for a
particular cluster member. You can have gluster utilize a different
IP for *new* connections by updating DNS or /etc/hosts to point the
cluster peer name to a new IP.<br>
<br>
On 4/21/12 7:31 AM, lejeczek wrote:
<blockquote cite="mid:4F929A80.3010700@yahoo.co.uk" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font size="-1"><font face="serif">helo everybody<br>
<br>
this I'd imagine must be common scenario, where a peer, or
more peers are multi if/IPs nodes<br>
for an instance<br>
what happens if a cheaper route to a peer is made available
after some time a volume has been up?<br>
how one introduces this change to the volume? how one tells
the gluster to use different IP whereas everything else
remains unchanged?<br>
<br>
cheers<br>
lejeczek<br>
<br>
<br>
</font></font> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://gluster.org/cgi-bin/mailman/listinfo/gluster-users">http://gluster.org/cgi-bin/mailman/listinfo/gluster-users</a>
</pre>
</blockquote>
</body>
</html>