| mark added a comment. |
I agree; there's a very good reason for setting masters to read-only when something happened, because it needs manual intervention to investigate whether it's safe to go read-write again. Any automation to do that should be REALLY thoroughly thought through, covering all cases, and it seems doubtful we're able to do that now, especially with naive Puppet manifests.
However, on the other end, monitoring and (where appropriate) alerting on masters that are read-only but shouldn't be, OR MediaWiki hitting read-only databases when they shouldn't (aside from lag and other causes) may be feasible.
TASK DETAIL
EMAIL PREFERENCES
To: jcrespo, mark
Cc: mark, Marostegui, Elitre, Joe, jcrespo, greg, Mbch331, Smalyshev, MisterSynergy, TerraCodes, Jay8g, Liuxinyu970226, Lydia_Pintscher, Aklapper, Esc3300, PokestarFan, GoranSMilovanovic, Th3d3v1ls, Hfbn0, QZanden, Zppix, Johan, Izno, Luke081515, Wikidata-bugs, aude, ArielGlenn, faidon, He7d3r, TheDJ, fgiunchedi, mmodell
Cc: mark, Marostegui, Elitre, Joe, jcrespo, greg, Mbch331, Smalyshev, MisterSynergy, TerraCodes, Jay8g, Liuxinyu970226, Lydia_Pintscher, Aklapper, Esc3300, PokestarFan, GoranSMilovanovic, Th3d3v1ls, Hfbn0, QZanden, Zppix, Johan, Izno, Luke081515, Wikidata-bugs, aude, ArielGlenn, faidon, He7d3r, TheDJ, fgiunchedi, mmodell
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
