<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [Gluster-users] Client detect when server comes back up</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi Vikas,<BR>
<BR>
No the files are not being written to Server B, and the log does not say that the server B is connected.<BR>
Does gluster not keep polling to see if its nodes are back up and then reconnect it? Because I'm very sure serverB is up and running.<BR>
<BR>
-----Original Message-----<BR>
From: Vikas Gorur [<A HREF="mailto:vikas@gluster.com">mailto:vikas@gluster.com</A>]<BR>
Sent: Fri 7/3/2009 10:28 PM<BR>
To: Simon Liang<BR>
Cc: gluster-users@gluster.org<BR>
Subject: Re: [Gluster-users] Client detect when server comes back up<BR>
<BR>
<BR>
----- "Simon Liang" <simonl@bigair.net.au> wrote:<BR>
<BR>
> Hi,<BR>
<BR>
> I have a basic 2 server (serverA and serverB) replication with 1<BR>
> client.<BR>
> Sometimes serverB will go offline, so client is writing directly to<BR>
> serverA.<BR>
<BR>
> However when serverB comes back online, the client does not detect<BR>
> this and ignore serverB until I restart the client. Is this meant to<BR>
> happen?<BR>
<BR>
No. Why do you think that the client is ignoring serverB? Are files<BR>
not being created on serverB? Data not being written? Does the client<BR>
log file say "subvolume serverB came up"?<BR>
<BR>
Vikas<BR>
--<BR>
Engineer - <A HREF="http://gluster.com/">http://gluster.com/</A><BR>
<BR>
A: Because it messes up the way people read text.<BR>
Q: Why is a top-posting such a bad thing?<BR>
--<BR>
<BR>
Checked by AVG - www.avg.com<BR>
Version: 8.5.375 / Virus Database: 270.13.2/2215 - Release Date: 07/02/09 18:06:00<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>