These pages are treated as nullipotent, so DBPerformance log expectation are based on that. However, CentralAuth still uses the master on all POST requests (as a transitional measure). It should really only use it on requests which might write data (most particularly the CentralAuth endpoints the update user data).
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | aaron | T88445 MediaWiki active/active datacenter investigation and work (tracking) | |||
| Open | None | T92357 Fix database master queries from HTTP GET/HEAD before active-active multi-dc | |||
| Resolved | aaron | T134608 CentralAuth uses master on POST requests for API/specialpages that return false for doesWrites() |
Event Timeline
Comment Actions
Change 287292 had a related patch set uploaded (by Aaron Schulz):
Add WebRequest::isNullipotent()/markNullipotent() methods
Comment Actions
Change 287292 merged by jenkins-bot:
Add WebRequest methods for determining "safe" requests
Comment Actions
Change 288365 had a related patch set uploaded (by Aaron Schulz):
Avoid using the master DB for non-write POST requests
Comment Actions
Change 288365 merged by jenkins-bot:
Avoid using the master DB for non-write POST requests