Change Details

This task has been created by DC Ops for #serviceops implementation tracking (per serviceops request when filing racking tasks.) Once racking task T363212 has been completed, this task can be taken by service ops for implementation. Please note this task is not monitored by DC ops and any questions should be directed to the racking task. The process for replacing brokers is described in https://wikitech.wikimedia.org/wiki/Kafka/Administration#Hardware_replace_a_broker Before replacing the first broker here, give traffic a headsup so they can monitor for high latency of cache purges (purged). We saw that happening during {T363210} but I think this is not an issue anymore with the transfer.py approach. [x] kafka-main1006 [] kafka-main1007 [] kafka-main1008 [] kafka-main1009 [] kafka-main1010

This task has been created by DC Ops for #serviceops implementation tracking (per serviceops request when filing racking tasks.) Once racking task T363212 has been completed, this task can be taken by service ops for implementation. Please note this task is not monitored by DC ops and any questions should be directed to the racking task. The process for replacing brokers is described in https://wikitech.wikimedia.org/wiki/Kafka/Administration#Hardware_replace_a_broker Before replacing the first broker here, give traffic a headsup so they can monitor for high latency of cache purges (purged). We saw that happening during {T363210} but I think this is not an issue anymore with the transfer.py approach. [x] kafka-main1006 [x] kafka-main1007 [] kafka-main1008 [] kafka-main1009 [] kafka-main1010

This task has been created by DC Ops for #serviceops implementation tracking (per serviceops request when filing racking tasks.) Once racking task T363212 has been completed, this task can be taken by service ops for implementation. Please note this task is not monitored by DC ops and any questions should be directed to the racking task. The process for replacing brokers is described in https://wikitech.wikimedia.org/wiki/Kafka/Administration#Hardware_replace_a_broker Before replacing the first broker here, give traffic a headsup so they can monitor for high latency of cache purges (purged). We saw that happening during {T363210} but I think this is not an issue anymore with the transfer.py approach. [x] kafka-main1006 [x] kafka-main1007 [] kafka-main1008 [] kafka-main1009 [] kafka-main1010