This will cause a some duplicates to be present during the time that both camus jobs are running, but should not cause any loss as long as both jumbo and analytics replcas are relatively caught up.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | elukey | T166833 Produce webrequests from varnishkafka to Kafka with Kafka message timestamp set to configurable content field | |||
| Resolved | Ottomata | T152015 Provision new Kafka cluster(s) with security features | |||
| Resolved | Lucas_Werkmeister_WMDE | T145712 Use RDF statement counts from entity data, not page props ( wikibase:identifiers, wikibase:statements and wikibase:sitelinks ) | |||
| Resolved | Ottomata | T161731 Create reliable change stream for specific wiki | |||
| Resolved | Ottomata | T183303 Decomission old analytics kafka cluster | |||
| Resolved | Ottomata | T175461 Port Kafka clients to new jumbo cluster | |||
| Resolved | Ottomata | T189713 Migrate eventbus camus to Kafka jumbo |
Change 419493 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/puppet@production] Migrate eventbus camus job to Kafka jumbo
Change 419493 merged by Ottomata:
[operations/puppet@production] Migrate eventbus camus job to Kafka jumbo
Change 441254 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/puppet@production] Move camus mediawiki_job to use kafka jumbo instead of analytics
Change 441254 merged by Ottomata:
[operations/puppet@production] Move camus mediawiki_job to use kafka jumbo instead of analytics