| commit | 54ca8f2b8d2d67710cc3583eebff824b45415141 | |
| author | Sitaram Chamarty <sitaram@atc.tcs.com> | |
| Tue, 15 Dec 2015 05:49:12 +0000 (15 11:19 +0530) | ||
| committer | Sitaram Chamarty <sitaram@atc.tcs.com> | |
| Tue, 15 Dec 2015 06:07:57 +0000 (15 11:37 +0530) | ||
| tree | d679f1e6bc5a5dd94f0df6ec207e7509ac35c224 | treesnapshot (tar.gz zip) |
| parent | ab38ba0a86c13113ad1a9954a11cb497f95318dd | commitdiff |
testing mirror push "one plus one" mode... (read below)
Currently, every time someone does a push to a master server, a slave push
(one for each slave) is triggered.
This is not only wasteful, it also causes too much load. First of all, pushes
should be serialised -- there is no point running TWO 'git push --mirror' from
one server to another. This means when one push is running, any more pushes
of the same repo to the same slave must be queued.
But more importantly, it does not make sense to queue more than one!
Hence the "one(running) plus one(queued)" name of the helper script.
Currently, every time someone does a push to a master server, a slave push
(one for each slave) is triggered.
This is not only wasteful, it also causes too much load. First of all, pushes
should be serialised -- there is no point running TWO 'git push --mirror' from
one server to another. This means when one push is running, any more pushes
of the same repo to the same slave must be queued.
But more importantly, it does not make sense to queue more than one!
Hence the "one(running) plus one(queued)" name of the helper script.
| src/commands/1plus1 | diffblobblamehistory |