Toolserver:Replication lag

Toolserver uses database replication to mirror the Wikimedia database used by the live servers. Each update to the live database is logged, and the Toolserver databases follow this log to make the same updates. The Toolserver databases may fall behind the Wikimedia database, resulting in a situation where the toolserver data represents the state of the Wikimedia database some time in the past. The replication lag (replag) tells how far behind the Wikimedia databases the Toolserver databases have fallen. Database crashes and expensive queries can cause the replag to dramatically increase.

The current replag can be viewed here or there, or by typing @replag in the #wikimedia-toolserver IRC channel on freenode.

When invoked, the replag bot (currently tsbot) will output something like this: s1: 0s [no change]; s1-c: 7s [+0.01 sec/sec]; s2: 1h 24m 42s [-0.62 sec/sec]; s3: 5s [+0.01 sec/sec]; s3-c: 7s [+0.01 sec/sec] (59s sample)

This shows the amount of lag on s1, s2, and s3 and the rate of change for each. It also shows the amount of lag of for the Commons replications (s1-c and s3-c).

But how replagged is my wiki?

 * s1:English Wikipedia
 * s2:Bulgarian Wikipedia and Wiktionary, Wikimedia Commons, Czech Wikipedia, German Wikipedia, English Wikiquote and Wiktionary, Esperanto Wikipedia, Finnish Wikipedia, Indonesian Wikipedia, Italian Wikipedia, Dutch Wikipedia, Norwegian Wikipedia, Polish Wikipedia, Portuguese Wikipedia, Swedish Wikipedia, Thai Wikipedia, Turkish Wikipedia, Chinese Wikipedia
 * s3:Everything else

Or, see Wiki server assignments - the server column lists the same information as above.