| jcrespo added a comment. |
We know the exact timestamps of missing rows,
from
db1071-bin.007238:795791989 2018-09-13 09:08:17 on the active (codfw) master: db2045-bin.005879:1036765620
to
db1071-bin.007238:796727644 2018-09-13 09:58:26 on the active (codfw) master: db2045-bin.005880:132937482We have recovered all sql code executed at that time, no there should not be permanent data loss, I am trying to recover those now in a way that will be safe do no further loss happens of newer transactions- this may take a bit, as this happened a long time ago. If this had been identified 3 days later, we could not even do that, as binlog is purged after 30 days.
In the worse case scenario, we could publish those changes so they are redone, but I am going to try to apply them to the main affected tables (user, revision, page, text, ...) automatically. Content itself was not affected because content is stored through a different replication channel- so only the metadata needed to access it.
Cc: jcrespo, mark, Stashbot, Nikki, Marostegui, daniel, TerraCodes, Liuxinyu970226, Addshore, Ladsgroup, Lea_Lacroix_WMDE, Lexicographical data, KaMan, Nandana, Banyek, jijiki, Mringgaard, AndyTan, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Minhnv-2809, Volans, Jonas, Luke081515, Wikidata-bugs, aude, Lydia_Pintscher, Darkdadaah, Mbch331, Jay8g, Krenair, akosiaris
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
