On 06/12/2014 11:31 PM, Martin Gagnon wrote: > On Thu, Jun 12, 2014 at 02:46:09PM -0400, Eric Rubin-Smith wrote: >> I believe I have seen this issue. It's been a while, but here is the >> scenario >> as far as I can recollect: >> >> 1. Assume there are three repo copies in a "master/client" topology: M, C1, >> and C2. M is the master, and C1/C2 are clones of the master (meaning >> that >> C1 and C2 don't know about each other; they always push to and pull from >> M). No proxies anywhere. >> 2. M, C1, and C2 are all separated by low-bandwidth, high-latency links, >> which ... > I got same issue recently and I'm also using WAL mode. My topology is > like this: > > M: Master > (Linux and main development machine, db in WAL mode) > > C1: clone 1 (autosync with Master) > (windows laptop through slow connection) > > C2: clone 2 (autosync with Master) > (Linux, on LAN with fast connection) > > BK: clone 3 Offsite backup repo > (no checkout, master push to it frequently)
Ah, maybe there is something here! I have almost the same scenario as you, but M is a laptop while C1 and C2 are dev machines and C1 also runs a backup script against M, pulling repos. So I could have the situation where C1 pushes and is also pulling (though locks should prevent any problems), and later on C2 pulls. I don't have the super-long-time push, but it does seem to occur more often when the push involves a large number (or number of bytes) of files. -- For confidential messages, please use my GnuPG key http://ronware.org/gpg_key.html
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
