[Csync2] Csync timeout and lock contention

[Chuck Handshy]

Lars,

I am glad to hear that the next version will have a configurable timeout.

My current experience with many clients working against a central server 
with a large number of
changes to sync show that the timeout alone was not enough. The timeouts 
were still being hit at the
1 second retries and still unable to capture a lock before the extended 
timeouts expired. By adding the
usleep to increase then number of attempts per second and tuning both 
variables allowed most of the
lock contention went away.

I think one of the issues is that with the larger number of clients 
working the db file
we are seeing the higher number of connection attempts to the db file 
and with just
the timeout you will continue to see the lock contention because 
checking once a
second isn't aggressive enough to actually get a lock when competition 
is high.

I think it is important to have those variables available and 
configurable in the next version as every
environment is unique and depending on how busy the networks, servers, 
and other architecture.
Having the ability to tweak these two key variables may allow for a more 
useful experience in the larger
or more intensively utilized setups.

Catch you later,

Chuck Handshy
H2Consulting, LLC.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/csync2/attachments/20130531/37787433/attachment.htm>