Page MenuHomePhabricator

Cargo use of DB_SLAVE does not account for replication lag
Closed, ResolvedPublic

Description

We have connections to slave for queries which inform updates. If the slave is out of date the updates on the master will be derived from stale information. Therefore even the read-only connections in an update cycle need to be made to master.

Event Timeline

EdHoo created this task.Dec 27 2015, 6:33 AM
EdHoo claimed this task.
EdHoo raised the priority of this task from to Medium.
EdHoo updated the task description. (Show Details)
EdHoo added a subscriber: Yaron_Koren.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 27 2015, 6:33 AM
EdHoo renamed this task from #cargo_query use of DB_SLAVE does not account for replication lag to Cargo use of DB_SLAVE does not account for replication lag.Dec 27 2015, 6:34 AM
EdHoo set Security to None.

Change 261105 had a related patch set uploaded (by Ed Hoo):
Use of DB_MASTER in order to consider replication lag

https://gerrit.wikimedia.org/r/261105

Change 261106 had a related patch set uploaded (by Ed Hoo):
Use of DB_MASTER in order to consider replication lag

https://gerrit.wikimedia.org/r/261106

Change 261106 abandoned by Ed Hoo:
Use of DB_MASTER in order to consider replication lag

Reason:
Should have been in the same request.

https://gerrit.wikimedia.org/r/261106

Change 261105 merged by jenkins-bot:
Use of DB_MASTER in order to consider replication lag

https://gerrit.wikimedia.org/r/261105

EdHoo closed this task as Resolved.Dec 28 2015, 5:34 PM