[2025-02-10 01:56:47,899] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 0 (state.change.logger)
[2025-02-10 01:56:47,938] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 1 for 960 partitions (state.change.logger)
[2025-02-10 01:56:48,501] INFO [Broker id=3] Follower -uve-topic-22-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,501] INFO [Broker id=3] Follower -uve-topic-23-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,501] INFO [Broker id=3] Follower -uve-topic-17-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-16-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-29-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-2-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-18-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-27-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-14-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-5-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,502] INFO [Broker id=3] Follower -uve-topic-16-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,503] INFO [Broker id=3] Follower -uve-topic-29-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,503] INFO [Broker id=3] Follower -uve-topic-17-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,503] INFO [Broker id=3] Follower -uve-topic-21-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,503] INFO [Broker id=3] Follower -uve-topic-11-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,503] INFO [Broker id=3] Follower -uve-topic-24-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,503] INFO [Broker id=3] Follower -uve-topic-13-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,503] INFO [Broker id=3] Follower -uve-topic-26-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,504] INFO [Broker id=3] Follower -uve-topic-8-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,504] INFO [Broker id=3] Follower -uve-topic-0-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,504] INFO [Broker id=3] Follower -uve-topic-17-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,504] INFO [Broker id=3] Follower -uve-topic-9-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,504] INFO [Broker id=3] Follower -uve-topic-0-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,504] INFO [Broker id=3] Follower -uve-topic-20-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,504] INFO [Broker id=3] Follower -uve-topic-1-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,505] INFO [Broker id=3] Follower -uve-topic-3-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,505] INFO [Broker id=3] Follower -uve-topic-2-0 starts at leader epoch 2 from offset 466 with high watermark 465. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,505] INFO [Broker id=3] Follower -uve-topic-7-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,505] INFO [Broker id=3] Follower -uve-topic-6-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,505] INFO [Broker id=3] Follower -uve-topic-15-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,505] INFO [Broker id=3] Follower -uve-topic-28-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,506] INFO [Broker id=3] Follower -uve-topic-6-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,506] INFO [Broker id=3] Follower -uve-topic-7-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,506] INFO [Broker id=3] Follower -uve-topic-22-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,506] INFO [Broker id=3] Follower -uve-topic-0-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,506] INFO [Broker id=3] Follower -uve-topic-9-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,506] INFO [Broker id=3] Follower -uve-topic-21-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,506] INFO [Broker id=3] Follower structured_syslog_topic-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,507] INFO [Broker id=3] Follower -uve-topic-5-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,507] INFO [Broker id=3] Follower -uve-topic-4-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,507] INFO [Broker id=3] Follower -uve-topic-17-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,507] INFO [Broker id=3] Follower -uve-topic-8-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,507] INFO [Broker id=3] Follower -uve-topic-3-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,507] INFO [Broker id=3] Follower -uve-topic-4-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,507] INFO [Broker id=3] Follower -uve-topic-10-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,508] INFO [Broker id=3] Follower -uve-topic-23-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,508] INFO [Broker id=3] Follower -uve-topic-25-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,508] INFO [Broker id=3] Follower -uve-topic-20-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,508] INFO [Broker id=3] Follower -uve-topic-12-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,508] INFO [Broker id=3] Follower -uve-topic-19-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,508] INFO [Broker id=3] Follower -uve-topic-29-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,509] INFO [Broker id=3] Follower -uve-topic-16-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,513] INFO [Broker id=3] Follower -uve-topic-8-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,514] INFO [Broker id=3] Follower -uve-topic-21-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,515] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-14 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,515] INFO [Broker id=3] Follower -uve-topic-2-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,515] INFO [Broker id=3] Follower -uve-topic-9-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,517] INFO [Broker id=3] Follower -uve-topic-18-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,518] INFO [Broker id=3] Follower -uve-topic-10-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,518] INFO [Broker id=3] Follower -uve-topic-23-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,518] INFO [Broker id=3] Follower -uve-topic-14-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,519] INFO [Broker id=3] Follower -uve-topic-27-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,520] INFO [Broker id=3] Follower -uve-topic-7-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,521] INFO [Broker id=3] Follower -uve-topic-6-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,523] INFO [Broker id=3] Follower -uve-topic-8-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,523] INFO [Broker id=3] Follower -uve-topic-21-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,524] INFO [Broker id=3] Follower -uve-topic-20-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,524] INFO [Broker id=3] Follower -uve-topic-0-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,525] INFO [Broker id=3] Follower -uve-topic-17-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,526] INFO [Broker id=3] Follower -uve-topic-29-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,527] INFO [Broker id=3] Follower -uve-topic-16-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,529] INFO [Broker id=3] Follower -uve-topic-4-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,530] INFO [Broker id=3] Follower -uve-topic-13-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,530] INFO [Broker id=3] Follower -uve-topic-26-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,530] INFO [Broker id=3] Follower -uve-topic-6-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,530] INFO [Broker id=3] Follower -uve-topic-5-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,531] INFO [Broker id=3] Follower -uve-topic-12-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,533] INFO [Broker id=3] Follower -uve-topic-26-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,534] INFO [Broker id=3] Follower -uve-topic-25-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,534] INFO [Broker id=3] Follower -uve-topic-29-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,534] INFO [Broker id=3] Follower -uve-topic-16-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,534] INFO [Broker id=3] Follower -uve-topic-10-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,534] INFO [Broker id=3] Follower -uve-topic-23-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,534] INFO [Broker id=3] Follower -uve-topic-19-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,534] INFO [Broker id=3] Follower -uve-topic-25-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-11-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-24-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-19-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-28-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-15-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-20-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-29-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-16-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,535] INFO [Broker id=3] Follower -uve-topic-7-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-8-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-22-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-18-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-24-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-11-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-17-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-22-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower -uve-topic-1-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,536] INFO [Broker id=3] Follower structured_syslog_topic-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,537] INFO [Broker id=3] Follower -uve-topic-5-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,540] INFO [Broker id=3] Follower -uve-topic-15-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,540] INFO [Broker id=3] Follower -uve-topic-28-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,540] INFO [Broker id=3] Follower -uve-topic-20-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,542] INFO [Broker id=3] Follower -uve-topic-21-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,542] INFO [Broker id=3] Follower -uve-topic-7-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,542] INFO [Broker id=3] Follower -uve-topic-3-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,542] INFO [Broker id=3] Follower -uve-topic-8-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,543] INFO [Broker id=3] Follower -uve-topic-21-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,543] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-11 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,543] INFO [Broker id=3] Follower -uve-topic-0-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,543] INFO [Broker id=3] Follower -uve-topic-24-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower -uve-topic-23-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower -uve-topic-11-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower -uve-topic-10-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower -uve-topic-19-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower -uve-topic-20-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower -uve-topic-3-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-8 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,544] INFO [Broker id=3] Follower -uve-topic-7-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower -uve-topic-17-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower -uve-topic-16-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower -uve-topic-29-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower -uve-topic-0-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower structured_syslog_topic-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower -uve-topic-9-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower -uve-topic-6-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,545] INFO [Broker id=3] Follower -uve-topic-26-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-13-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-5-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-7-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-8-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-19-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-4-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-25-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-20-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,546] INFO [Broker id=3] Follower -uve-topic-12-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-27 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-16-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-29-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-8-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-18-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-1-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-22-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-23-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-10-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,547] INFO [Broker id=3] Follower -uve-topic-2-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-18-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-27-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-14-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-15-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-28-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-28-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-27-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-14-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,548] INFO [Broker id=3] Follower -uve-topic-8-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,549] INFO [Broker id=3] Follower -uve-topic-22-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,549] INFO [Broker id=3] Follower -uve-topic-16-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,549] INFO [Broker id=3] Follower -uve-topic-15-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,549] INFO [Broker id=3] Follower -uve-topic-29-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,549] INFO [Broker id=3] Follower -uve-topic-28-0 starts at leader epoch 3 from offset 682 with high watermark 682. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,549] INFO [Broker id=3] Follower -uve-topic-21-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,553] INFO [Broker id=3] Follower -uve-topic-17-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-20-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-21-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower structured_syslog_topic-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-25-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-12-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-24-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-11-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-26-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,554] INFO [Broker id=3] Follower -uve-topic-13-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-15-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-28-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-20-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-7-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-3-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-19-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-23-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,555] INFO [Broker id=3] Follower -uve-topic-10-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,556] INFO [Broker id=3] Follower -uve-topic-25-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,556] INFO [Broker id=3] Follower -uve-topic-12-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,556] INFO [Broker id=3] Follower -uve-topic-24-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,556] INFO [Broker id=3] Follower -uve-topic-11-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,556] INFO [Broker id=3] Follower -uve-topic-15-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,557] INFO [Broker id=3] Follower -uve-topic-28-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,557] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-5 starts at leader epoch 3 from offset 6 with high watermark 6. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,557] INFO [Broker id=3] Follower -uve-topic-20-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,557] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-24 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,557] INFO [Broker id=3] Follower -uve-topic-6-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,557] INFO [Broker id=3] Follower -uve-topic-9-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,557] INFO [Broker id=3] Follower -uve-topic-19-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-18-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-22-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-10-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-23-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-18-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-17-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-22-0 starts at leader epoch 3 from offset 1991 with high watermark 1989. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-14-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-27-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,558] INFO [Broker id=3] Follower -uve-topic-5-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,559] INFO [Broker id=3] Follower -uve-topic-21-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,559] INFO [Broker id=3] Follower -uve-topic-28-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,559] INFO [Broker id=3] Follower -uve-topic-15-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,559] INFO [Broker id=3] Follower -uve-topic-16-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,559] INFO [Broker id=3] Follower -uve-topic-17-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,559] INFO [Broker id=3] Follower -uve-topic-13-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,560] INFO [Broker id=3] Follower -uve-topic-12-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,560] INFO [Broker id=3] Follower -uve-topic-25-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,561] INFO [Broker id=3] Follower -uve-topic-26-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,561] INFO [Broker id=3] Follower -uve-topic-14-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,561] INFO [Broker id=3] Follower -uve-topic-27-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,561] INFO [Broker id=3] Follower -uve-topic-7-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,561] INFO [Broker id=3] Follower -uve-topic-2-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-14-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-27-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-28-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-15-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-7-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-0-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-1-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-2-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,562] INFO [Broker id=3] Follower -uve-topic-9-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,563] INFO [Broker id=3] Follower -uve-topic-8-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,563] INFO [Broker id=3] Follower structured_syslog_topic-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,563] INFO [Broker id=3] Follower -uve-topic-1-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,566] INFO [Broker id=3] Follower -uve-topic-0-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,566] INFO [Broker id=3] Follower structured_syslog_topic-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,566] INFO [Broker id=3] Follower -uve-topic-4-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,569] INFO [Broker id=3] Follower -uve-topic-13-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,569] INFO [Broker id=3] Follower -uve-topic-26-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,569] INFO [Broker id=3] Follower -uve-topic-6-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,570] INFO [Broker id=3] Follower -uve-topic-8-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,570] INFO [Broker id=3] Follower -uve-topic-7-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,570] INFO [Broker id=3] Follower -uve-topic-20-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,570] INFO [Broker id=3] Follower -uve-topic-11-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,570] INFO [Broker id=3] Follower -uve-topic-24-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-29-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-16-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-3-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-11-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-4-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-5-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-6-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-2-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,571] INFO [Broker id=3] Follower -uve-topic-1-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,572] INFO [Broker id=3] Follower -uve-topic-18-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,572] INFO [Broker id=3] Follower structured_syslog_topic-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,572] INFO [Broker id=3] Follower -uve-topic-3-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,572] INFO [Broker id=3] Follower -uve-topic-2-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,572] INFO [Broker id=3] Follower -uve-topic-14-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower -uve-topic-27-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower -uve-topic-28-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower -uve-topic-15-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower -uve-topic-8-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower -uve-topic-1-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower -uve-topic-0-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower -uve-topic-20-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,573] INFO [Broker id=3] Follower structured_syslog_topic-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,574] INFO [Broker id=3] Follower -uve-topic-9-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,574] INFO [Broker id=3] Follower -uve-topic-22-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,574] INFO [Broker id=3] Follower -uve-topic-13-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,575] INFO [Broker id=3] Follower -uve-topic-12-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,575] INFO [Broker id=3] Follower -uve-topic-25-0 starts at leader epoch 3 from offset 925 with high watermark 925. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,575] INFO [Broker id=3] Follower -uve-topic-26-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,575] INFO [Broker id=3] Follower -uve-topic-5-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,576] INFO [Broker id=3] Follower -uve-topic-12-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,576] INFO [Broker id=3] Follower -uve-topic-25-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,577] INFO [Broker id=3] Follower -uve-topic-13-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,577] INFO [Broker id=3] Follower -uve-topic-26-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,577] INFO [Broker id=3] Follower -uve-topic-7-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,577] INFO [Broker id=3] Follower -uve-topic-6-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,577] INFO [Broker id=3] Follower -uve-topic-28-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,577] INFO [Broker id=3] Follower -uve-topic-15-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,577] INFO [Broker id=3] Follower -uve-topic-7-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,578] INFO [Broker id=3] Follower -uve-topic-19-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,579] INFO [Broker id=3] Follower -uve-topic-10-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,580] INFO [Broker id=3] Follower -uve-topic-11-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,580] INFO [Broker id=3] Follower -uve-topic-24-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,580] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-21 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,580] INFO [Broker id=3] Follower -uve-topic-19-0 starts at leader epoch 3 from offset 140 with high watermark 140. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,580] INFO [Broker id=3] Follower structured_syslog_topic-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,580] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,581] INFO [Broker id=3] Follower -uve-topic-14-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,581] INFO [Broker id=3] Follower -uve-topic-27-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-10-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-23-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-17-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-9-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-14-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-27-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-6-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,582] INFO [Broker id=3] Follower -uve-topic-29-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,583] INFO [Broker id=3] Follower -uve-topic-16-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,583] INFO [Broker id=3] Follower -uve-topic-21-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,583] INFO [Broker id=3] Follower -uve-topic-0-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,583] INFO [Broker id=3] Follower -uve-topic-4-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,583] INFO [Broker id=3] Follower -uve-topic-8-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,586] INFO [Broker id=3] Follower -uve-topic-28-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,588] INFO [Broker id=3] Follower -uve-topic-14-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,588] INFO [Broker id=3] Follower -uve-topic-27-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,588] INFO [Broker id=3] Follower -uve-topic-29-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,592] INFO [Broker id=3] Follower -uve-topic-16-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,592] INFO [Broker id=3] Follower -uve-topic-10-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,592] INFO [Broker id=3] Follower -uve-topic-23-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,592] INFO [Broker id=3] Follower -uve-topic-12-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower -uve-topic-25-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-18 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower -uve-topic-27-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower -uve-topic-13-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower -uve-topic-26-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower -uve-topic-18-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower -uve-topic-9-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,593] INFO [Broker id=3] Follower -uve-topic-0-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,594] INFO [Broker id=3] Follower -uve-topic-1-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,594] INFO [Broker id=3] Follower -uve-topic-2-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,594] INFO [Broker id=3] Follower structured_syslog_topic-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,594] INFO [Broker id=3] Follower -uve-topic-6-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,595] INFO [Broker id=3] Follower -uve-topic-5-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,595] INFO [Broker id=3] Follower -uve-topic-14-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,595] INFO [Broker id=3] Follower -uve-topic-27-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,595] INFO [Broker id=3] Follower -uve-topic-5-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,596] INFO [Broker id=3] Follower -uve-topic-13-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,596] INFO [Broker id=3] Follower -uve-topic-6-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,596] INFO [Broker id=3] Follower -uve-topic-7-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,596] INFO [Broker id=3] Follower -uve-topic-8-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,596] INFO [Broker id=3] Follower -uve-topic-20-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,596] INFO [Broker id=3] Follower -uve-topic-11-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,605] INFO [Broker id=3] Follower -uve-topic-24-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower -uve-topic-4-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower -uve-topic-3-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower structured_syslog_topic-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower -uve-topic-5-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower -uve-topic-7-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower -uve-topic-13-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower -uve-topic-26-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,606] INFO [Broker id=3] Follower -uve-topic-6-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-3-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-2-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-22-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-19-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower structured_syslog_topic-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-14-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-9-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-8-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,607] INFO [Broker id=3] Follower -uve-topic-21-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,620] INFO [Broker id=3] Follower -uve-topic-28-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,621] INFO [Broker id=3] Follower -uve-topic-15-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,621] INFO [Broker id=3] Follower -uve-topic-1-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,621] INFO [Broker id=3] Follower -uve-topic-0-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,621] INFO [Broker id=3] Follower -uve-topic-17-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,621] INFO [Broker id=3] Follower structured_syslog_topic-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,621] INFO [Broker id=3] Follower -uve-topic-13-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,621] INFO [Broker id=3] Follower -uve-topic-26-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,628] INFO [Broker id=3] Follower -uve-topic-4-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,632] INFO [Broker id=3] Follower structured_syslog_topic-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,633] INFO [Broker id=3] Follower -uve-topic-28-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,633] INFO [Broker id=3] Follower -uve-topic-15-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,633] INFO [Broker id=3] Follower -uve-topic-0-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,633] INFO [Broker id=3] Follower -uve-topic-7-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-20-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-28-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-15-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-12-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-25-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-3-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-19-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,634] INFO [Broker id=3] Follower -uve-topic-4-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,635] INFO [Broker id=3] Follower -uve-topic-11-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,635] INFO [Broker id=3] Follower -uve-topic-24-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,635] INFO [Broker id=3] Follower structured_syslog_topic-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,635] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-15 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,635] INFO [Broker id=3] Follower -uve-topic-6-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,635] INFO [Broker id=3] Follower -uve-topic-13-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-26-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-14-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-27-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-18-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-22-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-10-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-23-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-6-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,636] INFO [Broker id=3] Follower -uve-topic-20-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,637] INFO [Broker id=3] Follower -uve-topic-21-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,637] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-25 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,637] INFO [Broker id=3] Follower -uve-topic-16-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,637] INFO [Broker id=3] Follower -uve-topic-29-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-21-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-4-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-27-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-14-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-16-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-29-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-2-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-2-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,638] INFO [Broker id=3] Follower -uve-topic-1-0 starts at leader epoch 3 from offset 464 with high watermark 464. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-3-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-26-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-13-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-5-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-9-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-17-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-1-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-8-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower structured_syslog_topic-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-5-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,639] INFO [Broker id=3] Follower -uve-topic-22-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-26-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-13-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-5-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-16-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-29-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-15-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-28-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-8-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-5-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-4-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-24-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-11-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,640] INFO [Broker id=3] Follower -uve-topic-4-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,641] INFO [Broker id=3] Follower structured_syslog_topic-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,641] INFO [Broker id=3] Follower -uve-topic-5-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,641] INFO [Broker id=3] Follower -uve-topic-7-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,641] INFO [Broker id=3] Follower -uve-topic-18-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,642] INFO [Broker id=3] Follower -uve-topic-1-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,643] INFO [Broker id=3] Follower -uve-topic-3-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,643] INFO [Broker id=3] Follower -uve-topic-19-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,643] INFO [Broker id=3] Follower structured_syslog_topic-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,644] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-12 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,644] INFO [Broker id=3] Follower -uve-topic-4-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,644] INFO [Broker id=3] Follower -uve-topic-25-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,644] INFO [Broker id=3] Follower -uve-topic-26-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,645] INFO [Broker id=3] Follower -uve-topic-12-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,647] INFO [Broker id=3] Follower -uve-topic-13-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,647] INFO [Broker id=3] Follower -uve-topic-4-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-0-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-17-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-16-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-29-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-2-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-22-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-9-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower -uve-topic-21-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,648] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-3 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,649] INFO [Broker id=3] Follower -uve-topic-17-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,649] INFO [Broker id=3] Follower -uve-topic-26-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,649] INFO [Broker id=3] Follower -uve-topic-13-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,649] INFO [Broker id=3] Follower -uve-topic-15-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,649] INFO [Broker id=3] Follower -uve-topic-28-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,649] INFO [Broker id=3] Follower -uve-topic-20-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,650] INFO [Broker id=3] Follower -uve-topic-21-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,650] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 2 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,650] INFO [Broker id=3] Follower -uve-topic-27-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,650] INFO [Broker id=3] Follower -uve-topic-14-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,651] INFO [Broker id=3] Follower -uve-topic-25-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,651] INFO [Broker id=3] Follower -uve-topic-19-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,651] INFO [Broker id=3] Follower -uve-topic-20-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,651] INFO [Broker id=3] Follower -uve-topic-10-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-24-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-23-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-25-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-12-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-27-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-26-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-13-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,652] INFO [Broker id=3] Follower -uve-topic-14-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-6-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-10-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-22-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-23-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-18-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-5-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-25-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-12-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-18-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,653] INFO [Broker id=3] Follower -uve-topic-17-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower -uve-topic-20-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower -uve-topic-21-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-19 starts at leader epoch 2 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower -uve-topic-22-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower -uve-topic-17-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower -uve-topic-16-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower -uve-topic-29-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower -uve-topic-21-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,654] INFO [Broker id=3] Follower structured_syslog_topic-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-20-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-27-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-14-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-16-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-15-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-29-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-28-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-0 starts at leader epoch 3 from offset 6 with high watermark 6. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-25-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-12-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,655] INFO [Broker id=3] Follower -uve-topic-24-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-11-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-26-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-13-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-12-0 starts at leader epoch 3 from offset 137 with high watermark 137. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-13-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-5-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-6-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-9-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-1-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,656] INFO [Broker id=3] Follower -uve-topic-8-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,657] INFO [Broker id=3] Follower -uve-topic-15-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,657] INFO [Broker id=3] Follower -uve-topic-28-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,657] INFO [Broker id=3] Follower -uve-topic-0-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,657] INFO [Broker id=3] Follower -uve-topic-7-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,657] INFO [Broker id=3] Follower -uve-topic-4-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower -uve-topic-3-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower -uve-topic-25-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower -uve-topic-12-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower -uve-topic-19-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower structured_syslog_topic-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-9 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower -uve-topic-7-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,658] INFO [Broker id=3] Follower -uve-topic-6-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-10-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-27-0 starts at leader epoch 3 from offset 1247 with high watermark 1246. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-23-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-14-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-2-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-18-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-19-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-22-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,659] INFO [Broker id=3] Follower -uve-topic-24-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower -uve-topic-11-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower -uve-topic-10-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower -uve-topic-23-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-28 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower -uve-topic-4-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower -uve-topic-25-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower -uve-topic-12-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,660] INFO [Broker id=3] Follower -uve-topic-5-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-4-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-17-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-0-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-1-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-16-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-2-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-9-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-25-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-12-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-4-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-3-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,661] INFO [Broker id=3] Follower -uve-topic-3-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-0-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-15-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-6-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-7-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-8-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-21-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-25-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,662] INFO [Broker id=3] Follower -uve-topic-12-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-19-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-24-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-11-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-4-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-24-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-11-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-5-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-6-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-27-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-14-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,663] INFO [Broker id=3] Follower -uve-topic-18-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,664] INFO [Broker id=3] Follower -uve-topic-19-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,664] INFO [Broker id=3] Follower -uve-topic-10-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,664] INFO [Broker id=3] Follower -uve-topic-22-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,664] INFO [Broker id=3] Follower -uve-topic-23-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-18-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-24-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-11-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-26-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-13-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-25-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-20-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,665] INFO [Broker id=3] Follower -uve-topic-12-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,666] INFO [Broker id=3] Follower -uve-topic-22-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,667] INFO [Broker id=3] Follower -uve-topic-16-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,667] INFO [Broker id=3] Follower -uve-topic-29-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,667] INFO [Broker id=3] Follower -uve-topic-21-0 starts at leader epoch 3 from offset 1591 with high watermark 1591. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,667] INFO [Broker id=3] Follower -uve-topic-8-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,667] INFO [Broker id=3] Follower -uve-topic-17-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,667] INFO [Broker id=3] Follower -uve-topic-15-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,668] INFO [Broker id=3] Follower -uve-topic-28-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,668] INFO [Broker id=3] Follower -uve-topic-7-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,668] INFO [Broker id=3] Follower -uve-topic-10-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,668] INFO [Broker id=3] Follower -uve-topic-23-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,668] INFO [Broker id=3] Follower -uve-topic-1-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,668] INFO [Broker id=3] Follower -uve-topic-3-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower structured_syslog_topic-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-5-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-6 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-4-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-9-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-9-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-19-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-13 starts at leader epoch 2 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-17-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-8-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-1-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-0-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,669] INFO [Broker id=3] Follower -uve-topic-24-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-5-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-7-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-6-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-23-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-10-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-3-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-2-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-18-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-19-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-4-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,670] INFO [Broker id=3] Follower -uve-topic-5-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-6-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-25-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-12-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-0-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-4-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-2-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-18-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-1-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-9-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-21-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-3-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-23-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-24-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,671] INFO [Broker id=3] Follower -uve-topic-11-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,672] INFO [Broker id=3] Follower -uve-topic-15-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,672] INFO [Broker id=3] Follower -uve-topic-3-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,672] INFO [Broker id=3] Follower -uve-topic-28-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,672] INFO [Broker id=3] Follower -uve-topic-8-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,672] INFO [Broker id=3] Follower -uve-topic-20-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,672] INFO [Broker id=3] Follower -uve-topic-7-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,672] INFO [Broker id=3] Follower -uve-topic-27-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,673] INFO [Broker id=3] Follower -uve-topic-14-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,673] INFO [Broker id=3] Follower -uve-topic-16-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,674] INFO [Broker id=3] Follower -uve-topic-29-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,674] INFO [Broker id=3] Follower -uve-topic-24-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,674] INFO [Broker id=3] Follower -uve-topic-11-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,674] INFO [Broker id=3] Follower -uve-topic-19-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,674] INFO [Broker id=3] Follower -uve-topic-24-0 starts at leader epoch 3 from offset 353 with high watermark 353. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,674] INFO [Broker id=3] Follower -uve-topic-11-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower -uve-topic-3-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower structured_syslog_topic-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower -uve-topic-26-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower -uve-topic-13-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower -uve-topic-22-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower -uve-topic-10-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower structured_syslog_topic-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,675] INFO [Broker id=3] Follower -uve-topic-5-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,676] INFO [Broker id=3] Follower -uve-topic-25-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,676] INFO [Broker id=3] Follower -uve-topic-12-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,676] INFO [Broker id=3] Follower -uve-topic-24-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower -uve-topic-11-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower -uve-topic-26-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower -uve-topic-13-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower -uve-topic-17-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower -uve-topic-20-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-29 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower -uve-topic-22-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,680] INFO [Broker id=3] Follower -uve-topic-9-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-19-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-18-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-24-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-23-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-11-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-10-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-3-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-19-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-23-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-10-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-15-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-28-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-21-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 2 from offset 5 with high watermark 5. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-6-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,681] INFO [Broker id=3] Follower -uve-topic-19-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-3-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-26-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-1-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-9-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-0-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-1-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-2-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-25-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-12-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-4-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-8-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,682] INFO [Broker id=3] Follower -uve-topic-0-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-16-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-29-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-7-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-8-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-2-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-27-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-6-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-7-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-27-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-14-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-2-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-24-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-11-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,683] INFO [Broker id=3] Follower -uve-topic-18-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-3-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-23-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-10-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-4-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-1-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-6-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-0-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-9-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-16-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-29-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-2-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,684] INFO [Broker id=3] Follower -uve-topic-1-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,685] INFO [Broker id=3] Follower -uve-topic-18-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,685] INFO [Broker id=3] Follower -uve-topic-3-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,685] INFO [Broker id=3] Follower -uve-topic-19-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,685] INFO [Broker id=3] Follower -uve-topic-25-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,685] INFO [Broker id=3] Follower -uve-topic-12-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,685] INFO [Broker id=3] Follower -uve-topic-24-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,685] INFO [Broker id=3] Follower -uve-topic-11-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-15-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-29-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-28-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-8-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-20-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-21-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-18-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower structured_syslog_topic-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-5-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-27-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-14-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,686] INFO [Broker id=3] Follower -uve-topic-7-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-20-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-27-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-26-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-13-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-14-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-23-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-10-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-19-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-22-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower structured_syslog_topic-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-24-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-11-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-26-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-25-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-12-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,687] INFO [Broker id=3] Follower -uve-topic-13-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,690] INFO [Broker id=3] Follower -uve-topic-21-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,690] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-7 starts at leader epoch 2 from offset 5 with high watermark 5. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,690] INFO [Broker id=3] Follower -uve-topic-17-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-9-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-23-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-0-0 starts at leader epoch 3 from offset 2857 with high watermark 2846. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-10-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-18-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-19-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-23-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-10-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-2-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,691] INFO [Broker id=3] Follower -uve-topic-28-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,695] INFO [Broker id=3] Follower -uve-topic-15-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,695] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-26 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,695] INFO [Broker id=3] Follower -uve-topic-2-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,695] INFO [Broker id=3] Follower -uve-topic-13-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-26-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-12-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-25-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-14-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-27-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-10-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-23-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-12-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-25-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-11-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-24-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,696] INFO [Broker id=3] Follower -uve-topic-4-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,697] INFO [Broker id=3] Follower -uve-topic-8-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,697] INFO [Broker id=3] Follower -uve-topic-0-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,697] INFO [Broker id=3] Follower -uve-topic-18-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,698] INFO [Broker id=3] Follower -uve-topic-2-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,698] INFO [Broker id=3] Follower -uve-topic-1-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,699] INFO [Broker id=3] Follower structured_syslog_topic-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,699] INFO [Broker id=3] Follower -uve-topic-7-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,699] INFO [Broker id=3] Follower -uve-topic-14-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,699] INFO [Broker id=3] Follower -uve-topic-27-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,699] INFO [Broker id=3] Follower -uve-topic-6-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,699] INFO [Broker id=3] Follower -uve-topic-2-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,699] INFO [Broker id=3] Follower -uve-topic-18-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,700] INFO [Broker id=3] Follower -uve-topic-5-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,700] INFO [Broker id=3] Follower -uve-topic-9-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,700] INFO [Broker id=3] Follower -uve-topic-22-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,700] INFO [Broker id=3] Follower -uve-topic-13-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,700] INFO [Broker id=3] Follower -uve-topic-26-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,700] INFO [Broker id=3] Follower -uve-topic-1-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,703] INFO [Broker id=3] Follower -uve-topic-17-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-18-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-21-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-20-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-22-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-3-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-19-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-10-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-11-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-23-0 starts at leader epoch 2 from offset 545 with high watermark 540. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,704] INFO [Broker id=3] Follower -uve-topic-24-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,705] INFO [Broker id=3] Follower -uve-topic-28-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,705] INFO [Broker id=3] Follower -uve-topic-3-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,705] INFO [Broker id=3] Follower -uve-topic-15-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-23 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-19-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-17-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-20-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-29-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-16-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-21-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-28-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-29-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-15-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-16-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-9-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-1-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-23-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-10-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower structured_syslog_topic-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-2-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-22-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,706] INFO [Broker id=3] Follower -uve-topic-18-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,707] INFO [Broker id=3] Follower -uve-topic-6-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,707] INFO [Broker id=3] Follower -uve-topic-5-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,707] INFO [Broker id=3] Follower -uve-topic-14-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,707] INFO [Broker id=3] Follower -uve-topic-27-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,707] INFO [Broker id=3] Follower -uve-topic-7-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,707] INFO [Broker id=3] Follower -uve-topic-20-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,707] INFO [Broker id=3] Follower -uve-topic-0-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-9-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-1-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-17-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower structured_syslog_topic-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-5-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-4-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-11-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-24-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,710] INFO [Broker id=3] Follower -uve-topic-13-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-12-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-26-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-29-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-16-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-17-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-22-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-18-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-21-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-1 starts at leader epoch 2 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-17-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-23-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,711] INFO [Broker id=3] Follower -uve-topic-10-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,713] INFO [Broker id=3] Follower -uve-topic-12-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,713] INFO [Broker id=3] Follower -uve-topic-25-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,713] INFO [Broker id=3] Follower -uve-topic-11-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,713] INFO [Broker id=3] Follower -uve-topic-19-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,713] INFO [Broker id=3] Follower -uve-topic-21-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,713] INFO [Broker id=3] Follower -uve-topic-20-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,713] INFO [Broker id=3] Follower -uve-topic-28-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-15-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-20 starts at leader epoch 3 from offset 6 with high watermark 6. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-22-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-18-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-14-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-13-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-26-0 starts at leader epoch 2 from offset 1184 with high watermark 1184. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-27-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-6-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,714] INFO [Broker id=3] Follower -uve-topic-1-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,715] INFO [Broker id=3] Follower -uve-topic-0-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,715] INFO [Broker id=3] Follower -uve-topic-22-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,715] INFO [Broker id=3] Follower -uve-topic-4-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,715] INFO [Broker id=3] Follower -uve-topic-3-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,715] INFO [Broker id=3] Follower -uve-topic-9-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,715] INFO [Broker id=3] Follower -uve-topic-28-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-29-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-15-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-16-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-8-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-2-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-3-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-9-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-2-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,716] INFO [Broker id=3] Follower -uve-topic-1-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,717] INFO [Broker id=3] Follower structured_syslog_topic-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,717] INFO [Broker id=3] Follower -uve-topic-22-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,717] INFO [Broker id=3] Follower -uve-topic-1-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,717] INFO [Broker id=3] Follower -uve-topic-0-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,718] INFO [Broker id=3] Follower -uve-topic-9-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,718] INFO [Broker id=3] Follower -uve-topic-4-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,719] INFO [Broker id=3] Follower -uve-topic-6-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,719] INFO [Broker id=3] Follower -uve-topic-5-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,719] INFO [Broker id=3] Follower -uve-topic-9-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,719] INFO [Broker id=3] Follower -uve-topic-22-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,720] INFO [Broker id=3] Follower -uve-topic-1-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,720] INFO [Broker id=3] Follower -uve-topic-17-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,720] INFO [Broker id=3] Follower -uve-topic-3-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,723] INFO [Broker id=3] Follower -uve-topic-19-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,723] INFO [Broker id=3] Follower -uve-topic-4-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,723] INFO [Broker id=3] Follower -uve-topic-5-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,723] INFO [Broker id=3] Follower -uve-topic-20-0 starts at leader epoch 3 from offset 1708 with high watermark 1708. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,723] INFO [Broker id=3] Follower -uve-topic-28-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,723] INFO [Broker id=3] Follower -uve-topic-3-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,723] INFO [Broker id=3] Follower -uve-topic-15-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-17 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower -uve-topic-8-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower -uve-topic-0-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower -uve-topic-17-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower -uve-topic-20-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower -uve-topic-29-0 starts at leader epoch 2 from offset 812 with high watermark 809. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower -uve-topic-16-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,724] INFO [Broker id=3] Follower -uve-topic-21-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-2-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-9-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-1-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-23-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-10-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-17-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower structured_syslog_topic-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-2-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-14-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-27-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-7-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-6-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-13-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-26-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,725] INFO [Broker id=3] Follower -uve-topic-14-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,726] INFO [Broker id=3] Follower -uve-topic-8-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-0-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-21-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-12-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-25-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-21-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-0-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-22-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,733] INFO [Broker id=3] Follower -uve-topic-9-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-8-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-29-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-11-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-24-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-18-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-29-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-15-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-16-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,734] INFO [Broker id=3] Follower -uve-topic-7-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 01:56:48,756] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 1 epoch 2 with correlation id 1 for 960 partitions (state.change.logger)
[2025-02-10 01:56:48,977] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 2 (state.change.logger)
[2025-02-10 01:56:49,440] INFO [Broker id=3] Add 227 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 3 (state.change.logger)
[2025-02-10 01:56:59,545] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 4 (state.change.logger)
[2025-02-10 01:58:50,183] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 5 from controller 1 for 960 partitions (state.change.logger)
[2025-02-10 01:58:50,200] INFO [Broker id=3] Stopped fetchers as part of LeaderAndIsr request correlationId 5 from controller 1 epoch 2 as part of the become-leader transition for 480 partitions (state.change.logger)
[2025-02-10 01:58:50,202] INFO [Broker id=3] Leader -uve-topic-23-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,211] INFO [Broker id=3] Leader -uve-topic-22-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,219] INFO [Broker id=3] Leader -uve-topic-16-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,223] INFO [Broker id=3] Leader -uve-topic-17-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,226] INFO [Broker id=3] Leader -uve-topic-29-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,229] INFO [Broker id=3] Leader -uve-topic-16-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,232] INFO [Broker id=3] Leader -uve-topic-11-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,234] INFO [Broker id=3] Leader -uve-topic-13-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,237] INFO [Broker id=3] Leader -uve-topic-17-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,240] INFO [Broker id=3] Leader -uve-topic-9-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,243] INFO [Broker id=3] Leader -uve-topic-20-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,246] INFO [Broker id=3] Leader -uve-topic-1-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,250] INFO [Broker id=3] Leader -uve-topic-3-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,253] INFO [Broker id=3] Leader -uve-topic-7-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,255] INFO [Broker id=3] Leader -uve-topic-6-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,257] INFO [Broker id=3] Leader -uve-topic-15-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,260] INFO [Broker id=3] Leader -uve-topic-21-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,263] INFO [Broker id=3] Leader structured_syslog_topic-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,267] INFO [Broker id=3] Leader -uve-topic-5-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,270] INFO [Broker id=3] Leader -uve-topic-8-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,272] INFO [Broker id=3] Leader -uve-topic-4-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,276] INFO [Broker id=3] Leader -uve-topic-25-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,279] INFO [Broker id=3] Leader -uve-topic-20-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,282] INFO [Broker id=3] Leader -uve-topic-12-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,290] INFO [Broker id=3] Leader -uve-topic-16-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,292] INFO [Broker id=3] Leader -uve-topic-8-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,296] INFO [Broker id=3] Leader -uve-topic-9-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,298] INFO [Broker id=3] Leader -uve-topic-14-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,301] INFO [Broker id=3] Leader -uve-topic-7-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,305] INFO [Broker id=3] Leader -uve-topic-20-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,308] INFO [Broker id=3] Leader -uve-topic-17-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,310] INFO [Broker id=3] Leader -uve-topic-16-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,315] INFO [Broker id=3] Leader -uve-topic-4-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,319] INFO [Broker id=3] Leader -uve-topic-13-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,323] INFO [Broker id=3] Leader -uve-topic-26-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,327] INFO [Broker id=3] Leader -uve-topic-25-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,331] INFO [Broker id=3] Leader -uve-topic-29-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,334] INFO [Broker id=3] Leader -uve-topic-10-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,337] INFO [Broker id=3] Leader -uve-topic-23-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,341] INFO [Broker id=3] Leader -uve-topic-25-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,344] INFO [Broker id=3] Leader -uve-topic-11-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,346] INFO [Broker id=3] Leader -uve-topic-19-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,350] INFO [Broker id=3] Leader -uve-topic-20-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,353] INFO [Broker id=3] Leader -uve-topic-16-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,357] INFO [Broker id=3] Leader -uve-topic-8-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,361] INFO [Broker id=3] Leader -uve-topic-22-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,364] INFO [Broker id=3] Leader -uve-topic-11-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,366] INFO [Broker id=3] Leader -uve-topic-24-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,371] INFO [Broker id=3] Leader -uve-topic-18-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,374] INFO [Broker id=3] Leader -uve-topic-22-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,376] INFO [Broker id=3] Leader -uve-topic-1-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,379] INFO [Broker id=3] Leader structured_syslog_topic-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,382] INFO [Broker id=3] Leader -uve-topic-5-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,385] INFO [Broker id=3] Leader -uve-topic-28-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,390] INFO [Broker id=3] Leader -uve-topic-7-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,392] INFO [Broker id=3] Leader -uve-topic-3-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,395] INFO [Broker id=3] Leader -uve-topic-8-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,398] INFO [Broker id=3] Leader -uve-topic-21-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,401] INFO [Broker id=3] Leader -uve-topic-0-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,404] INFO [Broker id=3] Leader -uve-topic-24-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,406] INFO [Broker id=3] Leader -uve-topic-3-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,409] INFO [Broker id=3] Leader -uve-topic-7-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,412] INFO [Broker id=3] Leader -uve-topic-17-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,414] INFO [Broker id=3] Leader -uve-topic-16-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,417] INFO [Broker id=3] Leader structured_syslog_topic-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,421] INFO [Broker id=3] Leader -uve-topic-26-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,426] INFO [Broker id=3] Leader -uve-topic-13-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,430] INFO [Broker id=3] Leader -uve-topic-5-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,433] INFO [Broker id=3] Leader -uve-topic-8-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,436] INFO [Broker id=3] Leader -uve-topic-19-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,439] INFO [Broker id=3] Leader -uve-topic-4-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,443] INFO [Broker id=3] Leader -uve-topic-25-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,446] INFO [Broker id=3] Leader -uve-topic-20-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,448] INFO [Broker id=3] Leader -uve-topic-12-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,452] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-27 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,455] INFO [Broker id=3] Leader -uve-topic-16-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,457] INFO [Broker id=3] Leader -uve-topic-8-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,460] INFO [Broker id=3] Leader -uve-topic-18-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,462] INFO [Broker id=3] Leader -uve-topic-1-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,465] INFO [Broker id=3] Leader -uve-topic-22-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,469] INFO [Broker id=3] Leader -uve-topic-23-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,471] INFO [Broker id=3] Leader -uve-topic-10-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,475] INFO [Broker id=3] Leader -uve-topic-27-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,479] INFO [Broker id=3] Leader -uve-topic-15-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,485] INFO [Broker id=3] Leader -uve-topic-28-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,488] INFO [Broker id=3] Leader -uve-topic-16-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,492] INFO [Broker id=3] Leader -uve-topic-29-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,497] INFO [Broker id=3] Leader -uve-topic-21-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,501] INFO [Broker id=3] Leader -uve-topic-20-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,503] INFO [Broker id=3] Leader structured_syslog_topic-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,509] INFO [Broker id=3] Leader -uve-topic-11-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,513] INFO [Broker id=3] Leader -uve-topic-13-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,515] INFO [Broker id=3] Leader -uve-topic-28-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,519] INFO [Broker id=3] Leader -uve-topic-20-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,523] INFO [Broker id=3] Leader -uve-topic-7-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,526] INFO [Broker id=3] Leader -uve-topic-10-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,531] INFO [Broker id=3] Leader -uve-topic-3-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,534] INFO [Broker id=3] Leader -uve-topic-23-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,536] INFO [Broker id=3] Leader -uve-topic-11-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,539] INFO [Broker id=3] Leader -uve-topic-25-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,542] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-24 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,544] INFO [Broker id=3] Leader -uve-topic-20-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,547] INFO [Broker id=3] Leader -uve-topic-6-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,550] INFO [Broker id=3] Leader -uve-topic-9-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,553] INFO [Broker id=3] Leader -uve-topic-19-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,557] INFO [Broker id=3] Leader -uve-topic-22-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,560] INFO [Broker id=3] Leader -uve-topic-18-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,562] INFO [Broker id=3] Leader -uve-topic-22-0 starts at leader epoch 4 from offset 2073 with high watermark 2073 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,565] INFO [Broker id=3] Leader -uve-topic-27-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,568] INFO [Broker id=3] Leader -uve-topic-5-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,570] INFO [Broker id=3] Leader -uve-topic-28-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,572] INFO [Broker id=3] Leader -uve-topic-16-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,575] INFO [Broker id=3] Leader -uve-topic-17-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,579] INFO [Broker id=3] Leader -uve-topic-25-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,591] INFO [Broker id=3] Leader -uve-topic-26-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,593] INFO [Broker id=3] Leader -uve-topic-27-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,596] INFO [Broker id=3] Leader -uve-topic-7-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,598] INFO [Broker id=3] Leader -uve-topic-14-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,602] INFO [Broker id=3] Leader -uve-topic-28-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,605] INFO [Broker id=3] Leader -uve-topic-7-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,608] INFO [Broker id=3] Leader -uve-topic-0-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,613] INFO [Broker id=3] Leader -uve-topic-1-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,616] INFO [Broker id=3] Leader -uve-topic-2-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,619] INFO [Broker id=3] Leader structured_syslog_topic-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,622] INFO [Broker id=3] Leader -uve-topic-4-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,625] INFO [Broker id=3] Leader -uve-topic-13-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,627] INFO [Broker id=3] Leader -uve-topic-7-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,630] INFO [Broker id=3] Leader -uve-topic-11-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,635] INFO [Broker id=3] Leader -uve-topic-24-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,638] INFO [Broker id=3] Leader -uve-topic-29-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,644] INFO [Broker id=3] Leader -uve-topic-11-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,649] INFO [Broker id=3] Leader -uve-topic-4-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,653] INFO [Broker id=3] Leader -uve-topic-6-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,656] INFO [Broker id=3] Leader -uve-topic-1-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,660] INFO [Broker id=3] Leader -uve-topic-18-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,663] INFO [Broker id=3] Leader -uve-topic-2-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,667] INFO [Broker id=3] Leader structured_syslog_topic-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,669] INFO [Broker id=3] Leader -uve-topic-3-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,673] INFO [Broker id=3] Leader -uve-topic-27-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,676] INFO [Broker id=3] Leader -uve-topic-15-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,680] INFO [Broker id=3] Leader -uve-topic-1-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,683] INFO [Broker id=3] Leader structured_syslog_topic-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,687] INFO [Broker id=3] Leader -uve-topic-20-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,691] INFO [Broker id=3] Leader -uve-topic-13-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,696] INFO [Broker id=3] Leader -uve-topic-12-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,699] INFO [Broker id=3] Leader -uve-topic-25-0 starts at leader epoch 4 from offset 968 with high watermark 968 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,704] INFO [Broker id=3] Leader -uve-topic-26-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,706] INFO [Broker id=3] Leader -uve-topic-5-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,710] INFO [Broker id=3] Leader -uve-topic-13-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,714] INFO [Broker id=3] Leader -uve-topic-28-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,719] INFO [Broker id=3] Leader -uve-topic-7-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,722] INFO [Broker id=3] Leader -uve-topic-19-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,725] INFO [Broker id=3] Leader -uve-topic-24-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,729] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-21 starts at leader epoch 4 from offset 1 with high watermark 1 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,733] INFO [Broker id=3] Leader -uve-topic-27-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,736] INFO [Broker id=3] Leader -uve-topic-17-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,739] INFO [Broker id=3] Leader -uve-topic-10-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,742] INFO [Broker id=3] Leader -uve-topic-23-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,748] INFO [Broker id=3] Leader -uve-topic-29-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,750] INFO [Broker id=3] Leader -uve-topic-16-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,755] INFO [Broker id=3] Leader -uve-topic-0-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,762] INFO [Broker id=3] Leader -uve-topic-4-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,767] INFO [Broker id=3] Leader -uve-topic-8-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,772] INFO [Broker id=3] Leader -uve-topic-27-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,777] INFO [Broker id=3] Leader -uve-topic-29-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,783] INFO [Broker id=3] Leader -uve-topic-10-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,787] INFO [Broker id=3] Leader -uve-topic-23-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,790] INFO [Broker id=3] Leader -uve-topic-25-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,793] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,796] INFO [Broker id=3] Leader -uve-topic-18-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,799] INFO [Broker id=3] Leader -uve-topic-9-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,801] INFO [Broker id=3] Leader -uve-topic-0-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,804] INFO [Broker id=3] Leader -uve-topic-1-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,807] INFO [Broker id=3] Leader -uve-topic-2-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,809] INFO [Broker id=3] Leader structured_syslog_topic-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,812] INFO [Broker id=3] Leader -uve-topic-6-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,814] INFO [Broker id=3] Leader -uve-topic-5-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,817] INFO [Broker id=3] Leader -uve-topic-13-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,820] INFO [Broker id=3] Leader -uve-topic-27-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,823] INFO [Broker id=3] Leader -uve-topic-5-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,826] INFO [Broker id=3] Leader -uve-topic-7-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,829] INFO [Broker id=3] Leader -uve-topic-11-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,833] INFO [Broker id=3] Leader -uve-topic-24-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,836] INFO [Broker id=3] Leader -uve-topic-3-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,838] INFO [Broker id=3] Leader structured_syslog_topic-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,840] INFO [Broker id=3] Leader -uve-topic-7-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,843] INFO [Broker id=3] Leader -uve-topic-13-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,846] INFO [Broker id=3] Leader -uve-topic-26-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,848] INFO [Broker id=3] Leader -uve-topic-6-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,852] INFO [Broker id=3] Leader -uve-topic-3-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,855] INFO [Broker id=3] Leader -uve-topic-22-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,858] INFO [Broker id=3] Leader -uve-topic-19-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,861] INFO [Broker id=3] Leader -uve-topic-14-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,864] INFO [Broker id=3] Leader -uve-topic-28-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,868] INFO [Broker id=3] Leader -uve-topic-17-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,871] INFO [Broker id=3] Leader -uve-topic-26-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,874] INFO [Broker id=3] Leader -uve-topic-4-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,879] INFO [Broker id=3] Leader -uve-topic-15-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,882] INFO [Broker id=3] Leader -uve-topic-28-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,884] INFO [Broker id=3] Leader -uve-topic-0-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,887] INFO [Broker id=3] Leader -uve-topic-28-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,889] INFO [Broker id=3] Leader -uve-topic-19-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,891] INFO [Broker id=3] Leader -uve-topic-4-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,894] INFO [Broker id=3] Leader -uve-topic-24-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,897] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-15 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,900] INFO [Broker id=3] Leader -uve-topic-6-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,904] INFO [Broker id=3] Leader -uve-topic-26-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,908] INFO [Broker id=3] Leader -uve-topic-27-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,911] INFO [Broker id=3] Leader -uve-topic-18-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,913] INFO [Broker id=3] Leader -uve-topic-23-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,916] INFO [Broker id=3] Leader -uve-topic-10-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,919] INFO [Broker id=3] Leader -uve-topic-20-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,924] INFO [Broker id=3] Leader -uve-topic-21-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,928] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 3 from offset 3 with high watermark 3 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,931] INFO [Broker id=3] Leader -uve-topic-16-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,933] INFO [Broker id=3] Leader -uve-topic-29-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,936] INFO [Broker id=3] Leader -uve-topic-4-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,939] INFO [Broker id=3] Leader -uve-topic-27-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,942] INFO [Broker id=3] Leader -uve-topic-14-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,944] INFO [Broker id=3] Leader -uve-topic-29-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,947] INFO [Broker id=3] Leader -uve-topic-2-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,949] INFO [Broker id=3] Leader -uve-topic-1-0 starts at leader epoch 4 from offset 490 with high watermark 490 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,952] INFO [Broker id=3] Leader -uve-topic-3-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,955] INFO [Broker id=3] Leader -uve-topic-26-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,958] INFO [Broker id=3] Leader -uve-topic-5-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,961] INFO [Broker id=3] Leader -uve-topic-17-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,964] INFO [Broker id=3] Leader -uve-topic-1-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,967] INFO [Broker id=3] Leader structured_syslog_topic-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,969] INFO [Broker id=3] Leader -uve-topic-26-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,972] INFO [Broker id=3] Leader -uve-topic-13-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,976] INFO [Broker id=3] Leader -uve-topic-5-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,978] INFO [Broker id=3] Leader -uve-topic-28-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,981] INFO [Broker id=3] Leader -uve-topic-5-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,984] INFO [Broker id=3] Leader -uve-topic-4-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,986] INFO [Broker id=3] Leader -uve-topic-24-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:50,989] INFO [Broker id=3] Leader -uve-topic-11-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,992] INFO [Broker id=3] Leader structured_syslog_topic-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,995] INFO [Broker id=3] Leader -uve-topic-7-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:50,997] INFO [Broker id=3] Leader -uve-topic-18-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,002] INFO [Broker id=3] Leader -uve-topic-3-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,006] INFO [Broker id=3] Leader -uve-topic-19-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,010] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-12 starts at leader epoch 4 from offset 1 with high watermark 1 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,013] INFO [Broker id=3] Leader -uve-topic-4-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,018] INFO [Broker id=3] Leader -uve-topic-0-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,021] INFO [Broker id=3] Leader -uve-topic-29-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,191] INFO [Broker id=3] Leader -uve-topic-2-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,381] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-3 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,399] INFO [Broker id=3] Leader -uve-topic-17-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,404] INFO [Broker id=3] Leader -uve-topic-26-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,408] INFO [Broker id=3] Leader -uve-topic-15-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,410] INFO [Broker id=3] Leader -uve-topic-21-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,413] INFO [Broker id=3] Leader -uve-topic-27-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,415] INFO [Broker id=3] Leader -uve-topic-19-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,418] INFO [Broker id=3] Leader -uve-topic-10-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,420] INFO [Broker id=3] Leader -uve-topic-24-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,423] INFO [Broker id=3] Leader -uve-topic-23-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,426] INFO [Broker id=3] Leader -uve-topic-25-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,428] INFO [Broker id=3] Leader -uve-topic-26-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,431] INFO [Broker id=3] Leader -uve-topic-13-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,434] INFO [Broker id=3] Leader -uve-topic-14-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,437] INFO [Broker id=3] Leader -uve-topic-6-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,439] INFO [Broker id=3] Leader -uve-topic-22-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,442] INFO [Broker id=3] Leader -uve-topic-23-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,444] INFO [Broker id=3] Leader -uve-topic-18-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,448] INFO [Broker id=3] Leader -uve-topic-5-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,450] INFO [Broker id=3] Leader -uve-topic-12-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,453] INFO [Broker id=3] Leader -uve-topic-17-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,455] INFO [Broker id=3] Leader -uve-topic-20-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,457] INFO [Broker id=3] Leader -uve-topic-21-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,460] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 3 from offset 5 with high watermark 5 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,462] INFO [Broker id=3] Leader -uve-topic-17-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,465] INFO [Broker id=3] Leader -uve-topic-16-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,468] INFO [Broker id=3] Leader -uve-topic-29-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,470] INFO [Broker id=3] Leader -uve-topic-27-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,472] INFO [Broker id=3] Leader -uve-topic-14-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,475] INFO [Broker id=3] Leader -uve-topic-29-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,477] INFO [Broker id=3] Leader -uve-topic-28-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,480] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-0 starts at leader epoch 4 from offset 6 with high watermark 6 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,483] INFO [Broker id=3] Leader -uve-topic-12-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,485] INFO [Broker id=3] Leader -uve-topic-24-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,489] INFO [Broker id=3] Leader -uve-topic-26-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,492] INFO [Broker id=3] Leader -uve-topic-5-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,495] INFO [Broker id=3] Leader -uve-topic-6-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,497] INFO [Broker id=3] Leader -uve-topic-1-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,501] INFO [Broker id=3] Leader -uve-topic-15-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,503] INFO [Broker id=3] Leader -uve-topic-28-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,506] INFO [Broker id=3] Leader -uve-topic-0-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,508] INFO [Broker id=3] Leader -uve-topic-4-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,511] INFO [Broker id=3] Leader -uve-topic-19-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,514] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,516] INFO [Broker id=3] Leader -uve-topic-6-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,519] INFO [Broker id=3] Leader -uve-topic-10-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,521] INFO [Broker id=3] Leader -uve-topic-27-0 starts at leader epoch 4 from offset 1299 with high watermark 1299 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,524] INFO [Broker id=3] Leader -uve-topic-2-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,526] INFO [Broker id=3] Leader -uve-topic-18-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,529] INFO [Broker id=3] Leader -uve-topic-10-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,532] INFO [Broker id=3] Leader -uve-topic-23-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,534] INFO [Broker id=3] Leader -uve-topic-12-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,537] INFO [Broker id=3] Leader -uve-topic-0-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,539] INFO [Broker id=3] Leader -uve-topic-2-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,542] INFO [Broker id=3] Leader -uve-topic-25-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,545] INFO [Broker id=3] Leader -uve-topic-0-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,548] INFO [Broker id=3] Leader -uve-topic-6-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,551] INFO [Broker id=3] Leader -uve-topic-21-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,554] INFO [Broker id=3] Leader -uve-topic-12-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,556] INFO [Broker id=3] Leader -uve-topic-19-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,559] INFO [Broker id=3] Leader -uve-topic-24-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,561] INFO [Broker id=3] Leader -uve-topic-11-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,564] INFO [Broker id=3] Leader -uve-topic-24-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,566] INFO [Broker id=3] Leader -uve-topic-14-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,569] INFO [Broker id=3] Leader -uve-topic-18-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,572] INFO [Broker id=3] Leader -uve-topic-19-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,574] INFO [Broker id=3] Leader -uve-topic-22-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,577] INFO [Broker id=3] Leader -uve-topic-23-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,581] INFO [Broker id=3] Leader -uve-topic-18-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,584] INFO [Broker id=3] Leader -uve-topic-12-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,587] INFO [Broker id=3] Leader -uve-topic-8-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,591] INFO [Broker id=3] Leader -uve-topic-17-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,593] INFO [Broker id=3] Leader -uve-topic-15-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,597] INFO [Broker id=3] Leader -uve-topic-7-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,600] INFO [Broker id=3] Leader -uve-topic-10-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,602] INFO [Broker id=3] Leader -uve-topic-23-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,605] INFO [Broker id=3] Leader -uve-topic-3-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,607] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-6 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,610] INFO [Broker id=3] Leader -uve-topic-4-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,612] INFO [Broker id=3] Leader -uve-topic-9-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,614] INFO [Broker id=3] Leader -uve-topic-19-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,617] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 3 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,619] INFO [Broker id=3] Leader -uve-topic-17-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,621] INFO [Broker id=3] Leader -uve-topic-0-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,624] INFO [Broker id=3] Leader -uve-topic-6-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,627] INFO [Broker id=3] Leader -uve-topic-10-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,630] INFO [Broker id=3] Leader -uve-topic-2-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,632] INFO [Broker id=3] Leader -uve-topic-18-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,635] INFO [Broker id=3] Leader -uve-topic-5-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,638] INFO [Broker id=3] Leader -uve-topic-6-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,640] INFO [Broker id=3] Leader -uve-topic-12-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,643] INFO [Broker id=3] Leader -uve-topic-2-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,646] INFO [Broker id=3] Leader -uve-topic-1-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,648] INFO [Broker id=3] Leader -uve-topic-9-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,651] INFO [Broker id=3] Leader -uve-topic-21-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,653] INFO [Broker id=3] Leader -uve-topic-24-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,656] INFO [Broker id=3] Leader -uve-topic-15-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,658] INFO [Broker id=3] Leader -uve-topic-3-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,662] INFO [Broker id=3] Leader -uve-topic-28-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,667] INFO [Broker id=3] Leader -uve-topic-8-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,670] INFO [Broker id=3] Leader -uve-topic-27-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,673] INFO [Broker id=3] Leader -uve-topic-14-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,676] INFO [Broker id=3] Leader -uve-topic-29-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,686] INFO [Broker id=3] Leader -uve-topic-19-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,689] INFO [Broker id=3] Leader -uve-topic-24-0 starts at leader epoch 4 from offset 378 with high watermark 378 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,693] INFO [Broker id=3] Leader -uve-topic-26-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,696] INFO [Broker id=3] Leader -uve-topic-10-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,699] INFO [Broker id=3] Leader -uve-topic-25-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,704] INFO [Broker id=3] Leader -uve-topic-11-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,706] INFO [Broker id=3] Leader -uve-topic-10-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,708] INFO [Broker id=3] Leader -uve-topic-15-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,711] INFO [Broker id=3] Leader -uve-topic-21-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,714] INFO [Broker id=3] Leader -uve-topic-6-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,718] INFO [Broker id=3] Leader -uve-topic-19-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,720] INFO [Broker id=3] Leader -uve-topic-9-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,723] INFO [Broker id=3] Leader -uve-topic-0-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,725] INFO [Broker id=3] Leader -uve-topic-2-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,743] INFO [Broker id=3] Leader -uve-topic-12-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,745] INFO [Broker id=3] Leader -uve-topic-8-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,747] INFO [Broker id=3] Leader -uve-topic-0-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,750] INFO [Broker id=3] Leader -uve-topic-2-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,752] INFO [Broker id=3] Leader -uve-topic-7-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,754] INFO [Broker id=3] Leader -uve-topic-14-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,756] INFO [Broker id=3] Leader -uve-topic-24-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,758] INFO [Broker id=3] Leader -uve-topic-18-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,761] INFO [Broker id=3] Leader -uve-topic-3-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,763] INFO [Broker id=3] Leader -uve-topic-23-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,765] INFO [Broker id=3] Leader -uve-topic-6-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,769] INFO [Broker id=3] Leader -uve-topic-29-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,771] INFO [Broker id=3] Leader -uve-topic-2-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,773] INFO [Broker id=3] Leader -uve-topic-1-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,775] INFO [Broker id=3] Leader -uve-topic-19-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,778] INFO [Broker id=3] Leader -uve-topic-25-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,780] INFO [Broker id=3] Leader -uve-topic-12-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,782] INFO [Broker id=3] Leader -uve-topic-24-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,784] INFO [Broker id=3] Leader -uve-topic-15-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,787] INFO [Broker id=3] Leader -uve-topic-28-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,789] INFO [Broker id=3] Leader -uve-topic-8-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,792] INFO [Broker id=3] Leader -uve-topic-14-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,794] INFO [Broker id=3] Leader -uve-topic-27-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,797] INFO [Broker id=3] Leader -uve-topic-20-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,800] INFO [Broker id=3] Leader -uve-topic-26-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,802] INFO [Broker id=3] Leader -uve-topic-10-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,805] INFO [Broker id=3] Leader structured_syslog_topic-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,809] INFO [Broker id=3] Leader -uve-topic-11-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,812] INFO [Broker id=3] Leader -uve-topic-13-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,814] INFO [Broker id=3] Leader -uve-topic-12-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,816] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 3 from offset 5 with high watermark 5 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,819] INFO [Broker id=3] Leader -uve-topic-21-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,821] INFO [Broker id=3] Leader -uve-topic-17-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,824] INFO [Broker id=3] Leader -uve-topic-9-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,826] INFO [Broker id=3] Leader -uve-topic-0-0 starts at leader epoch 4 from offset 3159 with high watermark 3159 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,829] INFO [Broker id=3] Leader -uve-topic-18-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,831] INFO [Broker id=3] Leader -uve-topic-23-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,834] INFO [Broker id=3] Leader -uve-topic-15-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,836] INFO [Broker id=3] Leader -uve-topic-2-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,838] INFO [Broker id=3] Leader -uve-topic-13-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,841] INFO [Broker id=3] Leader -uve-topic-12-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,843] INFO [Broker id=3] Leader -uve-topic-14-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,846] INFO [Broker id=3] Leader -uve-topic-23-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,849] INFO [Broker id=3] Leader -uve-topic-25-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,851] INFO [Broker id=3] Leader -uve-topic-8-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,854] INFO [Broker id=3] Leader -uve-topic-0-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,856] INFO [Broker id=3] Leader -uve-topic-14-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,859] INFO [Broker id=3] Leader -uve-topic-18-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,863] INFO [Broker id=3] Leader -uve-topic-9-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,865] INFO [Broker id=3] Leader -uve-topic-22-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,868] INFO [Broker id=3] Leader -uve-topic-21-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,870] INFO [Broker id=3] Leader -uve-topic-3-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,872] INFO [Broker id=3] Leader -uve-topic-10-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,875] INFO [Broker id=3] Leader -uve-topic-11-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,877] INFO [Broker id=3] Leader -uve-topic-20-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,879] INFO [Broker id=3] Leader -uve-topic-21-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,882] INFO [Broker id=3] Leader -uve-topic-15-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,884] INFO [Broker id=3] Leader -uve-topic-16-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,886] INFO [Broker id=3] Leader -uve-topic-9-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,889] INFO [Broker id=3] Leader -uve-topic-1-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,892] INFO [Broker id=3] Leader -uve-topic-22-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,895] INFO [Broker id=3] Leader structured_syslog_topic-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,897] INFO [Broker id=3] Leader -uve-topic-2-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,900] INFO [Broker id=3] Leader -uve-topic-14-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,902] INFO [Broker id=3] Leader -uve-topic-27-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,904] INFO [Broker id=3] Leader -uve-topic-20-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,906] INFO [Broker id=3] Leader -uve-topic-1-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,909] INFO [Broker id=3] Leader structured_syslog_topic-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,911] INFO [Broker id=3] Leader -uve-topic-5-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,913] INFO [Broker id=3] Leader -uve-topic-11-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,916] INFO [Broker id=3] Leader -uve-topic-13-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,918] INFO [Broker id=3] Leader -uve-topic-12-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,921] INFO [Broker id=3] Leader -uve-topic-29-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,927] INFO [Broker id=3] Leader -uve-topic-21-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,929] INFO [Broker id=3] Leader -uve-topic-22-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,931] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 3 from offset 4 with high watermark 4 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,934] INFO [Broker id=3] Leader -uve-topic-17-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,936] INFO [Broker id=3] Leader -uve-topic-12-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,939] INFO [Broker id=3] Leader -uve-topic-25-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,941] INFO [Broker id=3] Leader -uve-topic-15-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,943] INFO [Broker id=3] Leader -uve-topic-22-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,946] INFO [Broker id=3] Leader -uve-topic-26-0 starts at leader epoch 3 from offset 1236 with high watermark 1236 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,948] INFO [Broker id=3] Leader -uve-topic-6-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,951] INFO [Broker id=3] Leader -uve-topic-4-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,953] INFO [Broker id=3] Leader -uve-topic-9-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,956] INFO [Broker id=3] Leader -uve-topic-28-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,958] INFO [Broker id=3] Leader -uve-topic-15-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,961] INFO [Broker id=3] Leader -uve-topic-16-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,963] INFO [Broker id=3] Leader -uve-topic-8-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,966] INFO [Broker id=3] Leader -uve-topic-9-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,968] INFO [Broker id=3] Leader -uve-topic-3-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,971] INFO [Broker id=3] Leader -uve-topic-22-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,973] INFO [Broker id=3] Leader -uve-topic-1-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,975] INFO [Broker id=3] Leader -uve-topic-9-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,978] INFO [Broker id=3] Leader -uve-topic-4-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,982] INFO [Broker id=3] Leader -uve-topic-9-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,985] INFO [Broker id=3] Leader -uve-topic-22-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,987] INFO [Broker id=3] Leader -uve-topic-3-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,990] INFO [Broker id=3] Leader -uve-topic-5-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,992] INFO [Broker id=3] Leader -uve-topic-20-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:51,994] INFO [Broker id=3] Leader -uve-topic-8-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,997] INFO [Broker id=3] Leader -uve-topic-0-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:51,999] INFO [Broker id=3] Leader -uve-topic-21-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,001] INFO [Broker id=3] Leader -uve-topic-9-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,003] INFO [Broker id=3] Leader -uve-topic-2-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,005] INFO [Broker id=3] Leader structured_syslog_topic-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,008] INFO [Broker id=3] Leader -uve-topic-14-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,010] INFO [Broker id=3] Leader -uve-topic-7-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,013] INFO [Broker id=3] Leader -uve-topic-13-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,016] INFO [Broker id=3] Leader -uve-topic-14-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,018] INFO [Broker id=3] Leader -uve-topic-25-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,020] INFO [Broker id=3] Leader -uve-topic-21-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,023] INFO [Broker id=3] Leader -uve-topic-8-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,025] INFO [Broker id=3] Leader -uve-topic-29-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,027] INFO [Broker id=3] Leader -uve-topic-11-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,030] INFO [Broker id=3] Leader -uve-topic-15-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,033] INFO [Broker id=3] Leader -uve-topic-16-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,035] INFO [Broker id=3] Follower -uve-topic-29-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,035] INFO [Broker id=3] Follower -uve-topic-18-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-2-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-14-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-27-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-5-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-17-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-21-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-24-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-26-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-8-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-0-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-0-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-2-0 starts at leader epoch 3 from offset 488 with high watermark 488. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-28-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-6-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-7-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-22-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-0-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-9-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-4-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-17-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-3-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-10-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-23-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-19-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-29-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-14 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-21-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-18-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-2-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-10-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-23-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-27-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-6-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-8-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-21-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-0-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-29-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-26-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-12-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-6-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-5-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-16-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-19-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-24-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-28-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-15-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-29-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-7-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-17-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-15-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-20-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-21-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-11 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-23-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,036] INFO [Broker id=3] Follower -uve-topic-11-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-10-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-19-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-20-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-8 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-29-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-0-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-9-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-6-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-7-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-29-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-2-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-18-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-14-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-28-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-27-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-14-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-8-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-22-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-15-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-28-0 starts at leader epoch 4 from offset 716 with high watermark 716. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-17-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-21-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-25-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-12-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-24-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-26-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-15-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-19-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-12-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-24-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-15-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-28-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-5 starts at leader epoch 4 from offset 6 with high watermark 6. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-18-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-23-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-10-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-17-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-14-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-21-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-15-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-13-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-12-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-14-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-2-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-27-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-15-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-9-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-8-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-1-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,037] INFO [Broker id=3] Follower -uve-topic-0-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower structured_syslog_topic-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-26-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-6-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-20-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-8-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-16-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-3-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-5-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-14-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-2-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-28-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-8-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-0-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-9-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-22-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-12-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-25-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-26-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-7-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-6-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-15-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-10-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-11-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-19-0 starts at leader epoch 4 from offset 148 with high watermark 148. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower structured_syslog_topic-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-14-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-9-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-6-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-14-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-27-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-21-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-28-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-14-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-16-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-12-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-27-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-13-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-26-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-14-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-6-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-8-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-20-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-4-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-5-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-2-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower structured_syslog_topic-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-21-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-15-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-9-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-8-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-1-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-0-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower structured_syslog_topic-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower -uve-topic-13-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,038] INFO [Broker id=3] Follower structured_syslog_topic-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-7-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-20-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-15-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-12-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-25-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-3-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-11-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower structured_syslog_topic-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-13-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-14-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-22-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-6-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-21-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-16-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-2-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-13-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-9-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-8-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-5-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-22-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-29-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-16-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-15-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-8-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-4-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-5-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-1-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower structured_syslog_topic-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-26-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-25-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-12-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-13-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-4-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-17-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-16-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-22-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-9-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-21-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-13-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-28-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-20-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-14-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-25-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-20-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-12-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-27-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-10-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-25-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-18-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-22-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-21-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower structured_syslog_topic-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-20-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-16-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-15-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-25-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-11-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-13-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-12-0 starts at leader epoch 4 from offset 145 with high watermark 145. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-13-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-9-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-8-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-7-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-3-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-25-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-12-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower structured_syslog_topic-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-7-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-23-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-14-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-19-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-22-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-24-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-11-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-28 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-4-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-25-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-5-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-4-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-17-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-1-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-16-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,039] INFO [Broker id=3] Follower -uve-topic-9-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-12-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-4-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-3-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-3-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-15-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-7-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-8-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-25-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-4-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-11-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-5-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-6-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-27-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-10-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-24-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-11-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-26-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-13-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-25-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-20-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-22-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-16-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-29-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-21-0 starts at leader epoch 4 from offset 1663 with high watermark 1663. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-28-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-1-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower structured_syslog_topic-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-5-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-9-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-8-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-1-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-24-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-5-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-7-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-23-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-3-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-19-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-4-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-25-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-0-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-4-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-18-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-3-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-23-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-11-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-20-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-7-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-16-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-24-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-11-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-11-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-3-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower structured_syslog_topic-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-13-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-22-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower structured_syslog_topic-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-5-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-12-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-24-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-11-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-26-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-13-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-17-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-20-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-29 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-22-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-9-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-19-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-18-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-24-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-23-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-3-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-19-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-23-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-10-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-28-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 3 from offset 5 with high watermark 5. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-3-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-26-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-1-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-1-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-25-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-4-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-16-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-29-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-7-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-8-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,040] INFO [Broker id=3] Follower -uve-topic-27-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-6-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-27-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-2-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-11-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-10-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-4-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-1-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-0-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-9-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-16-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-18-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-3-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-11-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-29-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-20-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-21-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-18-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower structured_syslog_topic-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-5-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-7-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-27-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-13-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-14-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-23-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-19-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-22-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-24-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-26-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-25-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-23-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-10-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-19-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-10-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-2-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-28-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-26 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-26-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-25-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-27-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-10-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-12-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-24-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-11-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-4-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-18-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-2-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-1-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower structured_syslog_topic-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-7-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-27-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-6-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-2-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-5-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-13-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-26-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-1-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-17-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-18-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-20-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-22-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-19-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-23-0 starts at leader epoch 3 from offset 584 with high watermark 584. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-24-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-23 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-19-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-28-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-3-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-15-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-17-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-29-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-16-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-28-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-29-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-23-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-10-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-18-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-6-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-5-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-7-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-0-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-9-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-17-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-4-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-24-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-26-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-16-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,041] INFO [Broker id=3] Follower -uve-topic-17-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-18-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-23-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-10-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-11-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-19-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-21-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-20-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-28-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-20 starts at leader epoch 4 from offset 6 with high watermark 6. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-18-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-14-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-13-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-27-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-1-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-0-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-22-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-3-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-29-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-2-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-1-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-2-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower structured_syslog_topic-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-0-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-6-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-5-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-1-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-17-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-19-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-4-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-20-0 starts at leader epoch 4 from offset 1774 with high watermark 1774. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-28-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-3-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-15-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-17 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-29-0 starts at leader epoch 3 from offset 850 with high watermark 850. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-16-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-17-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-2-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-1-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-17-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-23-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,042] INFO [Broker id=3] Follower -uve-topic-10-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-27-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-6-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-26-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-8-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-0-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-21-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-12-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-0-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-22-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-9-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-24-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-18-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-7-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,043] INFO [Broker id=3] Follower -uve-topic-29-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,058] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 1 epoch 2 with correlation id 5 for 480 partitions (state.change.logger)
[2025-02-10 01:58:52,088] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 2 for 960 partitions (state.change.logger)
[2025-02-10 01:58:52,091] INFO [Broker id=3] Stopped fetchers as part of LeaderAndIsr request correlationId 1 from controller 2 epoch 3 as part of the become-leader transition for 960 partitions (state.change.logger)
[2025-02-10 01:58:52,091] INFO [Broker id=3] Leader -uve-topic-22-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,095] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,095] INFO [Broker id=3] Leader -uve-topic-23-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,098] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,099] INFO [Broker id=3] Leader -uve-topic-17-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,101] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,101] INFO [Broker id=3] Leader -uve-topic-16-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,107] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,107] INFO [Broker id=3] Leader -uve-topic-29-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,110] INFO [Broker id=3] Leader -uve-topic-2-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,112] INFO [Broker id=3] Leader -uve-topic-18-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,115] INFO [Broker id=3] Leader -uve-topic-27-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,117] INFO [Broker id=3] Leader -uve-topic-14-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,119] INFO [Broker id=3] Leader -uve-topic-5-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,122] INFO [Broker id=3] Leader -uve-topic-16-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,125] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,125] INFO [Broker id=3] Leader -uve-topic-29-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,127] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,127] INFO [Broker id=3] Leader -uve-topic-17-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,130] INFO [Broker id=3] Leader -uve-topic-21-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,132] INFO [Broker id=3] Leader -uve-topic-11-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,135] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,135] INFO [Broker id=3] Leader -uve-topic-24-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,137] INFO [Broker id=3] Leader -uve-topic-13-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,141] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,141] INFO [Broker id=3] Leader -uve-topic-26-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,143] INFO [Broker id=3] Leader -uve-topic-8-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,146] INFO [Broker id=3] Leader -uve-topic-0-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,148] INFO [Broker id=3] Leader -uve-topic-17-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,151] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,151] INFO [Broker id=3] Leader -uve-topic-9-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,153] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,153] INFO [Broker id=3] Leader -uve-topic-0-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,156] INFO [Broker id=3] Leader -uve-topic-20-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,158] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,158] INFO [Broker id=3] Leader -uve-topic-1-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,160] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,160] INFO [Broker id=3] Leader -uve-topic-3-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,163] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,163] INFO [Broker id=3] Leader -uve-topic-2-0 starts at leader epoch 4 from offset 488 with high watermark 488 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,166] INFO [Broker id=3] Leader -uve-topic-7-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,168] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,168] INFO [Broker id=3] Leader -uve-topic-6-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,170] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,170] INFO [Broker id=3] Leader -uve-topic-15-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,172] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,172] INFO [Broker id=3] Leader -uve-topic-28-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,176] INFO [Broker id=3] Leader -uve-topic-6-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,178] INFO [Broker id=3] Leader -uve-topic-7-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,181] INFO [Broker id=3] Leader -uve-topic-22-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,183] INFO [Broker id=3] Leader -uve-topic-0-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,186] INFO [Broker id=3] Leader -uve-topic-9-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,189] INFO [Broker id=3] Leader -uve-topic-21-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,191] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,191] INFO [Broker id=3] Leader structured_syslog_topic-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,194] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,194] INFO [Broker id=3] Leader -uve-topic-5-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,196] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,196] INFO [Broker id=3] Leader -uve-topic-4-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,198] INFO [Broker id=3] Leader -uve-topic-17-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,201] INFO [Broker id=3] Leader -uve-topic-8-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,203] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,203] INFO [Broker id=3] Leader -uve-topic-3-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,206] INFO [Broker id=3] Leader -uve-topic-4-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,208] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,208] INFO [Broker id=3] Leader -uve-topic-10-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,210] INFO [Broker id=3] Leader -uve-topic-23-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,213] INFO [Broker id=3] Leader -uve-topic-25-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,215] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,215] INFO [Broker id=3] Leader -uve-topic-20-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,217] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,217] INFO [Broker id=3] Leader -uve-topic-12-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,220] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,220] INFO [Broker id=3] Leader -uve-topic-19-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,222] INFO [Broker id=3] Leader -uve-topic-29-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,225] INFO [Broker id=3] Leader -uve-topic-16-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,227] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,227] INFO [Broker id=3] Leader -uve-topic-8-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,229] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,229] INFO [Broker id=3] Leader -uve-topic-21-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,232] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-14 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,234] INFO [Broker id=3] Leader -uve-topic-2-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,237] INFO [Broker id=3] Leader -uve-topic-9-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,239] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,239] INFO [Broker id=3] Leader -uve-topic-18-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,242] INFO [Broker id=3] Leader -uve-topic-10-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,244] INFO [Broker id=3] Leader -uve-topic-23-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,246] INFO [Broker id=3] Leader -uve-topic-14-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,249] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,249] INFO [Broker id=3] Leader -uve-topic-27-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,251] INFO [Broker id=3] Leader -uve-topic-7-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,254] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,254] INFO [Broker id=3] Leader -uve-topic-6-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,256] INFO [Broker id=3] Leader -uve-topic-8-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,259] INFO [Broker id=3] Leader -uve-topic-21-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,262] INFO [Broker id=3] Leader -uve-topic-20-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,265] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,265] INFO [Broker id=3] Leader -uve-topic-0-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,268] INFO [Broker id=3] Leader -uve-topic-17-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,270] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,270] INFO [Broker id=3] Leader -uve-topic-29-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,273] INFO [Broker id=3] Leader -uve-topic-16-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,275] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,275] INFO [Broker id=3] Leader -uve-topic-4-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,277] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,277] INFO [Broker id=3] Leader -uve-topic-13-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,280] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,280] INFO [Broker id=3] Leader -uve-topic-26-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,282] INFO [Broker id=3] Leader -uve-topic-6-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,284] INFO [Broker id=3] Leader -uve-topic-5-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,287] INFO [Broker id=3] Leader -uve-topic-12-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,290] INFO [Broker id=3] Leader -uve-topic-26-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,293] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,293] INFO [Broker id=3] Leader -uve-topic-25-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,296] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,296] INFO [Broker id=3] Leader -uve-topic-29-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,298] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,298] INFO [Broker id=3] Leader -uve-topic-16-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,301] INFO [Broker id=3] Leader -uve-topic-10-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,303] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,303] INFO [Broker id=3] Leader -uve-topic-23-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,306] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,306] INFO [Broker id=3] Leader -uve-topic-19-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,308] INFO [Broker id=3] Leader -uve-topic-25-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,310] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,310] INFO [Broker id=3] Leader -uve-topic-11-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,313] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,313] INFO [Broker id=3] Leader -uve-topic-24-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,315] INFO [Broker id=3] Leader -uve-topic-19-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,318] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,318] INFO [Broker id=3] Leader -uve-topic-28-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,320] INFO [Broker id=3] Leader -uve-topic-15-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,323] INFO [Broker id=3] Leader -uve-topic-20-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,326] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,326] INFO [Broker id=3] Leader -uve-topic-29-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,328] INFO [Broker id=3] Leader -uve-topic-16-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,330] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,330] INFO [Broker id=3] Leader -uve-topic-7-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,333] INFO [Broker id=3] Leader -uve-topic-8-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,335] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,335] INFO [Broker id=3] Leader -uve-topic-22-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,337] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,337] INFO [Broker id=3] Leader -uve-topic-18-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,339] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,339] INFO [Broker id=3] Leader -uve-topic-24-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,341] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,342] INFO [Broker id=3] Leader -uve-topic-11-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,344] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,344] INFO [Broker id=3] Leader -uve-topic-17-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,346] INFO [Broker id=3] Leader -uve-topic-22-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,348] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,348] INFO [Broker id=3] Leader -uve-topic-1-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,351] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,351] INFO [Broker id=3] Leader structured_syslog_topic-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,353] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,353] INFO [Broker id=3] Leader -uve-topic-5-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,356] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,356] INFO [Broker id=3] Leader -uve-topic-15-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,358] INFO [Broker id=3] Leader -uve-topic-28-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,360] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,360] INFO [Broker id=3] Leader -uve-topic-20-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,362] INFO [Broker id=3] Leader -uve-topic-21-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,365] INFO [Broker id=3] Leader -uve-topic-7-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,367] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,367] INFO [Broker id=3] Leader -uve-topic-3-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,369] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,369] INFO [Broker id=3] Leader -uve-topic-8-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,371] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,371] INFO [Broker id=3] Leader -uve-topic-21-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,374] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,374] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-11 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,376] INFO [Broker id=3] Leader -uve-topic-0-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,378] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,378] INFO [Broker id=3] Leader -uve-topic-24-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,380] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,381] INFO [Broker id=3] Leader -uve-topic-23-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,383] INFO [Broker id=3] Leader -uve-topic-11-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,385] INFO [Broker id=3] Leader -uve-topic-10-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,387] INFO [Broker id=3] Leader -uve-topic-19-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,390] INFO [Broker id=3] Leader -uve-topic-20-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,392] INFO [Broker id=3] Leader -uve-topic-3-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,394] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,394] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-8 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,396] INFO [Broker id=3] Leader -uve-topic-7-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,398] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,398] INFO [Broker id=3] Leader -uve-topic-17-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,401] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,401] INFO [Broker id=3] Leader -uve-topic-16-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,403] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,403] INFO [Broker id=3] Leader -uve-topic-29-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,405] INFO [Broker id=3] Leader -uve-topic-0-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,407] INFO [Broker id=3] Leader structured_syslog_topic-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,409] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,409] INFO [Broker id=3] Leader -uve-topic-9-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,412] INFO [Broker id=3] Leader -uve-topic-6-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,414] INFO [Broker id=3] Leader -uve-topic-26-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,416] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,416] INFO [Broker id=3] Leader -uve-topic-13-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,418] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,418] INFO [Broker id=3] Leader -uve-topic-5-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,420] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,420] INFO [Broker id=3] Leader -uve-topic-7-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,423] INFO [Broker id=3] Leader -uve-topic-8-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,425] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,425] INFO [Broker id=3] Leader -uve-topic-19-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,427] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,427] INFO [Broker id=3] Leader -uve-topic-4-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,429] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,429] INFO [Broker id=3] Leader -uve-topic-25-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,431] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,431] INFO [Broker id=3] Leader -uve-topic-20-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,434] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,434] INFO [Broker id=3] Leader -uve-topic-12-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,437] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,437] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-27 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,439] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,439] INFO [Broker id=3] Leader -uve-topic-16-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,441] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,441] INFO [Broker id=3] Leader -uve-topic-29-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,443] INFO [Broker id=3] Leader -uve-topic-8-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,445] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,445] INFO [Broker id=3] Leader -uve-topic-18-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,448] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,448] INFO [Broker id=3] Leader -uve-topic-1-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,452] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,452] INFO [Broker id=3] Leader -uve-topic-22-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,454] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,454] INFO [Broker id=3] Leader -uve-topic-23-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,456] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,456] INFO [Broker id=3] Leader -uve-topic-10-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,459] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,459] INFO [Broker id=3] Leader -uve-topic-2-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,461] INFO [Broker id=3] Leader -uve-topic-18-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,463] INFO [Broker id=3] Leader -uve-topic-27-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,467] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,467] INFO [Broker id=3] Leader -uve-topic-14-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,469] INFO [Broker id=3] Leader -uve-topic-15-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,471] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,471] INFO [Broker id=3] Leader -uve-topic-28-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,473] INFO [Broker id=3] Leader -uve-topic-28-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,475] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,475] INFO [Broker id=3] Leader -uve-topic-27-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,477] INFO [Broker id=3] Leader -uve-topic-14-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,479] INFO [Broker id=3] Leader -uve-topic-8-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,481] INFO [Broker id=3] Leader -uve-topic-22-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,483] INFO [Broker id=3] Leader -uve-topic-16-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,486] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,486] INFO [Broker id=3] Leader -uve-topic-15-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,489] INFO [Broker id=3] Leader -uve-topic-29-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,491] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,491] INFO [Broker id=3] Leader -uve-topic-28-0 starts at leader epoch 5 from offset 716 with high watermark 716 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,493] INFO [Broker id=3] Leader -uve-topic-21-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,495] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,495] INFO [Broker id=3] Leader -uve-topic-17-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,497] INFO [Broker id=3] Leader -uve-topic-20-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,499] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,499] INFO [Broker id=3] Leader -uve-topic-21-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,502] INFO [Broker id=3] Leader structured_syslog_topic-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,504] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,504] INFO [Broker id=3] Leader -uve-topic-25-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,506] INFO [Broker id=3] Leader -uve-topic-12-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,508] INFO [Broker id=3] Leader -uve-topic-24-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,510] INFO [Broker id=3] Leader -uve-topic-11-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,512] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,512] INFO [Broker id=3] Leader -uve-topic-26-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,514] INFO [Broker id=3] Leader -uve-topic-13-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,517] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,517] INFO [Broker id=3] Leader -uve-topic-15-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,519] INFO [Broker id=3] Leader -uve-topic-28-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,521] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,521] INFO [Broker id=3] Leader -uve-topic-20-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,523] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,523] INFO [Broker id=3] Leader -uve-topic-7-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,525] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,525] INFO [Broker id=3] Leader -uve-topic-3-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,527] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,528] INFO [Broker id=3] Leader -uve-topic-19-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,530] INFO [Broker id=3] Leader -uve-topic-23-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,533] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,533] INFO [Broker id=3] Leader -uve-topic-10-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,535] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,535] INFO [Broker id=3] Leader -uve-topic-25-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,538] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,538] INFO [Broker id=3] Leader -uve-topic-12-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,540] INFO [Broker id=3] Leader -uve-topic-24-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,542] INFO [Broker id=3] Leader -uve-topic-11-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,544] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,545] INFO [Broker id=3] Leader -uve-topic-15-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,547] INFO [Broker id=3] Leader -uve-topic-28-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,549] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-5 starts at leader epoch 5 from offset 6 with high watermark 6 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,552] INFO [Broker id=3] Leader -uve-topic-20-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,554] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,554] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-24 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,557] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,557] INFO [Broker id=3] Leader -uve-topic-6-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,559] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,559] INFO [Broker id=3] Leader -uve-topic-9-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,562] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,562] INFO [Broker id=3] Leader -uve-topic-19-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,564] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,564] INFO [Broker id=3] Leader -uve-topic-18-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,566] INFO [Broker id=3] Leader -uve-topic-22-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,569] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,569] INFO [Broker id=3] Leader -uve-topic-10-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,571] INFO [Broker id=3] Leader -uve-topic-23-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,574] INFO [Broker id=3] Leader -uve-topic-18-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,576] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,576] INFO [Broker id=3] Leader -uve-topic-17-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,578] INFO [Broker id=3] Leader -uve-topic-22-0 starts at leader epoch 5 from offset 2073 with high watermark 2073 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,580] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,580] INFO [Broker id=3] Leader -uve-topic-14-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,583] INFO [Broker id=3] Leader -uve-topic-27-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,585] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,585] INFO [Broker id=3] Leader -uve-topic-5-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,587] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,587] INFO [Broker id=3] Leader -uve-topic-21-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,590] INFO [Broker id=3] Leader -uve-topic-28-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,592] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,592] INFO [Broker id=3] Leader -uve-topic-15-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,595] INFO [Broker id=3] Leader -uve-topic-16-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,597] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,597] INFO [Broker id=3] Leader -uve-topic-17-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,599] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,600] INFO [Broker id=3] Leader -uve-topic-13-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,602] INFO [Broker id=3] Leader -uve-topic-12-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,604] INFO [Broker id=3] Leader -uve-topic-25-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,606] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,606] INFO [Broker id=3] Leader -uve-topic-26-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,609] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,609] INFO [Broker id=3] Leader -uve-topic-14-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,611] INFO [Broker id=3] Leader -uve-topic-27-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,613] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,613] INFO [Broker id=3] Leader -uve-topic-7-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,616] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,616] INFO [Broker id=3] Leader -uve-topic-2-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,618] INFO [Broker id=3] Leader -uve-topic-14-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,620] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,621] INFO [Broker id=3] Leader -uve-topic-27-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,623] INFO [Broker id=3] Leader -uve-topic-28-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,626] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,626] INFO [Broker id=3] Leader -uve-topic-15-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,629] INFO [Broker id=3] Leader -uve-topic-7-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,631] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,631] INFO [Broker id=3] Leader -uve-topic-0-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,634] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,634] INFO [Broker id=3] Leader -uve-topic-1-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,636] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,636] INFO [Broker id=3] Leader -uve-topic-2-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,638] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,638] INFO [Broker id=3] Leader -uve-topic-9-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,641] INFO [Broker id=3] Leader -uve-topic-8-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,643] INFO [Broker id=3] Leader structured_syslog_topic-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,645] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,645] INFO [Broker id=3] Leader -uve-topic-1-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,648] INFO [Broker id=3] Leader -uve-topic-0-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,650] INFO [Broker id=3] Leader structured_syslog_topic-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,652] INFO [Broker id=3] Leader -uve-topic-4-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,654] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,654] INFO [Broker id=3] Leader -uve-topic-13-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,657] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,657] INFO [Broker id=3] Leader -uve-topic-26-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,659] INFO [Broker id=3] Leader -uve-topic-6-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,661] INFO [Broker id=3] Leader -uve-topic-8-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,663] INFO [Broker id=3] Leader -uve-topic-7-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,667] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,667] INFO [Broker id=3] Leader -uve-topic-20-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,669] INFO [Broker id=3] Leader -uve-topic-11-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,672] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,672] INFO [Broker id=3] Leader -uve-topic-24-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,674] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,674] INFO [Broker id=3] Leader -uve-topic-29-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,676] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,676] INFO [Broker id=3] Leader -uve-topic-16-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,679] INFO [Broker id=3] Leader -uve-topic-3-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,681] INFO [Broker id=3] Leader -uve-topic-11-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,683] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,683] INFO [Broker id=3] Leader -uve-topic-4-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,685] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,685] INFO [Broker id=3] Leader -uve-topic-5-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,688] INFO [Broker id=3] Leader -uve-topic-6-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,690] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,690] INFO [Broker id=3] Leader -uve-topic-2-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,692] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,692] INFO [Broker id=3] Leader -uve-topic-1-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,694] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,694] INFO [Broker id=3] Leader -uve-topic-18-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,696] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,696] INFO [Broker id=3] Leader structured_syslog_topic-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,699] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,699] INFO [Broker id=3] Leader -uve-topic-3-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,701] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,701] INFO [Broker id=3] Leader -uve-topic-2-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,703] INFO [Broker id=3] Leader -uve-topic-14-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,705] INFO [Broker id=3] Leader -uve-topic-27-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,707] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,707] INFO [Broker id=3] Leader -uve-topic-28-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,710] INFO [Broker id=3] Leader -uve-topic-15-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,712] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,712] INFO [Broker id=3] Leader -uve-topic-8-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,714] INFO [Broker id=3] Leader -uve-topic-1-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,717] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,717] INFO [Broker id=3] Leader -uve-topic-0-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,720] INFO [Broker id=3] Leader -uve-topic-20-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,722] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,722] INFO [Broker id=3] Leader structured_syslog_topic-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,724] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,724] INFO [Broker id=3] Leader -uve-topic-9-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,726] INFO [Broker id=3] Leader -uve-topic-22-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,729] INFO [Broker id=3] Leader -uve-topic-13-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,731] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,731] INFO [Broker id=3] Leader -uve-topic-12-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,734] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,734] INFO [Broker id=3] Leader -uve-topic-25-0 starts at leader epoch 5 from offset 968 with high watermark 968 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,736] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,736] INFO [Broker id=3] Leader -uve-topic-26-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,739] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,739] INFO [Broker id=3] Leader -uve-topic-5-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,742] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,742] INFO [Broker id=3] Leader -uve-topic-12-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,744] INFO [Broker id=3] Leader -uve-topic-25-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,746] INFO [Broker id=3] Leader -uve-topic-13-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,749] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,749] INFO [Broker id=3] Leader -uve-topic-26-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,751] INFO [Broker id=3] Leader -uve-topic-7-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,754] INFO [Broker id=3] Leader -uve-topic-6-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,756] INFO [Broker id=3] Leader -uve-topic-28-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,758] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,758] INFO [Broker id=3] Leader -uve-topic-15-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,760] INFO [Broker id=3] Leader -uve-topic-7-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,762] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,762] INFO [Broker id=3] Leader -uve-topic-19-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,764] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,764] INFO [Broker id=3] Leader -uve-topic-10-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,767] INFO [Broker id=3] Leader -uve-topic-11-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,769] INFO [Broker id=3] Leader -uve-topic-24-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,771] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,771] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-21 starts at leader epoch 5 from offset 1 with high watermark 1 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,773] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,773] INFO [Broker id=3] Leader -uve-topic-19-0 starts at leader epoch 5 from offset 148 with high watermark 148 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,776] INFO [Broker id=3] Leader structured_syslog_topic-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,778] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,781] INFO [Broker id=3] Leader -uve-topic-14-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,784] INFO [Broker id=3] Leader -uve-topic-27-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,786] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,786] INFO [Broker id=3] Leader -uve-topic-10-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,788] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,788] INFO [Broker id=3] Leader -uve-topic-23-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,791] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,791] INFO [Broker id=3] Leader -uve-topic-17-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,793] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,793] INFO [Broker id=3] Leader -uve-topic-9-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,795] INFO [Broker id=3] Leader -uve-topic-14-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,798] INFO [Broker id=3] Leader -uve-topic-27-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,800] INFO [Broker id=3] Leader -uve-topic-6-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,802] INFO [Broker id=3] Leader -uve-topic-29-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,804] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,804] INFO [Broker id=3] Leader -uve-topic-16-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,807] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,807] INFO [Broker id=3] Leader -uve-topic-21-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,809] INFO [Broker id=3] Leader -uve-topic-0-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,811] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,811] INFO [Broker id=3] Leader -uve-topic-4-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,813] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,814] INFO [Broker id=3] Leader -uve-topic-8-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,816] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,816] INFO [Broker id=3] Leader -uve-topic-28-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,818] INFO [Broker id=3] Leader -uve-topic-14-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,821] INFO [Broker id=3] Leader -uve-topic-27-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,824] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,824] INFO [Broker id=3] Leader -uve-topic-29-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,826] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,826] INFO [Broker id=3] Leader -uve-topic-16-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,828] INFO [Broker id=3] Leader -uve-topic-10-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,830] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,830] INFO [Broker id=3] Leader -uve-topic-23-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,832] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,832] INFO [Broker id=3] Leader -uve-topic-12-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,834] INFO [Broker id=3] Leader -uve-topic-25-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,837] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,837] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,839] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,839] INFO [Broker id=3] Leader -uve-topic-27-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,841] INFO [Broker id=3] Leader -uve-topic-13-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,843] INFO [Broker id=3] Leader -uve-topic-26-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,845] INFO [Broker id=3] Leader -uve-topic-18-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,847] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,847] INFO [Broker id=3] Leader -uve-topic-9-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,850] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,850] INFO [Broker id=3] Leader -uve-topic-0-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,852] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,852] INFO [Broker id=3] Leader -uve-topic-1-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,854] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,855] INFO [Broker id=3] Leader -uve-topic-2-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,857] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,857] INFO [Broker id=3] Leader structured_syslog_topic-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,860] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,860] INFO [Broker id=3] Leader -uve-topic-6-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,862] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,862] INFO [Broker id=3] Leader -uve-topic-5-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,865] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,865] INFO [Broker id=3] Leader -uve-topic-14-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,867] INFO [Broker id=3] Leader -uve-topic-27-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,870] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,870] INFO [Broker id=3] Leader -uve-topic-5-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,872] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,872] INFO [Broker id=3] Leader -uve-topic-13-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,874] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,874] INFO [Broker id=3] Leader -uve-topic-6-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,876] INFO [Broker id=3] Leader -uve-topic-7-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,878] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,878] INFO [Broker id=3] Leader -uve-topic-8-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,881] INFO [Broker id=3] Leader -uve-topic-20-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,883] INFO [Broker id=3] Leader -uve-topic-11-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,885] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,885] INFO [Broker id=3] Leader -uve-topic-24-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,888] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,888] INFO [Broker id=3] Leader -uve-topic-4-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,890] INFO [Broker id=3] Leader -uve-topic-3-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,893] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,893] INFO [Broker id=3] Leader structured_syslog_topic-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,895] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,895] INFO [Broker id=3] Leader -uve-topic-5-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,898] INFO [Broker id=3] Leader -uve-topic-7-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,900] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,900] INFO [Broker id=3] Leader -uve-topic-13-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,903] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,903] INFO [Broker id=3] Leader -uve-topic-26-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,905] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,905] INFO [Broker id=3] Leader -uve-topic-6-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,907] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,907] INFO [Broker id=3] Leader -uve-topic-3-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,911] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,911] INFO [Broker id=3] Leader -uve-topic-2-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,913] INFO [Broker id=3] Leader -uve-topic-22-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,916] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,916] INFO [Broker id=3] Leader -uve-topic-19-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,918] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,918] INFO [Broker id=3] Leader structured_syslog_topic-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,921] INFO [Broker id=3] Leader -uve-topic-14-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,923] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,923] INFO [Broker id=3] Leader -uve-topic-9-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,926] INFO [Broker id=3] Leader -uve-topic-8-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,928] INFO [Broker id=3] Leader -uve-topic-21-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,930] INFO [Broker id=3] Leader -uve-topic-28-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,932] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,932] INFO [Broker id=3] Leader -uve-topic-15-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,935] INFO [Broker id=3] Leader -uve-topic-1-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,937] INFO [Broker id=3] Leader -uve-topic-0-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,939] INFO [Broker id=3] Leader -uve-topic-17-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,942] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,942] INFO [Broker id=3] Leader structured_syslog_topic-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,944] INFO [Broker id=3] Leader -uve-topic-13-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,947] INFO [Broker id=3] Leader -uve-topic-26-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,949] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,949] INFO [Broker id=3] Leader -uve-topic-4-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,951] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,951] INFO [Broker id=3] Leader structured_syslog_topic-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,954] INFO [Broker id=3] Leader -uve-topic-28-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,956] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,956] INFO [Broker id=3] Leader -uve-topic-15-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,958] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,958] INFO [Broker id=3] Leader -uve-topic-0-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,961] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,961] INFO [Broker id=3] Leader -uve-topic-7-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,964] INFO [Broker id=3] Leader -uve-topic-20-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,966] INFO [Broker id=3] Leader -uve-topic-28-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,968] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,968] INFO [Broker id=3] Leader -uve-topic-15-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,971] INFO [Broker id=3] Leader -uve-topic-12-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,973] INFO [Broker id=3] Leader -uve-topic-25-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,976] INFO [Broker id=3] Leader -uve-topic-3-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,978] INFO [Broker id=3] Leader -uve-topic-19-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,981] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,981] INFO [Broker id=3] Leader -uve-topic-4-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,984] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,984] INFO [Broker id=3] Leader -uve-topic-11-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:52,986] INFO [Broker id=3] Leader -uve-topic-24-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,989] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,989] INFO [Broker id=3] Leader structured_syslog_topic-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,991] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-15 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,993] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,993] INFO [Broker id=3] Leader -uve-topic-6-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,995] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:52,995] INFO [Broker id=3] Leader -uve-topic-13-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:52,998] INFO [Broker id=3] Leader -uve-topic-26-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,000] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,000] INFO [Broker id=3] Leader -uve-topic-14-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,003] INFO [Broker id=3] Leader -uve-topic-27-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,005] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,005] INFO [Broker id=3] Leader -uve-topic-18-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,008] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,008] INFO [Broker id=3] Leader -uve-topic-22-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,010] INFO [Broker id=3] Leader -uve-topic-10-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,012] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,012] INFO [Broker id=3] Leader -uve-topic-23-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,015] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,015] INFO [Broker id=3] Leader -uve-topic-6-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,018] INFO [Broker id=3] Leader -uve-topic-20-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,020] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,020] INFO [Broker id=3] Leader -uve-topic-21-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,022] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,022] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,024] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,024] INFO [Broker id=3] Leader -uve-topic-16-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,026] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,026] INFO [Broker id=3] Leader -uve-topic-29-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,029] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,029] INFO [Broker id=3] Leader -uve-topic-21-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,031] INFO [Broker id=3] Leader -uve-topic-4-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,034] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,034] INFO [Broker id=3] Leader -uve-topic-27-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,036] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,036] INFO [Broker id=3] Leader -uve-topic-14-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,038] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,038] INFO [Broker id=3] Leader -uve-topic-16-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,040] INFO [Broker id=3] Leader -uve-topic-29-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,043] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,043] INFO [Broker id=3] Leader -uve-topic-2-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,045] INFO [Broker id=3] Leader -uve-topic-2-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,047] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,047] INFO [Broker id=3] Leader -uve-topic-1-0 starts at leader epoch 5 from offset 490 with high watermark 490 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,050] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,050] INFO [Broker id=3] Leader -uve-topic-3-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,052] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,052] INFO [Broker id=3] Leader -uve-topic-26-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,054] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,054] INFO [Broker id=3] Leader -uve-topic-13-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,057] INFO [Broker id=3] Leader -uve-topic-5-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,059] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,059] INFO [Broker id=3] Leader -uve-topic-9-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,062] INFO [Broker id=3] Leader -uve-topic-17-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,064] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,065] INFO [Broker id=3] Leader -uve-topic-1-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,067] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,067] INFO [Broker id=3] Leader -uve-topic-8-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,070] INFO [Broker id=3] Leader structured_syslog_topic-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,072] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,072] INFO [Broker id=3] Leader -uve-topic-5-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,074] INFO [Broker id=3] Leader -uve-topic-22-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,076] INFO [Broker id=3] Leader -uve-topic-26-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,079] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,079] INFO [Broker id=3] Leader -uve-topic-13-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,081] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,081] INFO [Broker id=3] Leader -uve-topic-5-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,083] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,083] INFO [Broker id=3] Leader -uve-topic-16-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,086] INFO [Broker id=3] Leader -uve-topic-29-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,088] INFO [Broker id=3] Leader -uve-topic-15-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,090] INFO [Broker id=3] Leader -uve-topic-28-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,093] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,094] INFO [Broker id=3] Leader -uve-topic-8-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,096] INFO [Broker id=3] Leader -uve-topic-5-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,098] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,099] INFO [Broker id=3] Leader -uve-topic-4-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,102] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,102] INFO [Broker id=3] Leader -uve-topic-24-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,105] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,105] INFO [Broker id=3] Leader -uve-topic-11-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,107] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,107] INFO [Broker id=3] Leader -uve-topic-4-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,109] INFO [Broker id=3] Leader structured_syslog_topic-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,112] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,112] INFO [Broker id=3] Leader -uve-topic-5-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,114] INFO [Broker id=3] Leader -uve-topic-7-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,116] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,116] INFO [Broker id=3] Leader -uve-topic-18-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,119] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,119] INFO [Broker id=3] Leader -uve-topic-1-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,121] INFO [Broker id=3] Leader -uve-topic-3-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,123] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,123] INFO [Broker id=3] Leader -uve-topic-19-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,126] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,126] INFO [Broker id=3] Leader structured_syslog_topic-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,128] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-12 starts at leader epoch 5 from offset 1 with high watermark 1 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,131] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,132] INFO [Broker id=3] Leader -uve-topic-4-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,134] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,134] INFO [Broker id=3] Leader -uve-topic-25-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,136] INFO [Broker id=3] Leader -uve-topic-26-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,139] INFO [Broker id=3] Leader -uve-topic-12-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,141] INFO [Broker id=3] Leader -uve-topic-13-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,143] INFO [Broker id=3] Leader -uve-topic-4-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,146] INFO [Broker id=3] Leader -uve-topic-0-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,148] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,148] INFO [Broker id=3] Leader -uve-topic-17-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,151] INFO [Broker id=3] Leader -uve-topic-16-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,153] INFO [Broker id=3] Leader -uve-topic-29-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,156] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,156] INFO [Broker id=3] Leader -uve-topic-2-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,158] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,158] INFO [Broker id=3] Leader -uve-topic-22-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,161] INFO [Broker id=3] Leader -uve-topic-9-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,163] INFO [Broker id=3] Leader -uve-topic-21-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,166] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-3 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,168] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,168] INFO [Broker id=3] Leader -uve-topic-17-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,170] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,170] INFO [Broker id=3] Leader -uve-topic-26-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,173] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,173] INFO [Broker id=3] Leader -uve-topic-13-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,175] INFO [Broker id=3] Leader -uve-topic-15-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,177] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,177] INFO [Broker id=3] Leader -uve-topic-28-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,180] INFO [Broker id=3] Leader -uve-topic-20-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,183] INFO [Broker id=3] Leader -uve-topic-21-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,185] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,185] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 4 from offset 1 with high watermark 1 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,188] INFO [Broker id=3] Leader -uve-topic-27-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,190] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,190] INFO [Broker id=3] Leader -uve-topic-14-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,193] INFO [Broker id=3] Leader -uve-topic-25-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,196] INFO [Broker id=3] Leader -uve-topic-19-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,198] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,198] INFO [Broker id=3] Leader -uve-topic-20-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,202] INFO [Broker id=3] Leader -uve-topic-10-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,204] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,204] INFO [Broker id=3] Leader -uve-topic-24-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,207] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,207] INFO [Broker id=3] Leader -uve-topic-23-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,210] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,210] INFO [Broker id=3] Leader -uve-topic-25-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,213] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,213] INFO [Broker id=3] Leader -uve-topic-12-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,216] INFO [Broker id=3] Leader -uve-topic-27-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,218] INFO [Broker id=3] Leader -uve-topic-26-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,221] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,221] INFO [Broker id=3] Leader -uve-topic-13-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,223] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,223] INFO [Broker id=3] Leader -uve-topic-14-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,225] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,225] INFO [Broker id=3] Leader -uve-topic-6-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,228] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,228] INFO [Broker id=3] Leader -uve-topic-10-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,231] INFO [Broker id=3] Leader -uve-topic-22-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,233] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,233] INFO [Broker id=3] Leader -uve-topic-23-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,236] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,236] INFO [Broker id=3] Leader -uve-topic-18-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,238] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,238] INFO [Broker id=3] Leader -uve-topic-5-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,240] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,240] INFO [Broker id=3] Leader -uve-topic-25-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,243] INFO [Broker id=3] Leader -uve-topic-12-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,245] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,245] INFO [Broker id=3] Leader -uve-topic-18-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,247] INFO [Broker id=3] Leader -uve-topic-17-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,250] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,250] INFO [Broker id=3] Leader -uve-topic-20-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,252] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,252] INFO [Broker id=3] Leader -uve-topic-21-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,254] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,254] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 4 from offset 5 with high watermark 5 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,257] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,257] INFO [Broker id=3] Leader -uve-topic-22-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,259] INFO [Broker id=3] Leader -uve-topic-17-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,261] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,262] INFO [Broker id=3] Leader -uve-topic-16-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,264] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,264] INFO [Broker id=3] Leader -uve-topic-29-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,266] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,266] INFO [Broker id=3] Leader -uve-topic-21-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,269] INFO [Broker id=3] Leader structured_syslog_topic-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,271] INFO [Broker id=3] Leader -uve-topic-20-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,273] INFO [Broker id=3] Leader -uve-topic-27-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,276] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,276] INFO [Broker id=3] Leader -uve-topic-14-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,278] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,278] INFO [Broker id=3] Leader -uve-topic-16-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,280] INFO [Broker id=3] Leader -uve-topic-15-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,283] INFO [Broker id=3] Leader -uve-topic-29-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,285] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,285] INFO [Broker id=3] Leader -uve-topic-28-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,287] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,287] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-0 starts at leader epoch 5 from offset 6 with high watermark 6 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,289] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,290] INFO [Broker id=3] Leader -uve-topic-25-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,292] INFO [Broker id=3] Leader -uve-topic-12-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,294] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,294] INFO [Broker id=3] Leader -uve-topic-24-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,297] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,297] INFO [Broker id=3] Leader -uve-topic-11-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,300] INFO [Broker id=3] Leader -uve-topic-26-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,302] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,302] INFO [Broker id=3] Leader -uve-topic-13-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,304] INFO [Broker id=3] Leader -uve-topic-12-0 starts at leader epoch 5 from offset 145 with high watermark 145 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,306] INFO [Broker id=3] Leader -uve-topic-13-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,308] INFO [Broker id=3] Leader -uve-topic-5-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,310] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,310] INFO [Broker id=3] Leader -uve-topic-6-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,313] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,313] INFO [Broker id=3] Leader -uve-topic-9-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,315] INFO [Broker id=3] Leader -uve-topic-1-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,317] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,317] INFO [Broker id=3] Leader -uve-topic-8-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,320] INFO [Broker id=3] Leader -uve-topic-15-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,323] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,324] INFO [Broker id=3] Leader -uve-topic-28-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,326] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,326] INFO [Broker id=3] Leader -uve-topic-0-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,329] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,329] INFO [Broker id=3] Leader -uve-topic-7-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,331] INFO [Broker id=3] Leader -uve-topic-4-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,334] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,334] INFO [Broker id=3] Leader -uve-topic-3-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,336] INFO [Broker id=3] Leader -uve-topic-25-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,338] INFO [Broker id=3] Leader -uve-topic-12-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,341] INFO [Broker id=3] Leader -uve-topic-19-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,343] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,343] INFO [Broker id=3] Leader structured_syslog_topic-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,346] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,348] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,348] INFO [Broker id=3] Leader -uve-topic-7-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,351] INFO [Broker id=3] Leader -uve-topic-6-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,354] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,354] INFO [Broker id=3] Leader -uve-topic-10-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,356] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,356] INFO [Broker id=3] Leader -uve-topic-27-0 starts at leader epoch 5 from offset 1299 with high watermark 1299 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,358] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,359] INFO [Broker id=3] Leader -uve-topic-23-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,361] INFO [Broker id=3] Leader -uve-topic-14-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,363] INFO [Broker id=3] Leader -uve-topic-2-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,366] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,366] INFO [Broker id=3] Leader -uve-topic-18-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,368] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,368] INFO [Broker id=3] Leader -uve-topic-19-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,371] INFO [Broker id=3] Leader -uve-topic-22-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,373] INFO [Broker id=3] Leader -uve-topic-24-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,375] INFO [Broker id=3] Leader -uve-topic-11-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,378] INFO [Broker id=3] Leader -uve-topic-10-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,380] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,380] INFO [Broker id=3] Leader -uve-topic-23-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,382] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,383] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-28 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,385] INFO [Broker id=3] Leader -uve-topic-4-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,388] INFO [Broker id=3] Leader -uve-topic-25-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,390] INFO [Broker id=3] Leader -uve-topic-12-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,392] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,393] INFO [Broker id=3] Leader -uve-topic-5-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,395] INFO [Broker id=3] Leader -uve-topic-4-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,398] INFO [Broker id=3] Leader -uve-topic-17-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,400] INFO [Broker id=3] Leader -uve-topic-0-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,402] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,402] INFO [Broker id=3] Leader -uve-topic-1-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,405] INFO [Broker id=3] Leader -uve-topic-16-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,408] INFO [Broker id=3] Leader -uve-topic-2-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,410] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,410] INFO [Broker id=3] Leader -uve-topic-9-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,413] INFO [Broker id=3] Leader -uve-topic-25-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,415] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,415] INFO [Broker id=3] Leader -uve-topic-12-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,418] INFO [Broker id=3] Leader -uve-topic-4-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,420] INFO [Broker id=3] Leader -uve-topic-3-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,422] INFO [Broker id=3] Leader -uve-topic-3-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,425] INFO [Broker id=3] Leader -uve-topic-0-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,428] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,428] INFO [Broker id=3] Leader -uve-topic-15-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,431] INFO [Broker id=3] Leader -uve-topic-6-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,435] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,435] INFO [Broker id=3] Leader -uve-topic-7-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,439] INFO [Broker id=3] Leader -uve-topic-8-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,441] INFO [Broker id=3] Leader -uve-topic-21-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,444] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,444] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,446] INFO [Broker id=3] Leader -uve-topic-25-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,449] INFO [Broker id=3] Leader -uve-topic-12-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,452] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,452] INFO [Broker id=3] Leader -uve-topic-19-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,455] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,455] INFO [Broker id=3] Leader -uve-topic-24-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,457] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,457] INFO [Broker id=3] Leader -uve-topic-11-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,460] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,460] INFO [Broker id=3] Leader -uve-topic-4-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,462] INFO [Broker id=3] Leader -uve-topic-24-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,465] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,465] INFO [Broker id=3] Leader -uve-topic-11-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,467] INFO [Broker id=3] Leader -uve-topic-5-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,469] INFO [Broker id=3] Leader -uve-topic-6-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,472] INFO [Broker id=3] Leader -uve-topic-27-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,474] INFO [Broker id=3] Leader -uve-topic-14-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,476] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,477] INFO [Broker id=3] Leader -uve-topic-18-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,479] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,479] INFO [Broker id=3] Leader -uve-topic-19-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,481] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,481] INFO [Broker id=3] Leader -uve-topic-10-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,483] INFO [Broker id=3] Leader -uve-topic-22-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,486] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,486] INFO [Broker id=3] Leader -uve-topic-23-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,488] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,488] INFO [Broker id=3] Leader -uve-topic-18-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,491] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,491] INFO [Broker id=3] Leader -uve-topic-24-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,493] INFO [Broker id=3] Leader -uve-topic-11-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,495] INFO [Broker id=3] Leader -uve-topic-26-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,498] INFO [Broker id=3] Leader -uve-topic-13-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,500] INFO [Broker id=3] Leader -uve-topic-25-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,502] INFO [Broker id=3] Leader -uve-topic-20-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,505] INFO [Broker id=3] Leader -uve-topic-12-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,507] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,507] INFO [Broker id=3] Leader -uve-topic-22-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,510] INFO [Broker id=3] Leader -uve-topic-16-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,513] INFO [Broker id=3] Leader -uve-topic-29-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,515] INFO [Broker id=3] Leader -uve-topic-21-0 starts at leader epoch 5 from offset 1663 with high watermark 1663 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,518] INFO [Broker id=3] Leader -uve-topic-8-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,522] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,522] INFO [Broker id=3] Leader -uve-topic-17-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,526] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,526] INFO [Broker id=3] Leader -uve-topic-15-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,529] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,529] INFO [Broker id=3] Leader -uve-topic-28-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,532] INFO [Broker id=3] Leader -uve-topic-7-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,534] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,534] INFO [Broker id=3] Leader -uve-topic-10-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,536] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,537] INFO [Broker id=3] Leader -uve-topic-23-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,539] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,539] INFO [Broker id=3] Leader -uve-topic-1-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,543] INFO [Broker id=3] Leader -uve-topic-3-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,545] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,545] INFO [Broker id=3] Leader structured_syslog_topic-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,548] INFO [Broker id=3] Leader -uve-topic-5-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,552] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-6 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,555] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,555] INFO [Broker id=3] Leader -uve-topic-4-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,557] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,557] INFO [Broker id=3] Leader -uve-topic-9-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,559] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,559] INFO [Broker id=3] Leader -uve-topic-9-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,562] INFO [Broker id=3] Leader -uve-topic-19-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,564] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,564] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,567] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,567] INFO [Broker id=3] Leader -uve-topic-17-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,569] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,569] INFO [Broker id=3] Leader -uve-topic-8-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,571] INFO [Broker id=3] Leader -uve-topic-1-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,573] INFO [Broker id=3] Leader -uve-topic-0-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,575] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,575] INFO [Broker id=3] Leader -uve-topic-24-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,578] INFO [Broker id=3] Leader -uve-topic-5-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,580] INFO [Broker id=3] Leader -uve-topic-7-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,582] INFO [Broker id=3] Leader -uve-topic-6-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,584] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,584] INFO [Broker id=3] Leader -uve-topic-23-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,587] INFO [Broker id=3] Leader -uve-topic-10-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,589] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,589] INFO [Broker id=3] Leader -uve-topic-3-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,592] INFO [Broker id=3] Leader -uve-topic-2-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,594] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,594] INFO [Broker id=3] Leader -uve-topic-18-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,597] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,597] INFO [Broker id=3] Leader -uve-topic-19-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,599] INFO [Broker id=3] Leader -uve-topic-4-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,602] INFO [Broker id=3] Leader -uve-topic-5-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,605] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,605] INFO [Broker id=3] Leader -uve-topic-6-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,608] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,608] INFO [Broker id=3] Leader -uve-topic-25-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,611] INFO [Broker id=3] Leader -uve-topic-12-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,614] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,614] INFO [Broker id=3] Leader -uve-topic-0-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,617] INFO [Broker id=3] Leader -uve-topic-4-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,619] INFO [Broker id=3] Leader -uve-topic-2-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,622] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,622] INFO [Broker id=3] Leader -uve-topic-18-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,624] INFO [Broker id=3] Leader -uve-topic-1-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,627] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,627] INFO [Broker id=3] Leader -uve-topic-9-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,629] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,629] INFO [Broker id=3] Leader -uve-topic-21-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,632] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,632] INFO [Broker id=3] Leader -uve-topic-3-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,634] INFO [Broker id=3] Leader -uve-topic-23-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,637] INFO [Broker id=3] Leader -uve-topic-24-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,640] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,640] INFO [Broker id=3] Leader -uve-topic-11-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,643] INFO [Broker id=3] Leader -uve-topic-15-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,645] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,645] INFO [Broker id=3] Leader -uve-topic-3-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,648] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,648] INFO [Broker id=3] Leader -uve-topic-28-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,650] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,650] INFO [Broker id=3] Leader -uve-topic-8-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,654] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,654] INFO [Broker id=3] Leader -uve-topic-20-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,656] INFO [Broker id=3] Leader -uve-topic-7-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,658] INFO [Broker id=3] Leader -uve-topic-27-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,662] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,662] INFO [Broker id=3] Leader -uve-topic-14-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,665] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,665] INFO [Broker id=3] Leader -uve-topic-16-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,667] INFO [Broker id=3] Leader -uve-topic-29-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,669] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,670] INFO [Broker id=3] Leader -uve-topic-24-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,672] INFO [Broker id=3] Leader -uve-topic-11-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,674] INFO [Broker id=3] Leader -uve-topic-19-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,677] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,677] INFO [Broker id=3] Leader -uve-topic-24-0 starts at leader epoch 5 from offset 378 with high watermark 378 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,679] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,679] INFO [Broker id=3] Leader -uve-topic-11-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,682] INFO [Broker id=3] Leader -uve-topic-3-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,684] INFO [Broker id=3] Leader structured_syslog_topic-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,686] INFO [Broker id=3] Leader -uve-topic-26-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,689] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,689] INFO [Broker id=3] Leader -uve-topic-13-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,692] INFO [Broker id=3] Leader -uve-topic-22-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,695] INFO [Broker id=3] Leader -uve-topic-10-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,698] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,699] INFO [Broker id=3] Leader structured_syslog_topic-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,702] INFO [Broker id=3] Leader -uve-topic-5-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,705] INFO [Broker id=3] Leader -uve-topic-25-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,707] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,707] INFO [Broker id=3] Leader -uve-topic-12-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,710] INFO [Broker id=3] Leader -uve-topic-24-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,712] INFO [Broker id=3] Leader -uve-topic-11-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,715] INFO [Broker id=3] Leader -uve-topic-26-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,717] INFO [Broker id=3] Leader -uve-topic-13-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,720] INFO [Broker id=3] Leader -uve-topic-17-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,722] INFO [Broker id=3] Leader -uve-topic-20-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,724] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-29 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,727] INFO [Broker id=3] Leader -uve-topic-22-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,729] INFO [Broker id=3] Leader -uve-topic-9-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,731] INFO [Broker id=3] Leader -uve-topic-19-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,734] INFO [Broker id=3] Leader -uve-topic-18-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,736] INFO [Broker id=3] Leader -uve-topic-24-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,739] INFO [Broker id=3] Leader -uve-topic-23-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,741] INFO [Broker id=3] Leader -uve-topic-11-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,744] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,744] INFO [Broker id=3] Leader -uve-topic-10-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,746] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,746] INFO [Broker id=3] Leader -uve-topic-3-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,749] INFO [Broker id=3] Leader -uve-topic-19-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,751] INFO [Broker id=3] Leader -uve-topic-23-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,753] INFO [Broker id=3] Leader -uve-topic-10-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,755] INFO [Broker id=3] Leader -uve-topic-15-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,758] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,758] INFO [Broker id=3] Leader -uve-topic-28-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,760] INFO [Broker id=3] Leader -uve-topic-21-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,762] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,762] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 4 from offset 5 with high watermark 5 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,765] INFO [Broker id=3] Leader -uve-topic-6-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,767] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,767] INFO [Broker id=3] Leader -uve-topic-19-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,772] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,772] INFO [Broker id=3] Leader -uve-topic-3-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,774] INFO [Broker id=3] Leader -uve-topic-26-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,779] INFO [Broker id=3] Leader -uve-topic-1-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,781] INFO [Broker id=3] Leader -uve-topic-9-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,785] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,785] INFO [Broker id=3] Leader -uve-topic-0-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,787] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,787] INFO [Broker id=3] Leader -uve-topic-1-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,791] INFO [Broker id=3] Leader -uve-topic-2-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,793] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,794] INFO [Broker id=3] Leader -uve-topic-25-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,796] INFO [Broker id=3] Leader -uve-topic-12-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,798] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,798] INFO [Broker id=3] Leader -uve-topic-4-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,800] INFO [Broker id=3] Leader -uve-topic-8-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,802] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,802] INFO [Broker id=3] Leader -uve-topic-0-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,804] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,804] INFO [Broker id=3] Leader -uve-topic-16-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,807] INFO [Broker id=3] Leader -uve-topic-29-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,809] INFO [Broker id=3] Leader -uve-topic-7-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,813] INFO [Broker id=3] Leader -uve-topic-8-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,816] INFO [Broker id=3] Leader -uve-topic-2-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,818] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,818] INFO [Broker id=3] Leader -uve-topic-27-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,820] INFO [Broker id=3] Leader -uve-topic-6-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,824] INFO [Broker id=3] Leader -uve-topic-7-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,826] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,826] INFO [Broker id=3] Leader -uve-topic-27-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,828] INFO [Broker id=3] Leader -uve-topic-14-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,832] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,832] INFO [Broker id=3] Leader -uve-topic-2-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,836] INFO [Broker id=3] Leader -uve-topic-24-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,838] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,838] INFO [Broker id=3] Leader -uve-topic-11-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,843] INFO [Broker id=3] Leader -uve-topic-18-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,845] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,845] INFO [Broker id=3] Leader -uve-topic-3-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,848] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,848] INFO [Broker id=3] Leader -uve-topic-23-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,850] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,850] INFO [Broker id=3] Leader -uve-topic-10-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,853] INFO [Broker id=3] Leader -uve-topic-4-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,857] INFO [Broker id=3] Leader -uve-topic-1-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,859] INFO [Broker id=3] Leader -uve-topic-6-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,862] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,862] INFO [Broker id=3] Leader -uve-topic-0-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,864] INFO [Broker id=3] Leader -uve-topic-9-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,867] INFO [Broker id=3] Leader -uve-topic-16-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,871] INFO [Broker id=3] Leader -uve-topic-29-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,873] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,873] INFO [Broker id=3] Leader -uve-topic-2-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,877] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,877] INFO [Broker id=3] Leader -uve-topic-1-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,880] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,880] INFO [Broker id=3] Leader -uve-topic-18-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,882] INFO [Broker id=3] Leader -uve-topic-3-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,885] INFO [Broker id=3] Leader -uve-topic-19-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,887] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-19-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,887] INFO [Broker id=3] Leader -uve-topic-25-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,889] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,889] INFO [Broker id=3] Leader -uve-topic-12-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,892] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,892] INFO [Broker id=3] Leader -uve-topic-24-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,894] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-24-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,894] INFO [Broker id=3] Leader -uve-topic-11-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,896] INFO [Broker id=3] Leader -uve-topic-15-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,898] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,898] INFO [Broker id=3] Leader -uve-topic-29-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,900] INFO [Broker id=3] Leader -uve-topic-28-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,903] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,903] INFO [Broker id=3] Leader -uve-topic-8-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,905] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,905] INFO [Broker id=3] Leader -uve-topic-20-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,908] INFO [Broker id=3] Leader -uve-topic-21-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,910] INFO [Broker id=3] Leader -uve-topic-18-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,914] INFO [Broker id=3] Leader structured_syslog_topic-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,917] INFO [Broker id=3] Leader -uve-topic-5-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,919] INFO [Broker id=3] Leader -uve-topic-27-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,923] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,923] INFO [Broker id=3] Leader -uve-topic-14-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,925] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,925] INFO [Broker id=3] Leader -uve-topic-7-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,928] INFO [Broker id=3] Leader -uve-topic-20-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,931] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,931] INFO [Broker id=3] Leader -uve-topic-27-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,935] INFO [Broker id=3] Leader -uve-topic-26-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,937] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,937] INFO [Broker id=3] Leader -uve-topic-13-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,939] INFO [Broker id=3] Leader -uve-topic-14-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,941] INFO [Broker id=3] Leader -uve-topic-23-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,944] INFO [Broker id=3] Leader -uve-topic-10-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,946] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,946] INFO [Broker id=3] Leader -uve-topic-19-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,950] INFO [Broker id=3] Leader -uve-topic-22-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,952] INFO [Broker id=3] Leader structured_syslog_topic-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,955] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,955] INFO [Broker id=3] Leader -uve-topic-24-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,957] INFO [Broker id=3] Leader -uve-topic-11-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,959] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,959] INFO [Broker id=3] Leader -uve-topic-26-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,962] INFO [Broker id=3] Leader -uve-topic-25-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,965] INFO [Broker id=3] Leader -uve-topic-12-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,967] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,967] INFO [Broker id=3] Leader -uve-topic-13-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,970] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,970] INFO [Broker id=3] Leader -uve-topic-21-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,974] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,974] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 4 from offset 5 with high watermark 5 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,976] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,976] INFO [Broker id=3] Leader -uve-topic-17-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,978] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,978] INFO [Broker id=3] Leader -uve-topic-9-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,981] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,981] INFO [Broker id=3] Leader -uve-topic-23-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,983] INFO [Broker id=3] Leader -uve-topic-0-0 starts at leader epoch 5 from offset 3159 with high watermark 3159 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,985] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,986] INFO [Broker id=3] Leader -uve-topic-10-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,988] INFO [Broker id=3] Leader -uve-topic-18-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,990] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,990] INFO [Broker id=3] Leader -uve-topic-19-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:53,994] INFO [Broker id=3] Leader -uve-topic-23-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,996] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:53,996] INFO [Broker id=3] Leader -uve-topic-10-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:53,999] INFO [Broker id=3] Leader -uve-topic-2-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,001] INFO [Broker id=3] Leader -uve-topic-28-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,003] INFO [Broker id=3] Leader -uve-topic-15-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,006] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,006] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-26 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,008] INFO [Broker id=3] Leader -uve-topic-2-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,011] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,011] INFO [Broker id=3] Leader -uve-topic-13-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,013] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,013] INFO [Broker id=3] Leader -uve-topic-26-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,016] INFO [Broker id=3] Leader -uve-topic-12-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,019] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,019] INFO [Broker id=3] Leader -uve-topic-25-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,021] INFO [Broker id=3] Leader -uve-topic-14-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,024] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,024] INFO [Broker id=3] Leader -uve-topic-27-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,026] INFO [Broker id=3] Leader -uve-topic-10-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,029] INFO [Broker id=3] Leader -uve-topic-23-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,031] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-23-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,031] INFO [Broker id=3] Leader -uve-topic-12-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,033] INFO [Broker id=3] Leader -uve-topic-25-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,037] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,037] INFO [Broker id=3] Leader -uve-topic-11-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,040] INFO [Broker id=3] Leader -uve-topic-24-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,042] INFO [Broker id=3] Leader -uve-topic-4-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,045] INFO [Broker id=3] Leader -uve-topic-8-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,048] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,048] INFO [Broker id=3] Leader -uve-topic-0-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,050] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,051] INFO [Broker id=3] Leader -uve-topic-18-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,053] INFO [Broker id=3] Leader -uve-topic-2-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,056] INFO [Broker id=3] Leader -uve-topic-1-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,059] INFO [Broker id=3] Leader structured_syslog_topic-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,061] INFO [Broker id=3] Leader -uve-topic-7-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,064] INFO [Broker id=3] Leader -uve-topic-14-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,067] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,067] INFO [Broker id=3] Leader -uve-topic-27-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,069] INFO [Broker id=3] Leader -uve-topic-6-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,072] INFO [Broker id=3] Leader -uve-topic-2-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,075] INFO [Broker id=3] Leader -uve-topic-18-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,080] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-18-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,080] INFO [Broker id=3] Leader -uve-topic-5-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,083] INFO [Broker id=3] Leader -uve-topic-9-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,085] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,085] INFO [Broker id=3] Leader -uve-topic-22-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,088] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,088] INFO [Broker id=3] Leader -uve-topic-13-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,091] INFO [Broker id=3] Leader -uve-topic-26-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,093] INFO [Broker id=3] Leader -uve-topic-1-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,096] INFO [Broker id=3] Leader -uve-topic-17-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,098] INFO [Broker id=3] Leader -uve-topic-18-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,101] INFO [Broker id=3] Leader -uve-topic-21-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,103] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,103] INFO [Broker id=3] Leader -uve-topic-20-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,105] INFO [Broker id=3] Leader -uve-topic-22-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,108] INFO [Broker id=3] Leader -uve-topic-3-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,112] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,112] INFO [Broker id=3] Leader -uve-topic-19-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,114] INFO [Broker id=3] Leader -uve-topic-10-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,117] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-10-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,117] INFO [Broker id=3] Leader -uve-topic-11-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,119] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,119] INFO [Broker id=3] Leader -uve-topic-23-0 starts at leader epoch 4 from offset 584 with high watermark 584 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,123] INFO [Broker id=3] Leader -uve-topic-24-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,125] INFO [Broker id=3] Leader -uve-topic-28-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,128] INFO [Broker id=3] Leader -uve-topic-3-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,132] INFO [Broker id=3] Leader -uve-topic-15-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,135] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-23 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,138] INFO [Broker id=3] Leader -uve-topic-19-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,140] INFO [Broker id=3] Leader -uve-topic-17-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,143] INFO [Broker id=3] Leader -uve-topic-20-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,145] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,145] INFO [Broker id=3] Leader -uve-topic-29-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,149] INFO [Broker id=3] Leader -uve-topic-16-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,152] INFO [Broker id=3] Leader -uve-topic-21-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,155] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,155] INFO [Broker id=3] Leader -uve-topic-28-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,158] INFO [Broker id=3] Leader -uve-topic-29-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,161] INFO [Broker id=3] Leader -uve-topic-15-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,165] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,165] INFO [Broker id=3] Leader -uve-topic-16-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,168] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,168] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-4 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,171] INFO [Broker id=3] Leader -uve-topic-9-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,173] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,173] INFO [Broker id=3] Leader -uve-topic-1-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,176] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,176] INFO [Broker id=3] Leader -uve-topic-23-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,179] INFO [Broker id=3] Leader -uve-topic-10-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,181] INFO [Broker id=3] Leader structured_syslog_topic-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,183] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,183] INFO [Broker id=3] Leader -uve-topic-2-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,186] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,186] INFO [Broker id=3] Leader -uve-topic-22-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,189] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,189] INFO [Broker id=3] Leader -uve-topic-18-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,191] INFO [Broker id=3] Leader -uve-topic-6-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,194] INFO [Broker id=3] Leader -uve-topic-5-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,196] INFO [Broker id=3] Leader -uve-topic-14-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,199] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,199] INFO [Broker id=3] Leader -uve-topic-27-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,201] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-27-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,201] INFO [Broker id=3] Leader -uve-topic-7-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,205] INFO [Broker id=3] Leader -uve-topic-20-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,207] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,207] INFO [Broker id=3] Leader -uve-topic-0-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,209] INFO [Broker id=3] Leader -uve-topic-9-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,212] INFO [Broker id=3] Leader -uve-topic-1-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,214] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,214] INFO [Broker id=3] Leader -uve-topic-17-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,219] INFO [Broker id=3] Leader structured_syslog_topic-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,221] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,221] INFO [Broker id=3] Leader -uve-topic-5-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,224] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,224] INFO [Broker id=3] Leader -uve-topic-4-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,227] INFO [Broker id=3] Leader -uve-topic-11-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,229] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,229] INFO [Broker id=3] Leader -uve-topic-24-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,232] INFO [Broker id=3] Leader -uve-topic-13-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,236] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,236] INFO [Broker id=3] Leader -uve-topic-12-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,238] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,239] INFO [Broker id=3] Leader -uve-topic-26-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,241] INFO [Broker id=3] Leader -uve-topic-29-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,244] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,244] INFO [Broker id=3] Leader -uve-topic-16-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,247] INFO [Broker id=3] Leader -uve-topic-17-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,249] INFO [Broker id=3] Leader -uve-topic-22-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,252] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,252] INFO [Broker id=3] Leader -uve-topic-18-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,254] INFO [Broker id=3] Leader -uve-topic-21-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,257] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,257] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 4 from offset 4 with high watermark 4 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,259] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition HEALTH_CHECK_TOPIC-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,259] INFO [Broker id=3] Leader -uve-topic-17-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,261] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-17-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,261] INFO [Broker id=3] Leader -uve-topic-23-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,265] INFO [Broker id=3] Leader -uve-topic-10-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,267] INFO [Broker id=3] Leader -uve-topic-12-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,269] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-12-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,269] INFO [Broker id=3] Leader -uve-topic-25-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,272] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,272] INFO [Broker id=3] Leader -uve-topic-11-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,274] INFO [Broker id=3] Leader -uve-topic-19-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,277] INFO [Broker id=3] Leader -uve-topic-21-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,279] INFO [Broker id=3] Leader -uve-topic-20-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,281] INFO [Broker id=3] Leader -uve-topic-28-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,285] INFO [Broker id=3] Leader -uve-topic-15-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,288] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,288] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-20 starts at leader epoch 5 from offset 6 with high watermark 6 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,290] INFO [Broker id=3] Leader -uve-topic-22-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,293] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,293] INFO [Broker id=3] Leader -uve-topic-18-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,295] INFO [Broker id=3] Leader -uve-topic-14-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,297] INFO [Broker id=3] Leader -uve-topic-13-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,300] INFO [Broker id=3] Leader -uve-topic-26-0 starts at leader epoch 4 from offset 1236 with high watermark 1236 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,302] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-26-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,302] INFO [Broker id=3] Leader -uve-topic-27-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,304] INFO [Broker id=3] Leader -uve-topic-6-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,307] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-6-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,307] INFO [Broker id=3] Leader -uve-topic-1-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,312] INFO [Broker id=3] Leader -uve-topic-0-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,315] INFO [Broker id=3] Leader -uve-topic-22-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,317] INFO [Broker id=3] Leader -uve-topic-4-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,320] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,320] INFO [Broker id=3] Leader -uve-topic-3-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,322] INFO [Broker id=3] Leader -uve-topic-9-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,325] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,325] INFO [Broker id=3] Leader -uve-topic-28-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,328] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-28-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,328] INFO [Broker id=3] Leader -uve-topic-29-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,330] INFO [Broker id=3] Leader -uve-topic-15-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,334] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,334] INFO [Broker id=3] Leader -uve-topic-16-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,337] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,337] INFO [Broker id=3] Leader -uve-topic-8-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,340] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,340] INFO [Broker id=3] Leader -uve-topic-2-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,344] INFO [Broker id=3] Leader -uve-topic-3-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,346] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,346] INFO [Broker id=3] Leader -uve-topic-9-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,349] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,349] INFO [Broker id=3] Leader -uve-topic-2-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,353] INFO [Broker id=3] Leader -uve-topic-1-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,356] INFO [Broker id=3] Leader structured_syslog_topic-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,359] INFO [Broker id=3] Leader -uve-topic-22-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,362] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,362] INFO [Broker id=3] Leader -uve-topic-1-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,364] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-1-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,364] INFO [Broker id=3] Leader -uve-topic-0-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,367] INFO [Broker id=3] Leader -uve-topic-9-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,369] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,369] INFO [Broker id=3] Leader -uve-topic-4-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,373] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-4-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,373] INFO [Broker id=3] Leader -uve-topic-6-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,375] INFO [Broker id=3] Leader -uve-topic-5-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,377] INFO [Broker id=3] Leader -uve-topic-9-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,380] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,380] INFO [Broker id=3] Leader -uve-topic-22-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,383] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-22-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,383] INFO [Broker id=3] Leader -uve-topic-1-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,385] INFO [Broker id=3] Leader -uve-topic-17-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,388] INFO [Broker id=3] Leader -uve-topic-3-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,390] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-3-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,390] INFO [Broker id=3] Leader -uve-topic-19-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,392] INFO [Broker id=3] Leader -uve-topic-4-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,395] INFO [Broker id=3] Leader -uve-topic-5-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,398] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-5-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,398] INFO [Broker id=3] Leader -uve-topic-20-0 starts at leader epoch 5 from offset 1774 with high watermark 1774 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,400] INFO [Broker id=3] Leader -uve-topic-28-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,403] INFO [Broker id=3] Leader -uve-topic-3-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,407] INFO [Broker id=3] Leader -uve-topic-15-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,411] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-17 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,415] INFO [Broker id=3] Leader -uve-topic-8-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,419] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,419] INFO [Broker id=3] Leader -uve-topic-0-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,423] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-0-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,423] INFO [Broker id=3] Leader -uve-topic-17-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,427] INFO [Broker id=3] Leader -uve-topic-20-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,431] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-20-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,431] INFO [Broker id=3] Leader -uve-topic-29-0 starts at leader epoch 4 from offset 850 with high watermark 850 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,438] INFO [Broker id=3] Leader -uve-topic-16-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,442] INFO [Broker id=3] Leader -uve-topic-21-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,445] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,445] INFO [Broker id=3] Leader -uve-topic-2-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,449] INFO [Broker id=3] Leader -uve-topic-9-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,451] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-9-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,451] INFO [Broker id=3] Leader -uve-topic-1-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,456] INFO [Broker id=3] Leader -uve-topic-23-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,459] INFO [Broker id=3] Leader -uve-topic-10-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,462] INFO [Broker id=3] Leader -uve-topic-17-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,466] INFO [Broker id=3] Leader structured_syslog_topic-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,470] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition structured_syslog_topic-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,470] INFO [Broker id=3] Leader -uve-topic-2-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,474] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-2-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,474] INFO [Broker id=3] Leader -uve-topic-14-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,476] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,476] INFO [Broker id=3] Leader -uve-topic-27-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,479] INFO [Broker id=3] Leader -uve-topic-7-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,483] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-7-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,483] INFO [Broker id=3] Leader -uve-topic-6-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,487] INFO [Broker id=3] Leader -uve-topic-13-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,491] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-13-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,491] INFO [Broker id=3] Leader -uve-topic-26-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,495] INFO [Broker id=3] Leader -uve-topic-14-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,499] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-14-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,499] INFO [Broker id=3] Leader -uve-topic-8-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,503] INFO [Broker id=3] Leader -uve-topic-0-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,507] INFO [Broker id=3] Leader -uve-topic-21-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,510] INFO [Broker id=3] Leader -uve-topic-12-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,515] INFO [Broker id=3] Leader -uve-topic-25-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,519] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-25-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,519] INFO [Broker id=3] Leader -uve-topic-21-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,523] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-21-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,523] INFO [Broker id=3] Leader -uve-topic-0-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,528] INFO [Broker id=3] Leader -uve-topic-22-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,532] INFO [Broker id=3] Leader -uve-topic-9-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-10 01:58:54,535] INFO [Broker id=3] Leader -uve-topic-8-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,539] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-8-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,539] INFO [Broker id=3] Leader -uve-topic-29-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,543] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-29-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,543] INFO [Broker id=3] Leader -uve-topic-11-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,547] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-11-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,547] INFO [Broker id=3] Leader -uve-topic-24-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,552] INFO [Broker id=3] Leader -uve-topic-18-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,556] INFO [Broker id=3] Leader -uve-topic-29-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,560] INFO [Broker id=3] Leader -uve-topic-15-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,564] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-15-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,564] INFO [Broker id=3] Leader -uve-topic-16-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,568] INFO [Broker id=3] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 2 epoch 3 for partition -uve-topic-16-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-10 01:58:54,568] INFO [Broker id=3] Leader -uve-topic-7-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-10 01:58:54,581] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 3 with correlation id 2 (state.change.logger)
[2025-02-10 01:58:54,586] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 3 from controller 2 for 960 partitions (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,587] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-23-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-24-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-25-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-20-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-21-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,588] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-29-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,589] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-2-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-0-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,590] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-12-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-13-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition structured_syslog_topic-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-14-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-6-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,591] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-7-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,592] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-17-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,593] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 3 for partition -uve-topic-18-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:54,601] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 3 with correlation id 4 (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 5 from controller 2 for 960 partitions (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-23-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,345] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-24-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-25-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-20-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-21-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,346] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-29-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-2-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,347] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-0-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,353] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-12-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-13-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition structured_syslog_topic-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,354] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-14-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,355] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-6-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-7-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,356] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-17-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,357] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 2 with correlation id 5 epoch 3 for partition -uve-topic-18-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:55,365] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 3 with correlation id 6 (state.change.logger)
[2025-02-10 01:58:56,724] INFO [Controller id=3 epoch=4] Sending UpdateMetadata request to brokers Set(3) for 0 partitions (state.change.logger)
[2025-02-10 01:58:56,789] INFO [Controller id=3 epoch=4] Sending LeaderAndIsr request to broker 3 with 960 become-leader and 0 become-follower partitions (state.change.logger)
[2025-02-10 01:58:56,792] INFO [Controller id=3 epoch=4] Sending UpdateMetadata request to brokers Set(3) for 960 partitions (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 3 for 960 partitions (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-23-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,821] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-24-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-25-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-20-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-21-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,822] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-29-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-2-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,823] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-0-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-12-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,824] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-13-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition structured_syslog_topic-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-14-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-7-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,825] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,826] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-17-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,827] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 1 epoch 4 for partition -uve-topic-18-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:56,840] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 4 with correlation id 2 (state.change.logger)
[2025-02-10 01:58:56,927] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,928] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,929] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,930] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,931] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,932] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,933] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,934] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,935] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,936] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,937] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,938] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,939] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,940] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,941] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,942] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,943] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,944] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,945] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,946] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,957] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,957] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:56,958] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,022] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,023] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,024] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,025] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,026] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,027] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,028] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,029] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,030] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-15 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-16 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,031] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-23 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-27 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-18 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,032] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-24 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-21 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-8 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-22 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-14 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-12 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,033] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-17 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-20 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-5 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-6 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-7 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-6 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-8-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-3 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-21 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-19 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-8 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-0 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-1 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-28 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-9 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-9 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-10 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-13 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-16 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-18-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-17 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-28 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-2 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-3 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,034] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-2 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-29 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-2-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-26 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-27 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-13 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-29-0 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-1 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-20-25 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-26 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-14 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-15 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-4 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-22 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition structured_syslog_topic-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-29 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-23 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-25 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-23-24 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-7 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-12 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-18 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-11 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-5 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-4 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-10 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-11 state changed to (Leader:3,ISR:3,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-20 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-19 state changed to (Leader:3,ISR:3,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-10 01:58:57,035] INFO [Controller id=3 epoch=4] Sending LeaderAndIsr request to broker 3 with 960 become-leader and 0 become-follower partitions (state.change.logger)
[2025-02-10 01:58:57,036] INFO [Controller id=3 epoch=4] Sending UpdateMetadata request to brokers Set(3) for 960 partitions (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 3 from controller 3 for 960 partitions (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,040] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-23-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-24-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-25-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-20-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-21-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,041] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-29-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-2-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-0-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,042] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-12-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-13-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition structured_syslog_topic-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-14-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-6-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,043] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-7-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-17-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,044] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,045] INFO [Broker id=3] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 4 for partition -uve-topic-18-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-10 01:58:57,051] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 4 with correlation id 4 (state.change.logger)