Simon Josefsson wrote: > Is there some tooling to make sure the mirrors are up to date, up to > some small time window?
It's two pronged. 1) I am aggressively watching over the mirror pool verifying that the sync'ing is active. 2) Another volunteer not me (Hi Scott) is working on a monitoring process to verify that the git mirrors are being updated and alerting if one becomes stale. The monitoring not online yet. Life and time is what keeps everything from happening all at once. But Scott is working on it actively at this time. > I recall seeing some stale information through one of the various > savannah git web view links (cannot remember which one, will try to keep > notes if it happens again) until I switched to a more direct way of > viewing content. It's never going to be a perfect solution to have independent mirrors always exactly in sync. They are geographically separated in different datacenters. This gives them resilience against problems that have taken the Boston datacenter down. So that's good. There are going to be global router glitches that occur if nothing else that will every so often create delays. Machines are asynchronously sync'ing in the background and so there will always be some amount of time skew. But it is better than the current situation where literally millions of scraping bots working through residential proxies take the primary offline by overloading it. The primary is required for member commit pushing via ssh. That is the primary function and must be kept working in order to make member commit access work. So other read-only uses must be pushed over to secondaries. Bob
