Core Platform Team/Initiative/Multi-DC Replication Lag/Initiative Description
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
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
- Known Dependencies/Blockers