This is required to ensure RESTBase has stored content from both Parsoid/PHP and Parsoid/JS as per T229018: RESTBase should be able to store Parsoid/PHP contents in Cassandra alongwith Parsoid/JS contents
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | ssastry | T229015 Tracking: Direct live production traffic at Parsoid/PHP | |||
Resolved | • mobrovac | T229018 RESTBase should be able to store Parsoid/PHP contents in Cassandra alongwith Parsoid/JS contents | |||
Declined | None | T229019 ChangePropagation should mirror reparse events to both Parsoid/PHP and Parsoid/JS |
Event Timeline
Comment Actions
In order to start mirroring parses for both variants (PHP and JS) we first need Parsoid/PHP to be deployed in production to a fleet large enough to withstand the full load. Stalling until that is the case.
Comment Actions
The RESTBase module that we have prepared over in T230791 will handle mirroring and splitting the traffic, so no changes will be needed here.