<div><br><div class="gmail_quote"><div>On Sat, 20 May 2017 at 1:03 AM, Jim Goven <<a href="mailto:radu.gluster@ohmi.org">radu.gluster@ohmi.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I would like to use glusterfs to replicate a volume between my desktop<br>
and my laptop, so that when I am away from home (and likely<br>
disconnected), I can still access some project files. The desktop is on<br>
most of the time, but the laptop is rarely on.<br>
<br>
I have successfully set up gluster to accomplish this goal, but I am<br>
looking to improve the disconnected behaviour of the desktop.<br>
<br>
While the laptop is disconnected (ie, most of the time), the desktop<br>
continuously re-tries to connect to the laptop, but in doing so it<br>
generates too much DNS traffic trying to find the laptop - it looks like<br>
there is no retry delay at all. In turn, the gluster client log files<br>
grow very fast, the DNS resolver logs also grow fast, and there is a lot<br>
of unnecessary network chatter.<br>
<br>
I would like to add a delay of between subsequent re-attempts to<br>
reconnect, but I can't find any such option at<br>
<a href="http://gluster.readthedocs.io/...Managing%20Volumes" rel="noreferrer" target="_blank">http://gluster.readthedocs.io/...Managing%20Volumes</a><br>
<br>
The question is: Is there a way to slow down gluster's attempts to<br>
reconnect?<br>
<br>
I looked through the source as well, and I can't find a delay mechanism.<br>
<br>
Ideally the reconnect attempts would follow an exponential back-off<br>
schedule with a configurable maximum delay, but a fixed, configurable<br>
delay would work too.<br>
<br>
In case a developer reads this, I would be inclined in implementing<br>
exponential backoff myself, and submitting a patch, but would appreciate<br>
a brief advice of where in the codebase this backoff should be inserted.</blockquote><div><br></div><div><br></div><div>Thanks for the offer. Check <a href="https://github.com/gluster/glusterfs/issues/152">https://github.com/gluster/glusterfs/issues/152</a> </div><div><br></div><div>Currently this is fixed number, you can either make it a xlator option or exponential backoff.</div><div><br></div><div>If you make it as xlator option, this should be in protocol/client codebase, and then handle it in rpc_clnt.c code.</div><div><br></div><div>Regards,</div><div>Amar</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Thank you<br>
jg<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>