<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Running a two node replicated volume with GlusterFS 3.5.3, I've
noticed that one node couldn't reach its time server, and is now
about 80 sec behind the other node.<br>
I'm a bit afraid of running a ntpdate to force the clock back on
sync, could such a big jump forward cause gluster to think the files
are out dated and start a heal ? Only meta-data heal maybe ? This
cluster is hosting critical data, and I don't want to take a risk.<br>
<br>
What could happen if I just leave it as is, with a big time offset
between the two nodes ? Could this explain why I see continuous
healed file (see my previous thread "info healed show files being
healed all the time") ?<br>
<br>
Thanks for your advice.<br>
<br>
Cheers<br>
Daniel<br>
<div class="moz-signature">-- <br>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<table>
<tbody>
<tr>
<td>
<p> <img
src="cid:part1.00090900.01000109@firewall-services.com"
alt="Logo FWS" width="275"> </p>
</td>
<td> <font face="Verdana, Geneva, sans-serif" size="2"> <strong>Daniel
Berteaud</strong><br>
<br>
FIREWALL-SERVICES SAS.<br>
Société de Services en Logiciels Libres<br>
Tel : 05 56 64 15 32<br>
Visio : <a class="moz-txt-link-freetext" href="http://vroom.im/dani">http://vroom.im/dani</a><br>
<em><a class="moz-txt-link-abbreviated" href="http://www.firewall-services.com">www.firewall-services.com</a></em> </font> </td>
</tr>
</tbody>
</table>
</div>
</body>
</html>