When mixing read and write operations to the database during an edit action, inconsistencies can be introduced due to slave lag if the read operations are performed against a slave DB. We should identify code sections prone to this issue, and address it in a suitable manner.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | hoo | T88986 [Task] Avoid inconsistencies in Wikidata editing due to slave lag | |||
| Resolved | daniel | T88985 ConnectionManager should safeguard against slave lag. | |||
| Resolved | hoo | T108929 [Task] only fallback to master in WikiPageEntityMetaDataLookup when explicitly requested |
Event Timeline
Comment Actions
This was touched on for claim / statement api modules in https://gerrit.wikimedia.org/r/#/c/222900/
Comment Actions
If this bug is wikidata-specific, can someone update the title to reflect that? Also, is anyone working on this yet?
Comment Actions
Is anyone one looking at that? I think I still see it in the logs from time to time by happenstance.
Comment Actions
No, but I can try to look into it next week (can't promise it though). It's not very hard to do, we just need to make sure we set the load from master flag whenever we load for editing and then the behavior can changed.
Comment Actions
I'm closing this and suggest that we rather great individual actionable bugs in case we actually encounter any issues. I don't think this ticket is useful as is.