Change Details

Porting the analytics EventLogging processes running on eventlog1001 from analytics Kafka to jumbo-eqiad Kafka should be relatively simple, so let's do it soon. === Steps # Create eventlogging-client-side and eventlogging-valid-mixed topics in jumbo-eqiad Kafka. # Configure varnishkafka eventlogging to use jumbo-eqiad Kafka and restart varnishkafka eventlogging processes. # Let EventLogging consume and process all remaining events in eventlogging-client-side topic in analytics Kafka. # Stop EventLogging. # Configure EventLogging processes to use jumbo-eqiad Kafka. # Start EventLogging. # Let webperf consumer on hafnium consume remaining events in analytics Kafka. # Configure webperf consumer to use jumbo-eqiad Kafka and restart webperf on hafnium. # Let EventLogging Camus job consume all remaining EventLogging events in analytics Kafka. # Configure new EventLogging Camus job to consume from jumbo-eqiad Kafka. This will require a new camus history directory in the camus properties, as there will be new offsets to work from in jumbo-eqiad. # Configure EventLogging analytics grafana dashboards to use jumbo-eqiad.

Porting the analytics EventLogging processes running on eventlog1001 from analytics Kafka to jumbo-eqiad Kafka should be relatively simple, so let's do it soon. === Steps [x] Create eventlogging-client-side and eventlogging-valid-mixed topics in jumbo-eqiad Kafka. [] Configure varnishkafka eventlogging to use jumbo-eqiad Kafka and restart varnishkafka eventlogging processes. [] Let EventLogging consume and process all remaining events in eventlogging-client-side topic in analytics Kafka. [] Stop EventLogging. [] Configure EventLogging processes to use jumbo-eqiad Kafka. [] Start EventLogging. [] Let webperf consumer on hafnium consume remaining events in analytics Kafka. [] Configure webperf consumer to use jumbo-eqiad Kafka and restart webperf on hafnium. [] Let EventLogging Camus job consume all remaining EventLogging events in analytics Kafka. [] Configure new EventLogging Camus job to consume from jumbo-eqiad Kafka. This will require a new camus history directory in the camus properties, as there will be new offsets to work from in jumbo-eqiad. [] Configure EventLogging analytics grafana dashboa

Porting the analytics EventLogging processes running on eventlog1001 from analytics Kafka to jumbo-eqiad Kafka should be relatively simple, so let's do it soon. === Steps #[x] Create eventlogging-client-side and eventlogging-valid-mixed topics in jumbo-eqiad Kafka. #[] Configure varnishkafka eventlogging to use jumbo-eqiad Kafka and restart varnishkafka eventlogging processes. #[] Let EventLogging consume and process all remaining events in eventlogging-client-side topic in analytics Kafka. #[] Stop EventLogging. #[] Configure EventLogging processes to use jumbo-eqiad Kafka. #[] Start EventLogging. #[] Let webperf consumer on hafnium consume remaining events in analytics Kafka. #[] Configure webperf consumer to use jumbo-eqiad Kafka and restart webperf on hafnium. #[] Let EventLogging Camus job consume all remaining EventLogging events in analytics Kafka. #[] Configure new EventLogging Camus job to consume from jumbo-eqiad Kafka. This will require a new camus history directory in the camus properties, as there will be new offsets to work from in jumbo-eqiad. #[] Configure EventLogging analytics grafana dashboards to use jumbo-eqiad.