<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE>
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
DIV.FoxDiv20130131125651751367 {
COLOR: #000000
}
P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
LINE-HEIGHT: 1.5; FONT-FAMILY: 宋体; COLOR: #000080; FONT-SIZE: 10.5pt
}
</STYLE>
<META name=GENERATOR content="MSHTML 9.00.8112.16457"></HEAD>
<BODY style="MARGIN: 10px">
<DIV>Thanks. But if we use NFS even plus software like keepalived, we 'll lose
the load balance of gluster. All traffic from clients will
firstly reach in and finally flow out from NFS mount
server. It becomes a bottleneck. </DIV>
<DIV> </DIV>
<HR style="WIDTH: 210px; HEIGHT: 1px" align=left color=#b5c4df SIZE=1>
<DIV><SPAN></SPAN></DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">Zhenghua
<DIV
style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKGROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B> <A href="mailto:robinr@miamioh.edu">R, Robin</A></DIV>
<DIV><B>Date:</B> 2013-01-31 11:47</DIV>
<DIV><B>To:</B> <A
href="mailto:glusterzhxue@163.com">glusterzhxue</A></DIV>
<DIV><B>Subject:</B> Re: [Gluster-users] NFS availability</DIV></DIV></DIV>
<DIV>
<DIV class=FoxDiv20130131125651751367>
<DIV dir=ltr>Hi,
<DIV><BR></DIV>
<DIV>You can use software like keepalived to manage a floating IP.</DIV>
<DIV><BR></DIV>
<DIV>So, you can get an IP say 10.1.1.3 and it will float between your host 1
and host 2. </DIV>
<DIV>Only one host at a time has the IP 10.1.1.3. If host 1 dies, host 2 can
assume the floating IP.</DIV>
<DIV><BR></DIV>
<DIV>You'll mount your NFS against the floating IP so the NFS mount still works
even if one of the hosts dies.</DIV>
<DIV><BR></DIV>
<DIV>Robin</DIV>
<DIV><BR></DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Wed, Jan 30, 2013 at 10:28 PM, glusterzhxue <SPAN
dir=ltr><<A href="mailto:glusterzhxue@163.com"
target=_blank>glusterzhxue@163.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote><U></U>
<DIV style="MARGIN: 10px">
<DIV>Hi all,</DIV>
<DIV>As is known to us all, gluster provides NFS mount. However, if
the mount point fails, clients will lose connection to Gluster. While if
we use gluster native client, this fail will have no effect on
clients. For example:</DIV>
<DIV style="TEXT-INDENT: 2em">mount -t glusterfs host1:/vol1 /mnt</DIV>
<DIV> </DIV>
<DIV>If host1 goes down for some reason, client works still,
it has no sense about the failure(suppose we have multiple gluster
servers). However, if we use the following:</DIV>
<DIV
style="TEXT-INDENT: 2em">mount -t nfs -o vers=3
host1:/vol1 /mnt</DIV>
<DIV> </DIV>
<DIV>If host1 failed, client will lose connection to gluster servers.</DIV>
<DIV> </DIV>
<DIV>Now, we want to use NFS way. Could anyone give us some suggestion to
solve the issue?</DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV> </DIV>
<DIV>Zhenghua</DIV></DIV><BR>_______________________________________________<BR>Gluster-users
mailing list<BR><A
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</A><BR><A
href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"
target=_blank>http://supercolony.gluster.org/mailman/listinfo/gluster-users</A><BR></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></BODY></HTML>