[Gluster-users] How do I slow down client reconnect attempts?

[Jim Goven]

Hello,

I would like to use glusterfs to replicate a volume between my desktop
and my laptop, so that when I am away from home (and likely
disconnected), I can still access some project files. The desktop is on
most of the time, but the laptop is rarely on.

I have successfully set up gluster to accomplish this goal, but I am
looking to improve the disconnected behaviour of the desktop.

While the laptop is disconnected (ie, most of the time), the desktop
continuously re-tries to connect to the laptop, but in doing so it
generates too much DNS traffic trying to find the laptop - it looks like
there is no retry delay at all. In turn, the gluster client log files
grow very fast, the DNS resolver logs also grow fast, and there is a lot
of unnecessary network chatter.

I would like to add a delay of between subsequent re-attempts to
reconnect, but I can't find any such option at
http://gluster.readthedocs.io/...Managing%20Volumes

The question is: Is there a way to slow down gluster's attempts to
reconnect?

I looked through the source as well, and I can't find a delay mechanism.

Ideally the reconnect attempts would follow an exponential back-off
schedule with a configurable maximum delay, but a fixed, configurable
delay would work too.

In case a developer reads this, I would be inclined in implementing
exponential backoff myself, and submitting a patch, but would appreciate
a brief advice of where in the codebase this backoff should be inserted.

Thank you
jg