Core Platform Team/Initiatives/Multi-DC Replication Lag
 | This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. The Core Platform Team and its initiatives do not exist anymore. See MediaWiki Engineering Group instead since 2023. |
Initiative Description
| This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. The Core Platform Team and its initiatives do not exist anymore. See MediaWiki Engineering Group instead since 2023. |
- Summary
Implement multi-DC-aware technologies in MediaWiki to ensure read-after-write consistency
- Significance and Motivation
The Chronology Protector mechanism was developed for a single active data center. There are concerns whether it will
- Outcomes
MediaWiki uses or can use pt-heartbeat to give more information about replication lag between data centers.
- Baseline Metrics
MediaWiki uses Chronology Protector for managing read-after-write consistency, which may not be sufficient for active-active data center.
- Target Metrics
Read-after-write consistency in multi-DC environment
- Stakeholders
Performance SRE
- Known Dependencies/Blockers
None given
Subpages