Hi Lars,<br><br><blockquote style="margin:0 0 0 40px;border:none;padding:0px">Good news is that i worked around the issue by setting the "lock-timeout 60;" in each of the csync configuration files.<br><br>When I set it for 30 the issue was still occuring on an average 1 in 7 so i have set it up as 60 seconds, and after that i could not see this issue, at least in dozen plus tests with a very bad (simulated) network.<br>
<br>So, this issue can be attributed to slower networks ( "-B" option did not help) and the workaround or may be a solution is to set appropriate lock-timeout in csync configuration file.<br><br>I'm still curious to know as to how would network strength (or rather weakness of it) affect the transaction time since csync accesses SQLite database on the same host and not remotely.<br>
<br></blockquote>Thanks and Regards,<br>Samba<br>===================================================================================<br><div class="gmail_quote">On Mon, Aug 6, 2012 at 4:28 PM, Samba <span dir="ltr"><<a href="mailto:saasira@gmail.com" target="_blank">saasira@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br><div style="margin-left:40px">I could reproduce this issue with the code checked out from the trunk as well. <br>
<br>Issue seems to be occurring when we have slow network [reproducbe at least once in 5 times over a WAN ping response-times 300 ms; if i increase delay to 1000 ms, then almost always reproducible].<br>
<br>I'm not sure why network speed (or rather slowness of it) would have any impact on SQLite database transactions, since the database is accessed locally within the same host.<br><br>I tried the option "-B" which is suggested over slow networks but that also could not completely resolve the issue although occasionally it did reduce the frequency of occurrence.<br>
<br>It would be great if any workaround [or if possible, a workable solution] is suggested.<br><br></div>Thanks and Regards,<br>Samba<br><br>===========================================================<div class="HOEnZb">
<div class="h5"><br><div class="gmail_quote">
On Tue, Jul 31, 2012 at 6:48 PM, Samba <span dir="ltr"><<a href="mailto:saasira@gmail.com" target="_blank">saasira@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Lars,<blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>I'm getting the error "Database backend is exceedingly busy => Terminating (requesting retry)" occasionally; not sure if it has to do with the patch I provided for "subdir_deletion" though. I'm sure that i did not play with SQL queries in my first version of the patch and even with that I see this error coming up occasionally, perhaps when the network is slow. I'm planning to run a few more tests to confirm whether this issue exists in the trunk version or introduced with my patch.</div>
<div><br></div><div>Could you throw some light on what can be going wrong to get that error?</div><div><br></div></blockquote>Thanks and Regards,<div>Samba<br><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><br></div></blockquote></div>
</blockquote></div><br>
</div></div></blockquote></div><br>