[2025-01-27 02:07:23,707] 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-01-27 02:07:23,754] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 1 for 960 partitions (state.change.logger)
[2025-01-27 02:07:24,879] 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-01-27 02:07:24,886] 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-01-27 02:07:24,887] 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-01-27 02:07:24,887] INFO [Broker id=3] Follower -uve-topic-16-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,887] 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-01-27 02:07:24,888] 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-01-27 02:07:24,891] 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-01-27 02:07:24,895] INFO [Broker id=3] Follower -uve-topic-27-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,896] 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 -1. (state.change.logger)
[2025-01-27 02:07:24,896] INFO [Broker id=3] Follower -uve-topic-5-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,896] INFO [Broker id=3] Follower -uve-topic-16-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,900] 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-01-27 02:07:24,901] INFO [Broker id=3] Follower -uve-topic-17-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,909] INFO [Broker id=3] Follower -uve-topic-21-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,914] 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-01-27 02:07:24,914] 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-01-27 02:07:24,915] INFO [Broker id=3] Follower -uve-topic-13-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,917] INFO [Broker id=3] Follower -uve-topic-26-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,918] 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-01-27 02:07:24,918] 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 -1. (state.change.logger)
[2025-01-27 02:07:24,919] INFO [Broker id=3] Follower -uve-topic-17-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,926] INFO [Broker id=3] Follower -uve-topic-9-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,927] 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-01-27 02:07:24,927] 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-01-27 02:07:24,933] 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-01-27 02:07:24,933] INFO [Broker id=3] Follower -uve-topic-3-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,933] INFO [Broker id=3] Follower -uve-topic-2-0 starts at leader epoch 2 from offset 530 with high watermark 529. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,934] 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-01-27 02:07:24,935] 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-01-27 02:07:24,935] INFO [Broker id=3] Follower -uve-topic-15-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,935] 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-01-27 02:07:24,936] 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-01-27 02:07:24,936] INFO [Broker id=3] Follower -uve-topic-7-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,936] 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 -1. (state.change.logger)
[2025-01-27 02:07:24,936] 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-01-27 02:07:24,936] 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 -1. (state.change.logger)
[2025-01-27 02:07:24,936] INFO [Broker id=3] Follower -uve-topic-21-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,937] 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-01-27 02:07:24,937] 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-01-27 02:07:24,937] INFO [Broker id=3] Follower -uve-topic-4-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,937] INFO [Broker id=3] Follower -uve-topic-17-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,937] 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-01-27 02:07:24,938] 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-01-27 02:07:24,938] 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-01-27 02:07:24,938] INFO [Broker id=3] Follower -uve-topic-10-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,943] 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-01-27 02:07:24,944] 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-01-27 02:07:24,944] 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-01-27 02:07:24,944] INFO [Broker id=3] Follower -uve-topic-12-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,944] INFO [Broker id=3] Follower -uve-topic-19-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,945] 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-01-27 02:07:24,951] INFO [Broker id=3] Follower -uve-topic-16-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,951] 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-01-27 02:07:24,951] 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 -1. (state.change.logger)
[2025-01-27 02:07:24,951] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-14 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,951] 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-01-27 02:07:24,951] INFO [Broker id=3] Follower -uve-topic-9-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,952] 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-01-27 02:07:24,952] INFO [Broker id=3] Follower -uve-topic-10-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,954] 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-01-27 02:07:24,955] INFO [Broker id=3] Follower -uve-topic-14-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,957] INFO [Broker id=3] Follower -uve-topic-27-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,957] 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-01-27 02:07:24,962] 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-01-27 02:07:24,963] 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-01-27 02:07:24,969] INFO [Broker id=3] Follower -uve-topic-21-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,969] 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-01-27 02:07:24,970] 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-01-27 02:07:24,970] 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-01-27 02:07:24,970] 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-01-27 02:07:24,972] INFO [Broker id=3] Follower -uve-topic-16-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,973] 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-01-27 02:07:24,973] INFO [Broker id=3] Follower -uve-topic-13-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,974] INFO [Broker id=3] Follower -uve-topic-26-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,974] 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-01-27 02:07:24,974] INFO [Broker id=3] Follower -uve-topic-5-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,982] 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 -1. (state.change.logger)
[2025-01-27 02:07:24,982] 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-01-27 02:07:24,982] 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-01-27 02:07:24,987] 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-01-27 02:07:24,988] 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 -1. (state.change.logger)
[2025-01-27 02:07:24,988] 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-01-27 02:07:24,988] 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-01-27 02:07:24,988] INFO [Broker id=3] Follower -uve-topic-19-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,988] INFO [Broker id=3] Follower -uve-topic-25-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:24,995] 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-01-27 02:07:24,997] 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-01-27 02:07:25,002] 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-01-27 02:07:25,002] 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-01-27 02:07:25,002] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,002] 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-01-27 02:07:25,002] 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-01-27 02:07:25,002] INFO [Broker id=3] Follower -uve-topic-16-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,003] INFO [Broker id=3] Follower -uve-topic-7-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,003] 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-01-27 02:07:25,003] INFO [Broker id=3] Follower -uve-topic-22-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,004] 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-01-27 02:07:25,004] INFO [Broker id=3] Follower -uve-topic-24-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,004] INFO [Broker id=3] Follower -uve-topic-11-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,008] INFO [Broker id=3] Follower -uve-topic-17-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,008] 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-01-27 02:07:25,008] 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-01-27 02:07:25,008] 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-01-27 02:07:25,008] 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-01-27 02:07:25,008] INFO [Broker id=3] Follower -uve-topic-15-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,008] INFO [Broker id=3] Follower -uve-topic-28-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,012] 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-01-27 02:07:25,014] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,016] 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-01-27 02:07:25,017] INFO [Broker id=3] Follower -uve-topic-3-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,017] 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-01-27 02:07:25,021] INFO [Broker id=3] Follower -uve-topic-21-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,022] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-11 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,022] INFO [Broker id=3] Follower -uve-topic-0-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,022] INFO [Broker id=3] Follower -uve-topic-24-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,022] 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-01-27 02:07:25,022] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,022] INFO [Broker id=3] Follower -uve-topic-10-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,025] INFO [Broker id=3] Follower -uve-topic-19-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,025] 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-01-27 02:07:25,025] INFO [Broker id=3] Follower -uve-topic-3-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,028] 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-01-27 02:07:25,028] 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-01-27 02:07:25,031] 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-01-27 02:07:25,032] INFO [Broker id=3] Follower -uve-topic-16-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,037] 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-01-27 02:07:25,037] 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-01-27 02:07:25,056] 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-01-27 02:07:25,057] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,057] 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-01-27 02:07:25,057] 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-01-27 02:07:25,057] INFO [Broker id=3] Follower -uve-topic-13-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,057] 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-01-27 02:07:25,057] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] INFO [Broker id=3] Follower -uve-topic-12-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,058] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-27 starts at leader epoch 2 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,058] INFO [Broker id=3] Follower -uve-topic-16-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,058] 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-01-27 02:07:25,059] 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-01-27 02:07:25,059] 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-01-27 02:07:25,059] 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-01-27 02:07:25,059] INFO [Broker id=3] Follower -uve-topic-14-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,067] INFO [Broker id=3] Follower -uve-topic-15-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,067] 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-01-27 02:07:25,067] INFO [Broker id=3] Follower -uve-topic-28-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,067] INFO [Broker id=3] Follower -uve-topic-27-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,067] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,067] 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-01-27 02:07:25,068] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,068] INFO [Broker id=3] Follower -uve-topic-16-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,068] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,068] 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-01-27 02:07:25,071] INFO [Broker id=3] Follower -uve-topic-28-0 starts at leader epoch 3 from offset 768 with high watermark 768. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,073] INFO [Broker id=3] Follower -uve-topic-21-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,073] INFO [Broker id=3] Follower -uve-topic-17-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,073] 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-01-27 02:07:25,074] INFO [Broker id=3] Follower -uve-topic-21-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,074] 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-01-27 02:07:25,074] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,074] 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-01-27 02:07:25,074] 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-01-27 02:07:25,074] 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-01-27 02:07:25,075] INFO [Broker id=3] Follower -uve-topic-26-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,075] INFO [Broker id=3] Follower -uve-topic-13-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,075] INFO [Broker id=3] Follower -uve-topic-15-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,075] INFO [Broker id=3] Follower -uve-topic-28-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,075] 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-01-27 02:07:25,075] 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-01-27 02:07:25,075] INFO [Broker id=3] Follower -uve-topic-3-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,080] INFO [Broker id=3] Follower -uve-topic-19-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,080] 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-01-27 02:07:25,080] 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-01-27 02:07:25,080] INFO [Broker id=3] Follower -uve-topic-25-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,080] 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-01-27 02:07:25,080] 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-01-27 02:07:25,080] 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-01-27 02:07:25,087] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,091] 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-01-27 02:07:25,091] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-5 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,095] 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-01-27 02:07:25,096] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-24 starts at leader epoch 2 from offset 5 with high watermark 5. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,096] 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-01-27 02:07:25,096] INFO [Broker id=3] Follower -uve-topic-9-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,096] 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-01-27 02:07:25,097] 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-01-27 02:07:25,097] INFO [Broker id=3] Follower -uve-topic-22-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,097] INFO [Broker id=3] Follower -uve-topic-10-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,097] 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-01-27 02:07:25,098] 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-01-27 02:07:25,098] INFO [Broker id=3] Follower -uve-topic-17-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,098] INFO [Broker id=3] Follower -uve-topic-22-0 starts at leader epoch 3 from offset 2840 with high watermark 2840. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,098] INFO [Broker id=3] Follower -uve-topic-14-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,098] 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-01-27 02:07:25,098] 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-01-27 02:07:25,098] INFO [Broker id=3] Follower -uve-topic-21-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,098] INFO [Broker id=3] Follower -uve-topic-28-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,098] INFO [Broker id=3] Follower -uve-topic-15-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,101] INFO [Broker id=3] Follower -uve-topic-16-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,102] 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-01-27 02:07:25,102] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,102] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,102] 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-01-27 02:07:25,102] 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-01-27 02:07:25,102] INFO [Broker id=3] Follower -uve-topic-14-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,102] 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-01-27 02:07:25,102] INFO [Broker id=3] Follower -uve-topic-7-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,102] 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-01-27 02:07:25,102] INFO [Broker id=3] Follower -uve-topic-14-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,104] INFO [Broker id=3] Follower -uve-topic-27-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,104] INFO [Broker id=3] Follower -uve-topic-28-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,104] INFO [Broker id=3] Follower -uve-topic-15-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,104] 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-01-27 02:07:25,104] INFO [Broker id=3] Follower -uve-topic-0-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,104] 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-01-27 02:07:25,104] 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-01-27 02:07:25,104] 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-01-27 02:07:25,104] 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-01-27 02:07:25,104] 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-01-27 02:07:25,107] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,107] 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-01-27 02:07:25,107] 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-01-27 02:07:25,107] 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-01-27 02:07:25,110] INFO [Broker id=3] Follower -uve-topic-13-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,110] INFO [Broker id=3] Follower -uve-topic-26-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,110] 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-01-27 02:07:25,110] 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-01-27 02:07:25,110] 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-01-27 02:07:25,111] 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-01-27 02:07:25,111] INFO [Broker id=3] Follower -uve-topic-11-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,111] INFO [Broker id=3] Follower -uve-topic-24-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,112] 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-01-27 02:07:25,112] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,112] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,112] 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-01-27 02:07:25,113] 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-01-27 02:07:25,113] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,113] 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-01-27 02:07:25,113] 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-01-27 02:07:25,113] 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-01-27 02:07:25,113] 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-01-27 02:07:25,113] 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-01-27 02:07:25,113] INFO [Broker id=3] Follower -uve-topic-3-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,113] 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-01-27 02:07:25,113] INFO [Broker id=3] Follower -uve-topic-14-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,113] 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-01-27 02:07:25,113] 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-01-27 02:07:25,113] INFO [Broker id=3] Follower -uve-topic-15-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,114] 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-01-27 02:07:25,114] INFO [Broker id=3] Follower -uve-topic-1-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,114] 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-01-27 02:07:25,115] 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-01-27 02:07:25,115] 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-01-27 02:07:25,115] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,115] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,115] INFO [Broker id=3] Follower -uve-topic-13-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,115] INFO [Broker id=3] Follower -uve-topic-12-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,115] INFO [Broker id=3] Follower -uve-topic-25-0 starts at leader epoch 3 from offset 388 with high watermark 388. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,115] 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-01-27 02:07:25,115] 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-01-27 02:07:25,115] 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-01-27 02:07:25,115] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,115] INFO [Broker id=3] Follower -uve-topic-13-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,115] INFO [Broker id=3] Follower -uve-topic-26-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,115] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,115] 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-01-27 02:07:25,115] INFO [Broker id=3] Follower -uve-topic-28-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,115] INFO [Broker id=3] Follower -uve-topic-15-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,116] 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-01-27 02:07:25,116] 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-01-27 02:07:25,116] INFO [Broker id=3] Follower -uve-topic-10-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,116] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,116] INFO [Broker id=3] Follower -uve-topic-24-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,116] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-21 starts at leader epoch 2 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,116] INFO [Broker id=3] Follower -uve-topic-19-0 starts at leader epoch 2 from offset 156 with high watermark 156. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,116] 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-01-27 02:07:25,116] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-2 starts at leader epoch 3 from offset 8 with high watermark 8. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,116] INFO [Broker id=3] Follower -uve-topic-14-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,116] 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-01-27 02:07:25,116] 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-01-27 02:07:25,116] 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-01-27 02:07:25,116] 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-01-27 02:07:25,116] 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-01-27 02:07:25,116] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,117] INFO [Broker id=3] Follower -uve-topic-27-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,117] 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-01-27 02:07:25,117] 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-01-27 02:07:25,117] INFO [Broker id=3] Follower -uve-topic-16-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,117] INFO [Broker id=3] Follower -uve-topic-21-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,117] INFO [Broker id=3] Follower -uve-topic-0-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,117] INFO [Broker id=3] Follower -uve-topic-4-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,117] 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-01-27 02:07:25,117] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,117] INFO [Broker id=3] Follower -uve-topic-14-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,117] 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-01-27 02:07:25,117] 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-01-27 02:07:25,117] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,117] 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-01-27 02:07:25,117] 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-01-27 02:07:25,117] 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-01-27 02:07:25,117] INFO [Broker id=3] Follower -uve-topic-25-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,118] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-18 starts at leader epoch 2 from offset 8 with high watermark 8. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,118] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,118] 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-01-27 02:07:25,118] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,118] 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-01-27 02:07:25,118] INFO [Broker id=3] Follower -uve-topic-9-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,118] INFO [Broker id=3] Follower -uve-topic-0-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,118] 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-01-27 02:07:25,118] 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-01-27 02:07:25,118] 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-01-27 02:07:25,118] 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-01-27 02:07:25,118] 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-01-27 02:07:25,118] INFO [Broker id=3] Follower -uve-topic-14-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,118] 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-01-27 02:07:25,118] INFO [Broker id=3] Follower -uve-topic-5-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,118] INFO [Broker id=3] Follower -uve-topic-13-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,118] 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-01-27 02:07:25,118] 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-01-27 02:07:25,119] 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-01-27 02:07:25,119] 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-01-27 02:07:25,120] INFO [Broker id=3] Follower -uve-topic-11-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,120] INFO [Broker id=3] Follower -uve-topic-24-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,120] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,120] INFO [Broker id=3] Follower -uve-topic-3-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,120] 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-01-27 02:07:25,120] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,121] INFO [Broker id=3] Follower -uve-topic-7-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,123] INFO [Broker id=3] Follower -uve-topic-13-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,123] 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-01-27 02:07:25,123] 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-01-27 02:07:25,123] INFO [Broker id=3] Follower -uve-topic-3-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,123] 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-01-27 02:07:25,123] INFO [Broker id=3] Follower -uve-topic-22-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,123] 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-01-27 02:07:25,123] 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-01-27 02:07:25,123] INFO [Broker id=3] Follower -uve-topic-14-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,123] 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-01-27 02:07:25,123] 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-01-27 02:07:25,123] INFO [Broker id=3] Follower -uve-topic-21-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,124] INFO [Broker id=3] Follower -uve-topic-28-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,124] INFO [Broker id=3] Follower -uve-topic-15-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,124] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,124] 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-01-27 02:07:25,124] 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-01-27 02:07:25,128] 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-01-27 02:07:25,130] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,130] 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-01-27 02:07:25,130] 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-01-27 02:07:25,130] 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-01-27 02:07:25,130] INFO [Broker id=3] Follower -uve-topic-28-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,131] 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-01-27 02:07:25,131] INFO [Broker id=3] Follower -uve-topic-0-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,131] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,131] 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-01-27 02:07:25,132] INFO [Broker id=3] Follower -uve-topic-28-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,132] INFO [Broker id=3] Follower -uve-topic-15-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,133] 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-01-27 02:07:25,133] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,133] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,133] 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-01-27 02:07:25,133] 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-01-27 02:07:25,155] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,159] INFO [Broker id=3] Follower -uve-topic-24-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,159] 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-01-27 02:07:25,159] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-15 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,160] 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-01-27 02:07:25,160] 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-01-27 02:07:25,160] INFO [Broker id=3] Follower -uve-topic-26-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,160] INFO [Broker id=3] Follower -uve-topic-14-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,160] 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-01-27 02:07:25,161] 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-01-27 02:07:25,161] INFO [Broker id=3] Follower -uve-topic-22-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,161] 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-01-27 02:07:25,161] 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-01-27 02:07:25,161] 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-01-27 02:07:25,161] 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-01-27 02:07:25,161] 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-01-27 02:07:25,161] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-25 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,161] INFO [Broker id=3] Follower -uve-topic-16-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,162] 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-01-27 02:07:25,162] INFO [Broker id=3] Follower -uve-topic-21-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,162] INFO [Broker id=3] Follower -uve-topic-4-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,162] INFO [Broker id=3] Follower -uve-topic-27-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,162] 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-01-27 02:07:25,168] 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-01-27 02:07:25,168] 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-01-27 02:07:25,168] 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-01-27 02:07:25,169] 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-01-27 02:07:25,169] INFO [Broker id=3] Follower -uve-topic-1-0 starts at leader epoch 3 from offset 529 with high watermark 529. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,169] INFO [Broker id=3] Follower -uve-topic-3-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,175] 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-01-27 02:07:25,175] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,175] INFO [Broker id=3] Follower -uve-topic-5-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,176] 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-01-27 02:07:25,176] 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-01-27 02:07:25,176] INFO [Broker id=3] Follower -uve-topic-1-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,176] 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-01-27 02:07:25,176] 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-01-27 02:07:25,176] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,176] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,176] 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-01-27 02:07:25,176] INFO [Broker id=3] Follower -uve-topic-13-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,176] 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-01-27 02:07:25,176] 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-01-27 02:07:25,177] 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-01-27 02:07:25,177] INFO [Broker id=3] Follower -uve-topic-15-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,177] INFO [Broker id=3] Follower -uve-topic-28-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,177] 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-01-27 02:07:25,177] INFO [Broker id=3] Follower -uve-topic-5-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,177] 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-01-27 02:07:25,177] INFO [Broker id=3] Follower -uve-topic-24-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,177] INFO [Broker id=3] Follower -uve-topic-11-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,177] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,178] 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-01-27 02:07:25,178] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,178] INFO [Broker id=3] Follower -uve-topic-7-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,178] 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-01-27 02:07:25,178] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,178] INFO [Broker id=3] Follower -uve-topic-3-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,178] 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-01-27 02:07:25,178] 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-01-27 02:07:25,178] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-12 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,178] INFO [Broker id=3] Follower -uve-topic-4-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,178] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,179] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,183] 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-01-27 02:07:25,183] 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-01-27 02:07:25,184] INFO [Broker id=3] Follower -uve-topic-4-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,184] INFO [Broker id=3] Follower -uve-topic-0-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,184] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,184] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,185] 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-01-27 02:07:25,189] 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-01-27 02:07:25,189] INFO [Broker id=3] Follower -uve-topic-22-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,189] 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-01-27 02:07:25,189] INFO [Broker id=3] Follower -uve-topic-21-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,189] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-3 starts at leader epoch 2 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,189] 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-01-27 02:07:25,190] 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-01-27 02:07:25,190] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,190] 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-01-27 02:07:25,190] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,190] 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-01-27 02:07:25,190] 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-01-27 02:07:25,190] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,190] 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-01-27 02:07:25,190] INFO [Broker id=3] Follower -uve-topic-14-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,190] INFO [Broker id=3] Follower -uve-topic-25-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,191] INFO [Broker id=3] Follower -uve-topic-19-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,191] 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-01-27 02:07:25,191] 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-01-27 02:07:25,191] INFO [Broker id=3] Follower -uve-topic-24-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,191] 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-01-27 02:07:25,191] INFO [Broker id=3] Follower -uve-topic-25-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,191] 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-01-27 02:07:25,192] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,192] 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-01-27 02:07:25,192] INFO [Broker id=3] Follower -uve-topic-13-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,192] 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-01-27 02:07:25,192] 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-01-27 02:07:25,192] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,192] INFO [Broker id=3] Follower -uve-topic-22-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,192] 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-01-27 02:07:25,192] 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-01-27 02:07:25,192] 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-01-27 02:07:25,192] INFO [Broker id=3] Follower -uve-topic-25-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,193] INFO [Broker id=3] Follower -uve-topic-12-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,193] 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-01-27 02:07:25,193] 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-01-27 02:07:25,193] 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-01-27 02:07:25,193] 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-01-27 02:07:25,193] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-19 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,193] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,193] INFO [Broker id=3] Follower -uve-topic-17-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,193] INFO [Broker id=3] Follower -uve-topic-16-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,193] 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-01-27 02:07:25,193] INFO [Broker id=3] Follower -uve-topic-21-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,193] 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-01-27 02:07:25,193] 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-01-27 02:07:25,193] INFO [Broker id=3] Follower -uve-topic-27-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] 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-01-27 02:07:25,194] 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-01-27 02:07:25,194] INFO [Broker id=3] Follower -uve-topic-15-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] 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-01-27 02:07:25,194] INFO [Broker id=3] Follower -uve-topic-28-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-0 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] INFO [Broker id=3] Follower -uve-topic-25-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] INFO [Broker id=3] Follower -uve-topic-12-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] INFO [Broker id=3] Follower -uve-topic-24-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,194] INFO [Broker id=3] Follower -uve-topic-26-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,194] 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-01-27 02:07:25,195] INFO [Broker id=3] Follower -uve-topic-12-0 starts at leader epoch 3 from offset 156 with high watermark 156. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,195] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,213] INFO [Broker id=3] Follower -uve-topic-5-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,213] 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-01-27 02:07:25,213] 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-01-27 02:07:25,213] INFO [Broker id=3] Follower -uve-topic-1-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,214] 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-01-27 02:07:25,215] 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-01-27 02:07:25,232] INFO [Broker id=3] Follower -uve-topic-28-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,232] INFO [Broker id=3] Follower -uve-topic-0-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,232] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,232] INFO [Broker id=3] Follower -uve-topic-4-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,232] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,232] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,232] 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-01-27 02:07:25,233] 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-01-27 02:07:25,233] 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-01-27 02:07:25,233] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-9 starts at leader epoch 2 from offset 7 with high watermark 7. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,233] INFO [Broker id=3] Follower -uve-topic-7-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,233] 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-01-27 02:07:25,233] INFO [Broker id=3] Follower -uve-topic-10-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,233] INFO [Broker id=3] Follower -uve-topic-27-0 starts at leader epoch 3 from offset 982 with high watermark 982. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,233] 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-01-27 02:07:25,233] INFO [Broker id=3] Follower -uve-topic-14-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,233] 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-01-27 02:07:25,233] 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-01-27 02:07:25,233] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,233] INFO [Broker id=3] Follower -uve-topic-22-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,233] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,233] INFO [Broker id=3] Follower -uve-topic-11-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,233] 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-01-27 02:07:25,234] 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-01-27 02:07:25,234] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-4-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-25-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-12-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-5-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,234] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-0-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-1-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,234] 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-01-27 02:07:25,234] 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-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-25-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] 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-01-27 02:07:25,234] INFO [Broker id=3] Follower -uve-topic-4-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,234] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,234] 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-01-27 02:07:25,235] INFO [Broker id=3] Follower -uve-topic-0-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,250] INFO [Broker id=3] Follower -uve-topic-15-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,251] 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-01-27 02:07:25,252] INFO [Broker id=3] Follower -uve-topic-7-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,252] 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-01-27 02:07:25,252] 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-01-27 02:07:25,252] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,252] INFO [Broker id=3] Follower -uve-topic-25-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,252] INFO [Broker id=3] Follower -uve-topic-12-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,252] INFO [Broker id=3] Follower -uve-topic-19-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,252] INFO [Broker id=3] Follower -uve-topic-24-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,255] INFO [Broker id=3] Follower -uve-topic-11-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,255] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,255] INFO [Broker id=3] Follower -uve-topic-24-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,255] INFO [Broker id=3] Follower -uve-topic-11-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,259] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,259] 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-01-27 02:07:25,259] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,259] 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-01-27 02:07:25,259] 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-01-27 02:07:25,259] 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-01-27 02:07:25,259] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,259] INFO [Broker id=3] Follower -uve-topic-22-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,259] 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-01-27 02:07:25,259] 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-01-27 02:07:25,259] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,260] INFO [Broker id=3] Follower -uve-topic-11-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,260] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,260] 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-01-27 02:07:25,260] INFO [Broker id=3] Follower -uve-topic-25-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,260] 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-01-27 02:07:25,260] INFO [Broker id=3] Follower -uve-topic-12-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,260] INFO [Broker id=3] Follower -uve-topic-22-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,260] 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-01-27 02:07:25,260] 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-01-27 02:07:25,261] INFO [Broker id=3] Follower -uve-topic-21-0 starts at leader epoch 2 from offset 1809 with high watermark 1807. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,261] 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-01-27 02:07:25,261] 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-01-27 02:07:25,261] 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-01-27 02:07:25,261] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,261] INFO [Broker id=3] Follower -uve-topic-7-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,261] 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-01-27 02:07:25,261] 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-01-27 02:07:25,261] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-3-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] 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-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-5-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-6 starts at leader epoch 2 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-4-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-9-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] 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-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-19-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-13 starts at leader epoch 3 from offset 7 with high watermark 7. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-17-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] 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-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-1-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] INFO [Broker id=3] Follower -uve-topic-0-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,262] 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-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-5-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-7-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] 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-01-27 02:07:25,263] 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-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-10-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] 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-01-27 02:07:25,263] 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-01-27 02:07:25,263] 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-01-27 02:07:25,263] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-4-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-5-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] 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-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-25-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-12-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,263] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,263] 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-01-27 02:07:25,263] 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-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-1-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] INFO [Broker id=3] Follower -uve-topic-9-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,263] 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-01-27 02:07:25,263] 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-01-27 02:07:25,263] 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-01-27 02:07:25,264] INFO [Broker id=3] Follower -uve-topic-24-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,264] INFO [Broker id=3] Follower -uve-topic-11-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,264] 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-01-27 02:07:25,264] INFO [Broker id=3] Follower -uve-topic-3-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,265] INFO [Broker id=3] Follower -uve-topic-28-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,285] 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-01-27 02:07:25,291] 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-01-27 02:07:25,291] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,291] INFO [Broker id=3] Follower -uve-topic-27-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,291] 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-01-27 02:07:25,291] 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-01-27 02:07:25,291] 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-01-27 02:07:25,291] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,291] INFO [Broker id=3] Follower -uve-topic-11-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,291] 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-01-27 02:07:25,291] INFO [Broker id=3] Follower -uve-topic-24-0 starts at leader epoch 2 from offset 698 with high watermark 698. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,291] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,291] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,291] 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-01-27 02:07:25,291] INFO [Broker id=3] Follower -uve-topic-26-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,291] 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-01-27 02:07:25,291] INFO [Broker id=3] Follower -uve-topic-22-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,291] 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-01-27 02:07:25,291] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-5-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-11-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-29 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-22-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-19-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] 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-01-27 02:07:25,292] 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-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-10-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-10-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-19-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-26-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-9-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-0-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-1-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] 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-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-25-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,292] INFO [Broker id=3] Follower -uve-topic-12-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-4-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-0-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-7-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-27-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-7-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-24-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-11-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-3-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-4-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-1-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-1-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-19-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,293] 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-01-27 02:07:25,293] INFO [Broker id=3] Follower -uve-topic-12-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-24-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-11-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] 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-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-28-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] 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-01-27 02:07:25,294] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] 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-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-5-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-27-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-7-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-27-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-26-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-10-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-22-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] 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-01-27 02:07:25,294] 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-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-26-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-25-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-12-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-13-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] 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-01-27 02:07:25,294] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-7 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,294] INFO [Broker id=3] Follower -uve-topic-17-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-9-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-0-0 starts at leader epoch 2 from offset 3129 with high watermark 3127. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-10-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-19-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-15-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-26 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-13-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-26-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-12-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-25-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-11-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-4-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-0-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-1-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-7-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-14-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] INFO [Broker id=3] Follower -uve-topic-27-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,295] 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-01-27 02:07:25,295] 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-01-27 02:07:25,295] 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-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-5-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-9-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-1-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-21-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-22-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-3-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-19-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-10-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-23-0 starts at leader epoch 2 from offset 526 with high watermark 526. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-23 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-17-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-16-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-9-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] INFO [Broker id=3] Follower -uve-topic-10-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,296] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-5-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-27-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-7-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-17-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-4-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-13-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-12-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-26-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-17-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-1 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-17-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-10-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-12-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-11-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-19-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,297] 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-01-27 02:07:25,297] INFO [Broker id=3] Follower -uve-topic-15-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-20 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,297] 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-01-27 02:07:25,298] 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-01-27 02:07:25,298] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,298] 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-01-27 02:07:25,298] INFO [Broker id=3] Follower -uve-topic-26-0 starts at leader epoch 3 from offset 1294 with high watermark 1294. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,298] INFO [Broker id=3] Follower -uve-topic-27-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,298] 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-01-27 02:07:25,298] INFO [Broker id=3] Follower -uve-topic-1-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,298] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,298] INFO [Broker id=3] Follower -uve-topic-22-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,298] 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-01-27 02:07:25,298] 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-01-27 02:07:25,298] INFO [Broker id=3] Follower -uve-topic-9-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,298] INFO [Broker id=3] Follower -uve-topic-28-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,298] 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-01-27 02:07:25,298] 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-01-27 02:07:25,298] INFO [Broker id=3] Follower -uve-topic-16-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,298] 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-01-27 02:07:25,298] 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-01-27 02:07:25,311] INFO [Broker id=3] Follower -uve-topic-3-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,311] INFO [Broker id=3] Follower -uve-topic-9-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,311] 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-01-27 02:07:25,311] INFO [Broker id=3] Follower -uve-topic-1-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] 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-01-27 02:07:25,312] 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-01-27 02:07:25,312] 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-01-27 02:07:25,312] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-9-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] 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-01-27 02:07:25,312] 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-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-5-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-9-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] 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-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-1-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-3-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-19-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-4-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] 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-01-27 02:07:25,312] INFO [Broker id=3] Follower -uve-topic-20-0 starts at leader epoch 3 from offset 989 with high watermark 989. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] 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-01-27 02:07:25,312] 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-01-27 02:07:25,312] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,312] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-17 starts at leader epoch 3 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,312] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-0-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-17-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-29-0 starts at leader epoch 2 from offset 2261 with high watermark 2260. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-9-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-1-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-10-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-17-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-14-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-27-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-13-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-26-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-21-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] INFO [Broker id=3] Follower -uve-topic-22-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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 -1. (state.change.logger)
[2025-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,313] 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-01-27 02:07:25,314] 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-01-27 02:07:25,314] 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-01-27 02:07:25,314] INFO [Broker id=3] Follower -uve-topic-16-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,314] INFO [Broker id=3] Follower -uve-topic-7-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:07:25,341] 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-01-27 02:07:25,777] 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-01-27 02:07:27,197] INFO [Broker id=3] Add 62 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-01-27 02:07:28,831] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 4 from controller 1 for 15 partitions (state.change.logger)
[2025-01-27 02:07:28,872] INFO [Broker id=3] Stopped fetchers as part of LeaderAndIsr request correlationId 4 from controller 1 epoch 2 as part of the become-leader transition for 15 partitions (state.change.logger)
[2025-01-27 02:07:29,026] INFO [Broker id=3] Leader -uve-topic-21-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,056] INFO [Broker id=3] Leader -uve-topic-21-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,065] INFO [Broker id=3] Leader -uve-topic-11-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,073] INFO [Broker id=3] Leader -uve-topic-21-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,083] INFO [Broker id=3] Leader -uve-topic-21-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,088] INFO [Broker id=3] Leader -uve-topic-11-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,099] INFO [Broker id=3] Leader -uve-topic-21-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,107] INFO [Broker id=3] Leader -uve-topic-6-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,114] INFO [Broker id=3] Leader -uve-topic-1-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,118] INFO [Broker id=3] Leader -uve-topic-11-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,125] INFO [Broker id=3] Leader -uve-topic-1-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,133] INFO [Broker id=3] Leader -uve-topic-6-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,138] INFO [Broker id=3] Leader -uve-topic-11-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,142] INFO [Broker id=3] Leader -uve-topic-6-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,147] INFO [Broker id=3] Leader -uve-topic-11-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [1,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:07:29,161] INFO [Broker id=3] Add 15 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 5 (state.change.logger)
[2025-01-27 02:07:34,740] 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 7 (state.change.logger)
[2025-01-27 02:07:44,459] INFO [Broker id=3] Add 15 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 8 (state.change.logger)
[2025-01-27 02:07:52,322] INFO [Broker id=3] Add 945 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 9 (state.change.logger)
[2025-01-27 02:09:37,576] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 10 from controller 1 for 945 partitions (state.change.logger)
[2025-01-27 02:09:37,593] INFO [Broker id=3] Stopped fetchers as part of LeaderAndIsr request correlationId 10 from controller 1 epoch 2 as part of the become-leader transition for 465 partitions (state.change.logger)
[2025-01-27 02:09:37,593] INFO [Broker id=3] Leader -uve-topic-23-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,597] INFO [Broker id=3] Leader -uve-topic-16-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,600] INFO [Broker id=3] Leader -uve-topic-14-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,603] INFO [Broker id=3] Leader -uve-topic-27-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,608] INFO [Broker id=3] Leader -uve-topic-5-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,613] INFO [Broker id=3] Leader -uve-topic-29-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,616] INFO [Broker id=3] Leader -uve-topic-17-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,618] INFO [Broker id=3] Leader -uve-topic-24-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,625] INFO [Broker id=3] Leader -uve-topic-26-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,629] INFO [Broker id=3] Leader -uve-topic-17-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,633] INFO [Broker id=3] Leader -uve-topic-0-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,636] INFO [Broker id=3] Leader -uve-topic-6-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,640] INFO [Broker id=3] Leader -uve-topic-15-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,643] INFO [Broker id=3] Leader -uve-topic-28-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,646] INFO [Broker id=3] Leader -uve-topic-7-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,649] INFO [Broker id=3] Leader -uve-topic-22-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,653] INFO [Broker id=3] Leader -uve-topic-0-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,656] INFO [Broker id=3] Leader structured_syslog_topic-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,659] INFO [Broker id=3] Leader -uve-topic-8-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,662] INFO [Broker id=3] Leader -uve-topic-3-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,665] INFO [Broker id=3] Leader -uve-topic-10-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,668] INFO [Broker id=3] Leader -uve-topic-20-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,670] INFO [Broker id=3] Leader -uve-topic-8-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,673] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-14 starts at leader epoch 4 from offset 4 with high watermark 4 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,677] INFO [Broker id=3] Leader -uve-topic-14-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,681] INFO [Broker id=3] Leader -uve-topic-21-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,684] INFO [Broker id=3] Leader -uve-topic-20-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,687] INFO [Broker id=3] Leader -uve-topic-0-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,691] INFO [Broker id=3] Leader -uve-topic-13-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,695] INFO [Broker id=3] Leader -uve-topic-29-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,699] INFO [Broker id=3] Leader -uve-topic-23-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,703] INFO [Broker id=3] Leader -uve-topic-19-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,708] INFO [Broker id=3] Leader -uve-topic-25-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,711] INFO [Broker id=3] Leader -uve-topic-24-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,715] INFO [Broker id=3] Leader -uve-topic-28-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,718] INFO [Broker id=3] Leader -uve-topic-15-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,721] INFO [Broker id=3] Leader -uve-topic-20-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,725] INFO [Broker id=3] Leader -uve-topic-16-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,728] INFO [Broker id=3] Leader -uve-topic-8-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,732] INFO [Broker id=3] Leader -uve-topic-22-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,734] INFO [Broker id=3] Leader -uve-topic-24-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,737] INFO [Broker id=3] Leader -uve-topic-18-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,741] INFO [Broker id=3] Leader structured_syslog_topic-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,744] INFO [Broker id=3] Leader -uve-topic-28-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,747] INFO [Broker id=3] Leader -uve-topic-15-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,750] INFO [Broker id=3] Leader -uve-topic-20-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,753] INFO [Broker id=3] Leader -uve-topic-3-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,758] INFO [Broker id=3] Leader -uve-topic-8-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,761] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-11 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,768] INFO [Broker id=3] Leader -uve-topic-10-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,772] INFO [Broker id=3] Leader -uve-topic-20-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,776] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-8 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,780] INFO [Broker id=3] Leader -uve-topic-16-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,783] INFO [Broker id=3] Leader -uve-topic-0-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,787] INFO [Broker id=3] Leader -uve-topic-7-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,790] INFO [Broker id=3] Leader -uve-topic-8-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,794] INFO [Broker id=3] Leader -uve-topic-20-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,797] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-27 starts at leader epoch 3 from offset 2 with high watermark 2 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,802] INFO [Broker id=3] Leader -uve-topic-8-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,806] INFO [Broker id=3] Leader -uve-topic-18-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,811] INFO [Broker id=3] Leader -uve-topic-23-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,814] INFO [Broker id=3] Leader -uve-topic-14-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,818] INFO [Broker id=3] Leader -uve-topic-15-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,821] INFO [Broker id=3] Leader -uve-topic-28-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,825] INFO [Broker id=3] Leader -uve-topic-28-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,831] INFO [Broker id=3] Leader -uve-topic-27-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,833] INFO [Broker id=3] Leader -uve-topic-14-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,837] INFO [Broker id=3] Leader -uve-topic-22-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,840] INFO [Broker id=3] Leader -uve-topic-15-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,843] INFO [Broker id=3] Leader -uve-topic-29-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,846] INFO [Broker id=3] Leader -uve-topic-28-0 starts at leader epoch 4 from offset 1009 with high watermark 1009 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,851] INFO [Broker id=3] Leader -uve-topic-17-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,854] INFO [Broker id=3] Leader -uve-topic-20-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,857] INFO [Broker id=3] Leader structured_syslog_topic-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,860] INFO [Broker id=3] Leader -uve-topic-25-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,863] INFO [Broker id=3] Leader -uve-topic-12-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,867] INFO [Broker id=3] Leader -uve-topic-24-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,870] INFO [Broker id=3] Leader -uve-topic-26-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,873] INFO [Broker id=3] Leader -uve-topic-3-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,876] INFO [Broker id=3] Leader -uve-topic-19-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,879] INFO [Broker id=3] Leader -uve-topic-23-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,881] INFO [Broker id=3] Leader -uve-topic-25-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,884] INFO [Broker id=3] Leader -uve-topic-12-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,887] INFO [Broker id=3] Leader -uve-topic-24-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,891] INFO [Broker id=3] Leader -uve-topic-15-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,895] INFO [Broker id=3] Leader -uve-topic-28-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,898] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-5 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,902] INFO [Broker id=3] Leader -uve-topic-20-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,906] INFO [Broker id=3] Leader -uve-topic-22-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,910] INFO [Broker id=3] Leader -uve-topic-18-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,912] INFO [Broker id=3] Leader -uve-topic-21-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,915] INFO [Broker id=3] Leader -uve-topic-15-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,918] INFO [Broker id=3] Leader -uve-topic-28-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,921] INFO [Broker id=3] Leader -uve-topic-14-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,926] INFO [Broker id=3] Leader -uve-topic-7-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,930] INFO [Broker id=3] Leader -uve-topic-14-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,934] INFO [Broker id=3] Leader -uve-topic-2-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,937] INFO [Broker id=3] Leader -uve-topic-9-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,943] INFO [Broker id=3] Leader structured_syslog_topic-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,946] INFO [Broker id=3] Leader -uve-topic-0-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,949] INFO [Broker id=3] Leader structured_syslog_topic-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,952] INFO [Broker id=3] Leader -uve-topic-13-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,956] INFO [Broker id=3] Leader -uve-topic-20-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,961] INFO [Broker id=3] Leader -uve-topic-24-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,963] INFO [Broker id=3] Leader -uve-topic-29-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,968] INFO [Broker id=3] Leader -uve-topic-5-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,974] INFO [Broker id=3] Leader -uve-topic-18-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,977] INFO [Broker id=3] Leader -uve-topic-2-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,981] INFO [Broker id=3] Leader structured_syslog_topic-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,984] INFO [Broker id=3] Leader -uve-topic-14-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:37,988] INFO [Broker id=3] Leader -uve-topic-28-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,991] INFO [Broker id=3] Leader -uve-topic-15-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:37,995] INFO [Broker id=3] Leader -uve-topic-0-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,000] INFO [Broker id=3] Leader -uve-topic-22-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,002] INFO [Broker id=3] Leader -uve-topic-12-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,005] INFO [Broker id=3] Leader -uve-topic-25-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,008] INFO [Broker id=3] Leader -uve-topic-26-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,011] INFO [Broker id=3] Leader -uve-topic-7-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,013] INFO [Broker id=3] Leader -uve-topic-10-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,016] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-21 starts at leader epoch 3 from offset 1 with high watermark 1 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,020] INFO [Broker id=3] Leader structured_syslog_topic-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,025] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-2 starts at leader epoch 4 from offset 8 with high watermark 8 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,031] INFO [Broker id=3] Leader -uve-topic-23-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,034] INFO [Broker id=3] Leader -uve-topic-9-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,037] INFO [Broker id=3] Leader -uve-topic-14-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,043] INFO [Broker id=3] Leader -uve-topic-27-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,049] INFO [Broker id=3] Leader -uve-topic-29-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,053] INFO [Broker id=3] Leader -uve-topic-0-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,060] INFO [Broker id=3] Leader -uve-topic-4-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,063] INFO [Broker id=3] Leader -uve-topic-8-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,070] INFO [Broker id=3] Leader -uve-topic-14-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,075] INFO [Broker id=3] Leader -uve-topic-29-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,079] INFO [Broker id=3] Leader -uve-topic-23-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,084] INFO [Broker id=3] Leader -uve-topic-12-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,090] INFO [Broker id=3] Leader -uve-topic-25-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,094] INFO [Broker id=3] Leader -uve-topic-27-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,100] INFO [Broker id=3] Leader -uve-topic-13-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,104] INFO [Broker id=3] Leader -uve-topic-26-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,107] INFO [Broker id=3] Leader -uve-topic-18-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,110] INFO [Broker id=3] Leader -uve-topic-2-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,113] INFO [Broker id=3] Leader structured_syslog_topic-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,116] INFO [Broker id=3] Leader -uve-topic-6-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,119] INFO [Broker id=3] Leader -uve-topic-13-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,121] INFO [Broker id=3] Leader -uve-topic-5-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,124] INFO [Broker id=3] Leader -uve-topic-20-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,126] INFO [Broker id=3] Leader -uve-topic-24-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,129] INFO [Broker id=3] Leader -uve-topic-4-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,132] INFO [Broker id=3] Leader -uve-topic-3-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,136] INFO [Broker id=3] Leader -uve-topic-5-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,139] INFO [Broker id=3] Leader -uve-topic-7-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,142] INFO [Broker id=3] Leader -uve-topic-22-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,145] INFO [Broker id=3] Leader -uve-topic-14-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,148] INFO [Broker id=3] Leader -uve-topic-21-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,151] INFO [Broker id=3] Leader -uve-topic-28-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,154] INFO [Broker id=3] Leader -uve-topic-15-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,156] INFO [Broker id=3] Leader -uve-topic-9-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,159] INFO [Broker id=3] Leader -uve-topic-1-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,163] INFO [Broker id=3] Leader -uve-topic-0-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,166] INFO [Broker id=3] Leader structured_syslog_topic-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,169] INFO [Broker id=3] Leader structured_syslog_topic-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,172] INFO [Broker id=3] Leader -uve-topic-7-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,176] INFO [Broker id=3] Leader -uve-topic-0-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,179] INFO [Broker id=3] Leader -uve-topic-12-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,183] INFO [Broker id=3] Leader -uve-topic-25-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,186] INFO [Broker id=3] Leader -uve-topic-11-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,189] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-15 starts at leader epoch 3 from offset 3 with high watermark 3 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,193] INFO [Broker id=3] Leader -uve-topic-6-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,196] INFO [Broker id=3] Leader -uve-topic-13-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,200] INFO [Broker id=3] Leader -uve-topic-26-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,203] INFO [Broker id=3] Leader -uve-topic-18-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,206] INFO [Broker id=3] Leader -uve-topic-23-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,210] INFO [Broker id=3] Leader -uve-topic-29-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,215] INFO [Broker id=3] Leader -uve-topic-4-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,220] INFO [Broker id=3] Leader -uve-topic-27-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,223] INFO [Broker id=3] Leader -uve-topic-16-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,226] INFO [Broker id=3] Leader -uve-topic-2-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,229] INFO [Broker id=3] Leader -uve-topic-5-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,232] INFO [Broker id=3] Leader -uve-topic-9-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,235] INFO [Broker id=3] Leader -uve-topic-1-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,239] INFO [Broker id=3] Leader -uve-topic-5-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,242] INFO [Broker id=3] Leader -uve-topic-22-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,246] INFO [Broker id=3] Leader -uve-topic-29-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,249] INFO [Broker id=3] Leader -uve-topic-16-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,251] INFO [Broker id=3] Leader -uve-topic-28-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,254] INFO [Broker id=3] Leader -uve-topic-15-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,257] INFO [Broker id=3] Leader -uve-topic-5-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,259] INFO [Broker id=3] Leader -uve-topic-11-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,262] INFO [Broker id=3] Leader -uve-topic-24-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,265] INFO [Broker id=3] Leader -uve-topic-4-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,267] INFO [Broker id=3] Leader -uve-topic-5-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,270] INFO [Broker id=3] Leader -uve-topic-7-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,273] INFO [Broker id=3] Leader -uve-topic-1-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,276] INFO [Broker id=3] Leader -uve-topic-4-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,278] INFO [Broker id=3] Leader -uve-topic-25-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,281] INFO [Broker id=3] Leader -uve-topic-26-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,284] INFO [Broker id=3] Leader -uve-topic-12-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,287] INFO [Broker id=3] Leader -uve-topic-13-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,290] INFO [Broker id=3] Leader -uve-topic-4-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,292] INFO [Broker id=3] Leader -uve-topic-17-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,295] INFO [Broker id=3] Leader -uve-topic-29-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,297] INFO [Broker id=3] Leader -uve-topic-2-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,300] INFO [Broker id=3] Leader -uve-topic-22-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,304] INFO [Broker id=3] Leader -uve-topic-9-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,307] INFO [Broker id=3] Leader -uve-topic-21-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,311] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-3 starts at leader epoch 3 from offset 4 with high watermark 4 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,316] INFO [Broker id=3] Leader -uve-topic-20-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,320] INFO [Broker id=3] Leader -uve-topic-14-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,323] INFO [Broker id=3] Leader -uve-topic-25-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,326] INFO [Broker id=3] Leader -uve-topic-19-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,328] INFO [Broker id=3] Leader -uve-topic-23-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,331] INFO [Broker id=3] Leader -uve-topic-25-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,337] INFO [Broker id=3] Leader -uve-topic-12-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,340] INFO [Broker id=3] Leader -uve-topic-27-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,343] INFO [Broker id=3] Leader -uve-topic-6-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,346] INFO [Broker id=3] Leader -uve-topic-22-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,349] INFO [Broker id=3] Leader -uve-topic-10-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,351] INFO [Broker id=3] Leader -uve-topic-18-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,355] INFO [Broker id=3] Leader -uve-topic-18-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,358] INFO [Broker id=3] Leader -uve-topic-22-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,360] INFO [Broker id=3] Leader -uve-topic-17-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,364] INFO [Broker id=3] Leader -uve-topic-29-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,367] INFO [Broker id=3] Leader structured_syslog_topic-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,370] INFO [Broker id=3] Leader -uve-topic-27-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,373] INFO [Broker id=3] Leader -uve-topic-16-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,375] INFO [Broker id=3] Leader -uve-topic-11-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,379] INFO [Broker id=3] Leader -uve-topic-26-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,383] INFO [Broker id=3] Leader -uve-topic-13-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,387] INFO [Broker id=3] Leader -uve-topic-12-0 starts at leader epoch 4 from offset 168 with high watermark 168 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,391] INFO [Broker id=3] Leader -uve-topic-5-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,395] INFO [Broker id=3] Leader -uve-topic-6-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,398] INFO [Broker id=3] Leader -uve-topic-9-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,402] INFO [Broker id=3] Leader -uve-topic-1-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,410] INFO [Broker id=3] Leader -uve-topic-0-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,413] INFO [Broker id=3] Leader -uve-topic-7-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,416] INFO [Broker id=3] Leader -uve-topic-4-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,420] INFO [Broker id=3] Leader -uve-topic-25-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,425] INFO [Broker id=3] Leader -uve-topic-12-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,428] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 3 from offset 7 with high watermark 7 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,432] INFO [Broker id=3] Leader -uve-topic-7-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,435] INFO [Broker id=3] Leader -uve-topic-6-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,437] INFO [Broker id=3] Leader -uve-topic-23-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,440] INFO [Broker id=3] Leader -uve-topic-10-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,443] INFO [Broker id=3] Leader -uve-topic-2-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,445] INFO [Broker id=3] Leader -uve-topic-18-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,448] INFO [Broker id=3] Leader -uve-topic-19-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,451] INFO [Broker id=3] Leader -uve-topic-23-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,453] INFO [Broker id=3] Leader -uve-topic-25-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,456] INFO [Broker id=3] Leader -uve-topic-12-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,459] INFO [Broker id=3] Leader -uve-topic-5-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,461] INFO [Broker id=3] Leader -uve-topic-4-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,464] INFO [Broker id=3] Leader -uve-topic-17-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,467] INFO [Broker id=3] Leader -uve-topic-2-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,470] INFO [Broker id=3] Leader -uve-topic-9-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,473] INFO [Broker id=3] Leader -uve-topic-25-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,475] INFO [Broker id=3] Leader -uve-topic-12-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,477] INFO [Broker id=3] Leader -uve-topic-4-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,480] INFO [Broker id=3] Leader -uve-topic-3-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,482] INFO [Broker id=3] Leader -uve-topic-15-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,485] INFO [Broker id=3] Leader -uve-topic-6-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,487] INFO [Broker id=3] Leader -uve-topic-25-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,490] INFO [Broker id=3] Leader -uve-topic-12-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,492] INFO [Broker id=3] Leader -uve-topic-19-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,495] INFO [Broker id=3] Leader -uve-topic-24-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,497] INFO [Broker id=3] Leader -uve-topic-11-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,500] INFO [Broker id=3] Leader -uve-topic-4-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,502] INFO [Broker id=3] Leader -uve-topic-11-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,506] INFO [Broker id=3] Leader -uve-topic-5-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,509] INFO [Broker id=3] Leader -uve-topic-27-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,513] INFO [Broker id=3] Leader -uve-topic-22-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,516] INFO [Broker id=3] Leader -uve-topic-10-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,518] INFO [Broker id=3] Leader -uve-topic-18-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,521] INFO [Broker id=3] Leader -uve-topic-26-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,523] INFO [Broker id=3] Leader -uve-topic-13-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,526] INFO [Broker id=3] Leader -uve-topic-22-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,528] INFO [Broker id=3] Leader -uve-topic-16-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,531] INFO [Broker id=3] Leader -uve-topic-29-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,534] INFO [Broker id=3] Leader -uve-topic-21-0 starts at leader epoch 3 from offset 1883 with high watermark 1883 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,537] INFO [Broker id=3] Leader -uve-topic-8-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,541] INFO [Broker id=3] Leader -uve-topic-7-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,544] INFO [Broker id=3] Leader -uve-topic-23-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,548] INFO [Broker id=3] Leader -uve-topic-1-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,551] INFO [Broker id=3] Leader -uve-topic-4-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,553] INFO [Broker id=3] Leader -uve-topic-9-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,556] INFO [Broker id=3] Leader -uve-topic-9-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,681] INFO [Broker id=3] Leader -uve-topic-19-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,910] INFO [Broker id=3] Leader -uve-topic-17-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,922] INFO [Broker id=3] Leader -uve-topic-1-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,926] INFO [Broker id=3] Leader -uve-topic-0-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,929] INFO [Broker id=3] Leader -uve-topic-24-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,932] INFO [Broker id=3] Leader -uve-topic-5-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,935] INFO [Broker id=3] Leader -uve-topic-7-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,937] INFO [Broker id=3] Leader -uve-topic-6-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,940] INFO [Broker id=3] Leader -uve-topic-23-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,944] INFO [Broker id=3] Leader -uve-topic-10-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,947] INFO [Broker id=3] Leader -uve-topic-3-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,950] INFO [Broker id=3] Leader -uve-topic-2-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,953] INFO [Broker id=3] Leader -uve-topic-18-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,956] INFO [Broker id=3] Leader -uve-topic-19-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,959] INFO [Broker id=3] Leader -uve-topic-5-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,962] INFO [Broker id=3] Leader -uve-topic-6-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,965] INFO [Broker id=3] Leader -uve-topic-25-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,968] INFO [Broker id=3] Leader -uve-topic-12-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,971] INFO [Broker id=3] Leader -uve-topic-4-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,973] INFO [Broker id=3] Leader -uve-topic-2-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,976] INFO [Broker id=3] Leader -uve-topic-18-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,979] INFO [Broker id=3] Leader -uve-topic-1-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,982] INFO [Broker id=3] Leader -uve-topic-3-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,984] INFO [Broker id=3] Leader -uve-topic-11-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:38,987] INFO [Broker id=3] Leader -uve-topic-8-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,990] INFO [Broker id=3] Leader -uve-topic-7-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,993] INFO [Broker id=3] Leader -uve-topic-27-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,996] INFO [Broker id=3] Leader -uve-topic-16-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:38,999] INFO [Broker id=3] Leader -uve-topic-11-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,002] INFO [Broker id=3] Leader -uve-topic-26-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,004] INFO [Broker id=3] Leader -uve-topic-13-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,008] INFO [Broker id=3] Leader -uve-topic-26-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,011] INFO [Broker id=3] Leader -uve-topic-13-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,014] INFO [Broker id=3] Leader -uve-topic-17-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,016] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-29 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,019] INFO [Broker id=3] Leader -uve-topic-22-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,023] INFO [Broker id=3] Leader -uve-topic-9-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,026] INFO [Broker id=3] Leader -uve-topic-19-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,028] INFO [Broker id=3] Leader -uve-topic-24-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,031] INFO [Broker id=3] Leader -uve-topic-23-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,033] INFO [Broker id=3] Leader -uve-topic-10-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,036] INFO [Broker id=3] Leader -uve-topic-3-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,040] INFO [Broker id=3] Leader -uve-topic-19-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,043] INFO [Broker id=3] Leader -uve-topic-6-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,051] INFO [Broker id=3] Leader -uve-topic-19-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,075] INFO [Broker id=3] Leader -uve-topic-3-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,080] INFO [Broker id=3] Leader -uve-topic-1-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,083] INFO [Broker id=3] Leader -uve-topic-9-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,087] INFO [Broker id=3] Leader -uve-topic-2-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,104] INFO [Broker id=3] Leader -uve-topic-4-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,110] INFO [Broker id=3] Leader -uve-topic-8-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,118] INFO [Broker id=3] Leader -uve-topic-16-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,123] INFO [Broker id=3] Leader -uve-topic-29-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,127] INFO [Broker id=3] Leader -uve-topic-2-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,131] INFO [Broker id=3] Leader -uve-topic-7-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,134] INFO [Broker id=3] Leader -uve-topic-27-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,139] INFO [Broker id=3] Leader -uve-topic-11-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,142] INFO [Broker id=3] Leader -uve-topic-10-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,145] INFO [Broker id=3] Leader -uve-topic-1-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,149] INFO [Broker id=3] Leader -uve-topic-6-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,153] INFO [Broker id=3] Leader -uve-topic-9-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,157] INFO [Broker id=3] Leader -uve-topic-16-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,159] INFO [Broker id=3] Leader -uve-topic-2-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,162] INFO [Broker id=3] Leader -uve-topic-1-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,168] INFO [Broker id=3] Leader -uve-topic-18-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,173] INFO [Broker id=3] Leader -uve-topic-3-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,176] INFO [Broker id=3] Leader -uve-topic-19-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,184] INFO [Broker id=3] Leader -uve-topic-11-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,187] INFO [Broker id=3] Leader -uve-topic-8-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,191] INFO [Broker id=3] Leader -uve-topic-21-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,194] INFO [Broker id=3] Leader -uve-topic-5-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,197] INFO [Broker id=3] Leader -uve-topic-27-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,200] INFO [Broker id=3] Leader -uve-topic-7-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,203] INFO [Broker id=3] Leader -uve-topic-20-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,206] INFO [Broker id=3] Leader -uve-topic-27-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,209] INFO [Broker id=3] Leader -uve-topic-26-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,211] INFO [Broker id=3] Leader -uve-topic-13-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,214] INFO [Broker id=3] Leader -uve-topic-14-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,218] INFO [Broker id=3] Leader -uve-topic-23-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,223] INFO [Broker id=3] Leader -uve-topic-10-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,226] INFO [Broker id=3] Leader -uve-topic-19-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,229] INFO [Broker id=3] Leader structured_syslog_topic-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,232] INFO [Broker id=3] Leader -uve-topic-24-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,236] INFO [Broker id=3] Leader -uve-topic-26-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,239] INFO [Broker id=3] Leader -uve-topic-25-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,245] INFO [Broker id=3] Leader -uve-topic-12-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,248] INFO [Broker id=3] Leader -uve-topic-17-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,251] INFO [Broker id=3] Leader -uve-topic-0-0 starts at leader epoch 3 from offset 3417 with high watermark 3417 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,254] INFO [Broker id=3] Leader -uve-topic-10-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,257] INFO [Broker id=3] Leader -uve-topic-10-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,259] INFO [Broker id=3] Leader -uve-topic-15-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,262] INFO [Broker id=3] Leader -uve-topic-28-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,264] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-26 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,268] INFO [Broker id=3] Leader -uve-topic-2-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,274] INFO [Broker id=3] Leader -uve-topic-13-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,278] INFO [Broker id=3] Leader -uve-topic-27-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,280] INFO [Broker id=3] Leader -uve-topic-10-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,283] INFO [Broker id=3] Leader -uve-topic-4-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,287] INFO [Broker id=3] Leader -uve-topic-8-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,289] INFO [Broker id=3] Leader -uve-topic-1-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,292] INFO [Broker id=3] Leader -uve-topic-14-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,294] INFO [Broker id=3] Leader -uve-topic-9-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,297] INFO [Broker id=3] Leader -uve-topic-13-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,299] INFO [Broker id=3] Leader -uve-topic-26-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,302] INFO [Broker id=3] Leader -uve-topic-17-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,304] INFO [Broker id=3] Leader -uve-topic-21-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,307] INFO [Broker id=3] Leader -uve-topic-22-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,309] INFO [Broker id=3] Leader -uve-topic-19-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,312] INFO [Broker id=3] Leader -uve-topic-3-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,314] INFO [Broker id=3] Leader -uve-topic-10-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,318] INFO [Broker id=3] Leader -uve-topic-23-0 starts at leader epoch 3 from offset 549 with high watermark 549 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,320] INFO [Broker id=3] Leader -uve-topic-24-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,323] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-23 starts at leader epoch 4 from offset 4 with high watermark 4 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,329] INFO [Broker id=3] Leader -uve-topic-19-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,332] INFO [Broker id=3] Leader -uve-topic-28-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,334] INFO [Broker id=3] Leader -uve-topic-3-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,337] INFO [Broker id=3] Leader -uve-topic-15-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,339] INFO [Broker id=3] Leader -uve-topic-17-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,342] INFO [Broker id=3] Leader -uve-topic-20-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,345] INFO [Broker id=3] Leader -uve-topic-29-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,348] INFO [Broker id=3] Leader -uve-topic-16-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,351] INFO [Broker id=3] Leader -uve-topic-16-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,354] INFO [Broker id=3] Leader -uve-topic-18-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,358] INFO [Broker id=3] Leader structured_syslog_topic-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,360] INFO [Broker id=3] Leader -uve-topic-2-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,363] INFO [Broker id=3] Leader -uve-topic-27-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,366] INFO [Broker id=3] Leader -uve-topic-5-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,369] INFO [Broker id=3] Leader -uve-topic-7-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,371] INFO [Broker id=3] Leader -uve-topic-20-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,374] INFO [Broker id=3] Leader -uve-topic-0-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,377] INFO [Broker id=3] Leader -uve-topic-17-16 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,380] INFO [Broker id=3] Leader structured_syslog_topic-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,384] INFO [Broker id=3] Leader -uve-topic-24-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,386] INFO [Broker id=3] Leader -uve-topic-12-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,389] INFO [Broker id=3] Leader -uve-topic-26-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,392] INFO [Broker id=3] Leader -uve-topic-16-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,395] INFO [Broker id=3] Leader -uve-topic-18-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,398] INFO [Broker id=3] Leader -uve-topic-17-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,402] INFO [Broker id=3] Leader -uve-topic-10-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,405] INFO [Broker id=3] Leader -uve-topic-11-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,407] INFO [Broker id=3] Leader -uve-topic-21-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,410] INFO [Broker id=3] Leader -uve-topic-28-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,413] INFO [Broker id=3] Leader -uve-topic-15-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,416] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-20 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,419] INFO [Broker id=3] Leader -uve-topic-14-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,423] INFO [Broker id=3] Leader -uve-topic-13-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,426] INFO [Broker id=3] Leader -uve-topic-26-0 starts at leader epoch 4 from offset 1592 with high watermark 1592 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,429] INFO [Broker id=3] Leader -uve-topic-27-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,432] INFO [Broker id=3] Leader -uve-topic-6-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,435] INFO [Broker id=3] Leader -uve-topic-1-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,438] INFO [Broker id=3] Leader -uve-topic-3-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,441] INFO [Broker id=3] Leader -uve-topic-8-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,445] INFO [Broker id=3] Leader -uve-topic-9-4 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,448] INFO [Broker id=3] Leader -uve-topic-9-10 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,451] INFO [Broker id=3] Leader -uve-topic-17-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,454] INFO [Broker id=3] Leader -uve-topic-3-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,457] INFO [Broker id=3] Leader -uve-topic-19-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,460] INFO [Broker id=3] Leader -uve-topic-4-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,462] INFO [Broker id=3] Leader -uve-topic-28-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,465] INFO [Broker id=3] Leader -uve-topic-3-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,467] INFO [Broker id=3] Leader -uve-topic-15-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,470] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-17 starts at leader epoch 4 from offset 1 with high watermark 1 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,474] INFO [Broker id=3] Leader -uve-topic-20-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,477] INFO [Broker id=3] Leader -uve-topic-29-0 starts at leader epoch 3 from offset 2349 with high watermark 2349 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,482] INFO [Broker id=3] Leader -uve-topic-16-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,485] INFO [Broker id=3] Leader -uve-topic-8-28 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,487] INFO [Broker id=3] Leader -uve-topic-17-22 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,490] INFO [Broker id=3] Leader -uve-topic-1-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,492] INFO [Broker id=3] Leader -uve-topic-2-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,495] INFO [Broker id=3] Leader structured_syslog_topic-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,497] INFO [Broker id=3] Leader -uve-topic-14-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,499] INFO [Broker id=3] Leader -uve-topic-13-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,502] INFO [Broker id=3] Leader -uve-topic-0-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,504] INFO [Broker id=3] Leader -uve-topic-21-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,507] INFO [Broker id=3] Leader -uve-topic-0-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,510] INFO [Broker id=3] Leader -uve-topic-21-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,513] INFO [Broker id=3] Leader -uve-topic-22-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,520] INFO [Broker id=3] Leader -uve-topic-8-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,523] INFO [Broker id=3] Leader -uve-topic-29-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,526] INFO [Broker id=3] Leader -uve-topic-24-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,529] INFO [Broker id=3] Leader -uve-topic-16-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [3,2] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-22-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-17-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] 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-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-16-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-11-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-0-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-20-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-1-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-2-0 starts at leader epoch 3 from offset 591 with high watermark 591. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-7-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-9-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-5-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-4-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-12-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-25-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-9-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] 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-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] 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 2. (state.change.logger)
[2025-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-7-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,532] 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-01-27 02:09:39,532] 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-01-27 02:09:39,532] INFO [Broker id=3] Follower -uve-topic-17-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] 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-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-4-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-12-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-26-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-25-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] 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-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-16-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-10-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-19-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-11-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] 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-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-22-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-1-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-5-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-7-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-0-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] 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-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] 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 2. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-7-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-17-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] 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-01-27 02:09:39,533] INFO [Broker id=3] Follower structured_syslog_topic-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-9-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] 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-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-26-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-13-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-5-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-19-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,533] INFO [Broker id=3] Follower -uve-topic-4-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-25-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-12-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-1-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-22-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-10-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] 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-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-27-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-16-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-11-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-20-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-7-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-10-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-11-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-24 starts at leader epoch 3 from offset 5 with high watermark 5. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-9-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-19-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-22-0 starts at leader epoch 4 from offset 3011 with high watermark 3011. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-27-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-5-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-17-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-13-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-12-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-26-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-25-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-27-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-7-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-1-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-4-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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 2. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,534] INFO [Broker id=3] Follower -uve-topic-7-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,534] 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-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-16-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-11-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-3-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-4-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-1-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-27-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] 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-01-27 02:09:39,535] INFO [Broker id=3] Follower structured_syslog_topic-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-20-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-9-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-13-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-12-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-25-0 starts at leader epoch 4 from offset 431 with high watermark 431. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-26-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-5-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-7-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-19-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-19-0 starts at leader epoch 3 from offset 162 with high watermark 162. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-27-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-17-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-10-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-16-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-28-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-27-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-16-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-10-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-18 starts at leader epoch 3 from offset 8 with high watermark 8. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-9-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-1-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-5-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-27-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-7-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] INFO [Broker id=3] Follower structured_syslog_topic-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-13-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-26-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-3-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-19-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] 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-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-17-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-4-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-13-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-26-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-28-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-15-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,535] 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-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] 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 2. (state.change.logger)
[2025-01-27 02:09:39,535] INFO [Broker id=3] Follower -uve-topic-19-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-3-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-4-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-27-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-10-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-20-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-21-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-25 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-16-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-14-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-29-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-1-0 starts at leader epoch 4 from offset 627 with high watermark 627. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-26-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-13-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-17-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower structured_syslog_topic-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-26-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-13-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-5-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-4-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower structured_syslog_topic-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-18-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-3-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-19-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-12 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-16-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-17-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-26-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-13-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-15-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-28-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-21-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 4 from offset 4 with high watermark 4. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-27-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-24-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-10-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-26-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-13-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-14-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-23-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-5-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-17-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-20-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-21-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-19 starts at leader epoch 4 from offset 1 with high watermark 1. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-16-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,536] 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 2. (state.change.logger)
[2025-01-27 02:09:39,536] 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-01-27 02:09:39,536] INFO [Broker id=3] Follower -uve-topic-14-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-29-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-0 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-13-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-15-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-28-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-3-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-19-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-27-0 starts at leader epoch 4 from offset 1394 with high watermark 1394. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-24-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-10-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-28 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-16-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-3-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-0-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-21-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 4 from offset 4 with high watermark 4. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-24-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-14-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-18-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-19-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-23-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-24-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-17-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-15-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-28-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-10-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-3-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-6 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-13 starts at leader epoch 4 from offset 7 with high watermark 7. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-0-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-21-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-24-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-15-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-3-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-28-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-14-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-29-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-24-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,537] 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 2. (state.change.logger)
[2025-01-27 02:09:39,537] INFO [Broker id=3] Follower -uve-topic-19-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-24-0 starts at leader epoch 3 from offset 738 with high watermark 738. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-3-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-10-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-25-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-12-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-24-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-11-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-15-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-28-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-21-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 4 from offset 4 with high watermark 4. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-0-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-14-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-24-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-18-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-3-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-23-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-0-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-29-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-25-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-12-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-24-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-15-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-28-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-14-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-11-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-21-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-7 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-18-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-23-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] 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 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-14-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-23-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-12-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,538] INFO [Broker id=3] Follower -uve-topic-25-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-24-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-0-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-18-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-22-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-11-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-21-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 4 from offset 1 with high watermark 1. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-28-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-15-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-9-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-1-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-22-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-14-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-9-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-1-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-5-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-11-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-29-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-21-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-22-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-1 starts at leader epoch 4 from offset 1 with high watermark 1. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-12-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-25-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-22-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-0-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-4-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-28-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-15-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-22-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-1-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-0-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-4-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-22-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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 2. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-5-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-20-0 starts at leader epoch 4 from offset 1081 with high watermark 1081. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-0-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] INFO [Broker id=3] Follower -uve-topic-21-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,539] 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-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-9-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,540] 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 2. (state.change.logger)
[2025-01-27 02:09:39,540] 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 2. (state.change.logger)
[2025-01-27 02:09:39,540] 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-01-27 02:09:39,540] 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 2. (state.change.logger)
[2025-01-27 02:09:39,540] 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-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-7-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,540] 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 2. (state.change.logger)
[2025-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-14-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,540] 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-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-12-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-25-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-9-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-11-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,540] 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-01-27 02:09:39,540] 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 2. (state.change.logger)
[2025-01-27 02:09:39,540] 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-01-27 02:09:39,540] INFO [Broker id=3] Follower -uve-topic-15-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,551] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 1 epoch 2 with correlation id 10 for 480 partitions (state.change.logger)
[2025-01-27 02:09:39,576] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 2 for 960 partitions (state.change.logger)
[2025-01-27 02:09:39,578] 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-01-27 02:09:39,578] 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-01-27 02:09:39,583] 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-01-27 02:09:39,588] INFO [Broker id=3] Skipped 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-01-27 02:09:39,588] 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-01-27 02:09:39,591] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,593] INFO [Broker id=3] Skipped 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-01-27 02:09:39,593] 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-01-27 02:09:39,596] 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-01-27 02:09:39,599] 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-01-27 02:09:39,602] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:39,604] INFO [Broker id=3] Skipped 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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,604] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:39,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-14-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,607] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:39,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-5-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,609] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,611] 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-01-27 02:09:39,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-29-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,614] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:39,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-17-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,616] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:39,619] 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-01-27 02:09:39,621] 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-01-27 02:09:39,623] INFO [Broker id=3] Skipped 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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,623] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:39,626] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:39,628] INFO [Broker id=3] Skipped 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-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,628] 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-01-27 02:09:39,631] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:39,633] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:39,637] INFO [Broker id=3] Skipped 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-01-27 02:09:39,637] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:39,639] 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-01-27 02:09:39,642] INFO [Broker id=3] Skipped 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-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,642] 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-01-27 02:09:39,644] 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-01-27 02:09:39,647] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:39,650] INFO [Broker id=3] Leader -uve-topic-2-0 starts at leader epoch 4 from offset 591 with high watermark 591 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:39,652] 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-01-27 02:09:39,655] 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-01-27 02:09:39,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-6-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,657] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:39,660] INFO [Broker id=3] Skipped 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-01-27 02:09:39,660] 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-01-27 02:09:39,663] INFO [Broker id=3] Skipped 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-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,664] 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-01-27 02:09:39,668] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:39,671] INFO [Broker id=3] Skipped 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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,671] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:39,673] INFO [Broker id=3] Skipped 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-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,673] 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-01-27 02:09:39,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-0-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,676] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:39,678] INFO [Broker id=3] Leader -uve-topic-21-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:39,681] INFO [Broker id=3] Skipped 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-01-27 02:09:39,681] 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-01-27 02:09:39,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 structured_syslog_topic-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,683] 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-01-27 02:09:39,686] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:39,688] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:39,690] 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-01-27 02:09:39,693] INFO [Broker id=3] Skipped 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-01-27 02:09:39,693] 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-01-27 02:09:39,695] INFO [Broker id=3] Skipped 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-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,695] 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-01-27 02:09:39,698] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:39,700] INFO [Broker id=3] Skipped 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-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,700] 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-01-27 02:09:39,703] 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-01-27 02:09:39,705] 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-01-27 02:09:39,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-20-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,707] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:39,710] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:39,712] 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-01-27 02:09:39,715] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,717] 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-01-27 02:09:39,720] INFO [Broker id=3] Skipped 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-01-27 02:09:39,720] INFO [Broker id=3] Leader -uve-topic-21-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:39,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-21-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,722] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-14 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:39,725] INFO [Broker id=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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,725] 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-01-27 02:09:39,727] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:39,730] 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-01-27 02:09:39,733] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:39,735] 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-01-27 02:09:39,738] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:39,741] INFO [Broker id=3] Skipped 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-01-27 02:09:39,741] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:39,744] 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-01-27 02:09:39,746] 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-01-27 02:09:39,749] 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-01-27 02:09:39,752] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:39,755] INFO [Broker id=3] Skipped 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-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,755] 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-01-27 02:09:39,759] INFO [Broker id=3] Skipped 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-01-27 02:09:39,759] 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-01-27 02:09:39,761] INFO [Broker id=3] Skipped 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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,761] 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-01-27 02:09:39,764] 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-01-27 02:09:39,767] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,769] 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-01-27 02:09:39,772] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:39,775] INFO [Broker id=3] Skipped 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-01-27 02:09:39,775] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:39,777] 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-01-27 02:09:39,780] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:39,782] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:39,785] 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-01-27 02:09:39,788] 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-01-27 02:09:39,790] 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-01-27 02:09:39,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-29-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,793] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,796] 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-01-27 02:09:39,800] 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-01-27 02:09:39,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-23-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,804] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:39,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-19-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,807] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:39,810] INFO [Broker id=3] Skipped 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-01-27 02:09:39,810] 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-01-27 02:09:39,813] 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-01-27 02:09:39,815] INFO [Broker id=3] Skipped 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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,815] 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-01-27 02:09:39,818] 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-01-27 02:09:39,820] INFO [Broker id=3] Skipped 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-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,820] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:39,823] INFO [Broker id=3] Skipped 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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,823] 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-01-27 02:09:39,827] INFO [Broker id=3] Skipped 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-01-27 02:09:39,827] 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-01-27 02:09:39,830] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,833] INFO [Broker id=3] Skipped 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-01-27 02:09:39,833] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:39,836] 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-01-27 02:09:39,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 -uve-topic-8-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,839] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:39,842] INFO [Broker id=3] Skipped 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-01-27 02:09:39,842] 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-01-27 02:09:39,846] INFO [Broker id=3] Skipped 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-01-27 02:09:39,846] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:39,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-24-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,848] INFO [Broker id=3] Leader -uve-topic-11-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:39,851] INFO [Broker id=3] Skipped 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-01-27 02:09:39,851] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:39,854] 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-01-27 02:09:39,856] 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-01-27 02:09:39,859] 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-01-27 02:09:39,861] INFO [Broker id=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-01-27 02:09:39,861] 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-01-27 02:09:39,864] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:39,867] INFO [Broker id=3] Skipped 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-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,867] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:39,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-28-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,870] 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-01-27 02:09:39,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-20-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,874] INFO [Broker id=3] Leader -uve-topic-21-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:39,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-21-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,877] 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-01-27 02:09:39,881] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:39,883] INFO [Broker id=3] Skipped 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-01-27 02:09:39,883] 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-01-27 02:09:39,886] INFO [Broker id=3] Skipped 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-01-27 02:09:39,886] INFO [Broker id=3] Leader -uve-topic-21-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:39,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-21-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,889] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-11 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-01-27 02:09:39,891] INFO [Broker id=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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,891] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:39,894] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:39,897] 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-01-27 02:09:39,900] INFO [Broker id=3] Leader -uve-topic-11-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:39,902] INFO [Broker id=3] Skipped 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-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,902] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:39,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-10-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,905] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:39,908] 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-01-27 02:09:39,912] INFO [Broker id=3] Skipped 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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,912] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:39,915] 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-01-27 02:09:39,917] INFO [Broker id=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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,917] 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-01-27 02:09:39,920] 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-01-27 02:09:39,923] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,926] INFO [Broker id=3] Skipped 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-01-27 02:09:39,926] 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-01-27 02:09:39,940] 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-01-27 02:09:39,943] INFO [Broker id=3] Skipped 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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,943] 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-01-27 02:09:39,946] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:39,948] 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-01-27 02:09:39,951] 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-01-27 02:09:39,954] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:39,956] 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-01-27 02:09:39,959] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:39,962] INFO [Broker id=3] Skipped 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-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,962] 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-01-27 02:09:39,964] INFO [Broker id=3] Skipped 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-01-27 02:09:39,964] 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-01-27 02:09:39,969] 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-01-27 02:09:39,972] 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-01-27 02:09:39,974] 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-01-27 02:09:39,977] INFO [Broker id=3] Skipped 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-01-27 02:09:39,977] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:39,979] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-27 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-01-27 02:09:39,982] INFO [Broker id=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-01-27 02:09:39,982] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:39,985] 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-01-27 02:09:39,987] 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-01-27 02:09:39,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-8-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:39,989] 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-01-27 02:09:39,992] INFO [Broker id=3] Skipped 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-01-27 02:09:39,992] 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-01-27 02:09:39,994] 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-01-27 02:09:39,997] 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-01-27 02:09:39,999] INFO [Broker id=3] Skipped 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-01-27 02:09:39,999] 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-01-27 02:09:40,002] 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-01-27 02:09:40,004] 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-01-27 02:09:40,007] 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-01-27 02:09:40,009] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,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-14-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,012] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,014] INFO [Broker id=3] Skipped 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-01-27 02:09:40,014] 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-01-27 02:09:40,017] INFO [Broker id=3] Skipped 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-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,017] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,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-28-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,019] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:40,021] INFO [Broker id=3] Skipped 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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,021] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,023] INFO [Broker id=3] Skipped 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-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,024] 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-01-27 02:09:40,026] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,028] INFO [Broker id=3] Skipped 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-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,028] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:40,031] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,033] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,033] 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-01-27 02:09:40,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-29-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,036] INFO [Broker id=3] Leader -uve-topic-28-0 starts at leader epoch 5 from offset 1009 with high watermark 1009 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,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-28-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,038] INFO [Broker id=3] Leader -uve-topic-21-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,041] INFO [Broker id=3] Skipped 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-01-27 02:09:40,041] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:40,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-17-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,043] 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-01-27 02:09:40,046] INFO [Broker id=3] Skipped 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-01-27 02:09:40,046] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:40,048] 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-01-27 02:09:40,051] INFO [Broker id=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-01-27 02:09:40,051] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,053] INFO [Broker id=3] Skipped 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-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,053] 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-01-27 02:09:40,056] INFO [Broker id=3] Skipped 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-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,056] 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-01-27 02:09:40,058] INFO [Broker id=3] Skipped 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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,058] 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-01-27 02:09:40,061] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:40,063] INFO [Broker id=3] Skipped 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-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,064] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,067] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,069] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,072] 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-01-27 02:09:40,074] 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-01-27 02:09:40,077] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,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-3-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,079] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:40,082] INFO [Broker id=3] Skipped 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-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,082] 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-01-27 02:09:40,084] INFO [Broker id=3] Skipped 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-01-27 02:09:40,084] 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-01-27 02:09:40,087] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,089] INFO [Broker id=3] Skipped 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-01-27 02:09:40,089] 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-01-27 02:09:40,092] INFO [Broker id=3] Skipped 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-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,092] 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-01-27 02:09:40,099] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,099] 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-01-27 02:09:40,101] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,104] INFO [Broker id=3] Skipped 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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,104] 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-01-27 02:09:40,106] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,106] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-5 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-01-27 02:09:40,110] INFO [Broker id=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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,110] 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-01-27 02:09:40,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-20-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,112] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-24 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-01-27 02:09:40,116] INFO [Broker id=3] Leader -uve-topic-6-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,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-6-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,119] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:40,126] 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-01-27 02:09:40,129] 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-01-27 02:09:40,131] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,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-22-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,134] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:40,136] 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-01-27 02:09:40,139] 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-01-27 02:09:40,142] INFO [Broker id=3] Skipped 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-01-27 02:09:40,142] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:40,145] INFO [Broker id=3] Leader -uve-topic-22-0 starts at leader epoch 5 from offset 3011 with high watermark 3011 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,147] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,150] 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-01-27 02:09:40,152] 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-01-27 02:09:40,155] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:40,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-21-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,158] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,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-28-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,160] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,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-15-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,163] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:40,165] 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-01-27 02:09:40,168] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,171] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:40,173] 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-01-27 02:09:40,176] 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-01-27 02:09:40,178] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,181] INFO [Broker id=3] Skipped 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-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,181] 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-01-27 02:09:40,183] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:40,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-7-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,186] 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-01-27 02:09:40,188] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,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-14-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,191] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:40,194] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,196] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,201] 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-01-27 02:09:40,204] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:40,207] 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-01-27 02:09:40,210] 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-01-27 02:09:40,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-2-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,213] 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-01-27 02:09:40,216] INFO [Broker id=3] Skipped 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-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,216] 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-01-27 02:09:40,220] 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-01-27 02:09:40,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 structured_syslog_topic-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,227] INFO [Broker id=3] Leader -uve-topic-1-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,231] INFO [Broker id=3] Skipped 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-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,231] 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-01-27 02:09:40,234] INFO [Broker id=3] Skipped 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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,234] 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-01-27 02:09:40,237] INFO [Broker id=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-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,237] 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-01-27 02:09:40,240] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,243] INFO [Broker id=3] Skipped 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-01-27 02:09:40,243] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:40,246] 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-01-27 02:09:40,248] 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-01-27 02:09:40,253] 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-01-27 02:09:40,258] 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-01-27 02:09:40,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-20-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,261] INFO [Broker id=3] Leader -uve-topic-11-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,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-11-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,265] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:40,268] INFO [Broker id=3] Skipped 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-01-27 02:09:40,268] 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-01-27 02:09:40,271] INFO [Broker id=3] Skipped 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-01-27 02:09:40,271] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:40,274] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,279] 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-01-27 02:09:40,282] 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-01-27 02:09:40,285] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:40,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-5-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,288] INFO [Broker id=3] Leader -uve-topic-6-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,291] INFO [Broker id=3] Skipped 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-01-27 02:09:40,291] 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-01-27 02:09:40,295] INFO [Broker id=3] Skipped 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-01-27 02:09:40,295] 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-01-27 02:09:40,298] 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-01-27 02:09:40,301] INFO [Broker id=3] Skipped 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-01-27 02:09:40,301] 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-01-27 02:09:40,304] INFO [Broker id=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-01-27 02:09:40,304] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,308] 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-01-27 02:09:40,310] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,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-14-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,313] 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-01-27 02:09:40,316] 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-01-27 02:09:40,319] INFO [Broker id=3] Skipped 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-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,319] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,321] INFO [Broker id=3] Skipped 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-01-27 02:09:40,321] 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-01-27 02:09:40,324] INFO [Broker id=3] Leader -uve-topic-1-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,327] INFO [Broker id=3] Skipped 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-01-27 02:09:40,327] 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-01-27 02:09:40,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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,329] 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-01-27 02:09:40,332] 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-01-27 02:09:40,335] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:40,338] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,342] INFO [Broker id=3] Skipped 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-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,342] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,344] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:40,348] INFO [Broker id=3] Leader -uve-topic-25-0 starts at leader epoch 5 from offset 431 with high watermark 431 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,352] 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-01-27 02:09:40,355] 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-01-27 02:09:40,358] 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-01-27 02:09:40,361] INFO [Broker id=3] Skipped 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-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,361] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,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-25-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,364] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,367] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:40,370] INFO [Broker id=3] Skipped 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-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,370] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:40,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-7-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,373] 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-01-27 02:09:40,376] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,380] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,383] 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-01-27 02:09:40,387] 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-01-27 02:09:40,391] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:40,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-10-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,394] INFO [Broker id=3] Leader -uve-topic-11-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,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-11-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,398] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:40,401] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-21 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-01-27 02:09:40,405] INFO [Broker id=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-01-27 02:09:40,405] INFO [Broker id=3] Leader -uve-topic-19-0 starts at leader epoch 4 from offset 162 with high watermark 162 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:40,408] 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-01-27 02:09:40,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 structured_syslog_topic-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,411] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-2 starts at leader epoch 5 from offset 8 with high watermark 8 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,413] INFO [Broker id=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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,413] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,416] 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-01-27 02:09:40,419] 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-01-27 02:09:40,422] 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-01-27 02:09:40,426] INFO [Broker id=3] Skipped 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-01-27 02:09:40,426] 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-01-27 02:09:40,429] 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-01-27 02:09:40,432] INFO [Broker id=3] Skipped 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-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,432] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,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-14-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,434] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:40,436] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,437] 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-01-27 02:09:40,439] 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-01-27 02:09:40,442] INFO [Broker id=3] Skipped 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-01-27 02:09:40,442] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:40,446] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:40,448] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:40,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-0-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,451] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:40,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-4-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,454] 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-01-27 02:09:40,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-8-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,457] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,460] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,464] INFO [Broker id=3] Skipped 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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,464] 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-01-27 02:09:40,467] 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-01-27 02:09:40,469] INFO [Broker id=3] Skipped 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-01-27 02:09:40,469] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:40,472] 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-01-27 02:09:40,474] 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-01-27 02:09:40,477] INFO [Broker id=3] Skipped 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-01-27 02:09:40,477] 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-01-27 02:09:40,480] INFO [Broker id=3] Skipped 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-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,480] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,482] INFO [Broker id=3] Skipped 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-01-27 02:09:40,482] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 4 from offset 8 with high watermark 8 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:40,486] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:40,489] INFO [Broker id=3] Skipped 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-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,489] 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-01-27 02:09:40,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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,491] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:40,494] INFO [Broker id=3] Skipped 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-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,494] 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-01-27 02:09:40,496] INFO [Broker id=3] Skipped 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-01-27 02:09:40,496] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:40,499] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:40,502] 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-01-27 02:09:40,505] 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-01-27 02:09:40,509] INFO [Broker id=3] Skipped 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-01-27 02:09:40,509] 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-01-27 02:09:40,513] INFO [Broker id=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-01-27 02:09:40,513] 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-01-27 02:09:40,516] INFO [Broker id=3] Skipped 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-01-27 02:09:40,516] 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-01-27 02:09:40,518] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,522] 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-01-27 02:09:40,524] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:40,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-5-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,527] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,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-13-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,529] 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-01-27 02:09:40,532] 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-01-27 02:09:40,534] 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-01-27 02:09:40,536] 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-01-27 02:09:40,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-20-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,539] INFO [Broker id=3] Leader -uve-topic-11-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,542] INFO [Broker id=3] Skipped 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-01-27 02:09:40,542] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:40,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-24-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,544] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:40,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-4-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,547] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,549] INFO [Broker id=3] Skipped 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-01-27 02:09:40,549] 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-01-27 02:09:40,552] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:40,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-5-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,554] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:40,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-7-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,557] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,561] 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-01-27 02:09:40,564] INFO [Broker id=3] Leader -uve-topic-6-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,566] INFO [Broker id=3] Skipped 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-01-27 02:09:40,566] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,569] 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-01-27 02:09:40,571] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,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-22-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,575] 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-01-27 02:09:40,577] 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-01-27 02:09:40,580] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,582] INFO [Broker id=3] Skipped 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-01-27 02:09:40,582] 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-01-27 02:09:40,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-9-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,585] 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-01-27 02:09:40,587] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:40,591] INFO [Broker id=3] Skipped 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-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,591] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,593] INFO [Broker id=3] Skipped 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-01-27 02:09:40,593] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,596] INFO [Broker id=3] Skipped 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-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,596] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:40,598] INFO [Broker id=3] Skipped 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-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,599] 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-01-27 02:09:40,601] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,601] 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-01-27 02:09:40,604] 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-01-27 02:09:40,607] INFO [Broker id=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-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,607] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,611] 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-01-27 02:09:40,615] 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-01-27 02:09:40,620] 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-01-27 02:09:40,623] INFO [Broker id=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-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,623] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,625] 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-01-27 02:09:40,628] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:40,630] INFO [Broker id=3] Skipped 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-01-27 02:09:40,630] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:40,633] INFO [Broker id=3] Skipped 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-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,633] 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-01-27 02:09:40,636] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,638] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,641] 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-01-27 02:09:40,644] INFO [Broker id=3] Skipped 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-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,644] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,647] INFO [Broker id=3] Skipped 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-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,647] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,653] 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-01-27 02:09:40,658] 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-01-27 02:09:40,660] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:40,663] INFO [Broker id=3] Skipped 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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,663] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:40,666] 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-01-27 02:09:40,669] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-15 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-01-27 02:09:40,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 HEALTH_CHECK_TOPIC-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,672] 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-01-27 02:09:40,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-6-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,674] 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-01-27 02:09:40,678] INFO [Broker id=3] Skipped 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-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,678] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:40,681] INFO [Broker id=3] Skipped 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-01-27 02:09:40,681] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,684] 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-01-27 02:09:40,691] 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-01-27 02:09:40,695] INFO [Broker id=3] Skipped 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-01-27 02:09:40,695] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,699] 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-01-27 02:09:40,702] 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-01-27 02:09:40,706] INFO [Broker id=3] Skipped 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-01-27 02:09:40,706] 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-01-27 02:09:40,708] 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-01-27 02:09:40,711] 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-01-27 02:09:40,713] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-25 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-01-27 02:09:40,717] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:40,719] 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-01-27 02:09:40,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-29-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,722] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:40,724] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:40,728] INFO [Broker id=3] Skipped 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-01-27 02:09:40,728] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:40,730] INFO [Broker id=3] Skipped 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-01-27 02:09:40,730] 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-01-27 02:09:40,733] 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-01-27 02:09:40,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-16-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,736] 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-01-27 02:09:40,738] 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-01-27 02:09:40,741] 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-01-27 02:09:40,743] INFO [Broker id=3] Skipped 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-01-27 02:09:40,743] INFO [Broker id=3] Leader -uve-topic-1-0 starts at leader epoch 5 from offset 627 with high watermark 627 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,745] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,748] 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-01-27 02:09:40,752] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,754] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:40,757] INFO [Broker id=3] Skipped 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-01-27 02:09:40,757] 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-01-27 02:09:40,761] INFO [Broker id=3] Skipped 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-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,761] 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-01-27 02:09:40,764] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:40,766] INFO [Broker id=3] Skipped 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-01-27 02:09:40,767] 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-01-27 02:09:40,769] 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-01-27 02:09:40,771] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:40,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 -uve-topic-5-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,773] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,775] INFO [Broker id=3] Skipped 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-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,776] 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-01-27 02:09:40,778] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,781] 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-01-27 02:09:40,783] 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-01-27 02:09:40,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-16-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,786] 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-01-27 02:09:40,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-29-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,788] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:40,790] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,790] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,794] INFO [Broker id=3] Skipped 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-01-27 02:09:40,794] 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-01-27 02:09:40,798] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:40,801] INFO [Broker id=3] Skipped 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-01-27 02:09:40,801] 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-01-27 02:09:40,804] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:40,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-24-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,807] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:40,810] INFO [Broker id=3] Skipped 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-01-27 02:09:40,810] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:40,815] INFO [Broker id=3] Skipped 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-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,815] 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-01-27 02:09:40,818] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:40,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-5-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,824] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:40,828] INFO [Broker id=3] Skipped 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-01-27 02:09:40,828] 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-01-27 02:09:40,831] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:40,834] INFO [Broker id=3] Skipped 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-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,834] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:40,837] 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-01-27 02:09:40,840] 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-01-27 02:09:40,843] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-12 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-01-27 02:09:40,847] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:40,851] INFO [Broker id=3] Skipped 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-01-27 02:09:40,851] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,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-25-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,854] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:40,856] INFO [Broker id=3] Skipped 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-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,856] 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-01-27 02:09:40,859] INFO [Broker id=3] Skipped 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-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,859] 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-01-27 02:09:40,861] INFO [Broker id=3] Skipped 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-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,861] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:40,864] INFO [Broker id=3] Skipped 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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,864] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:40,868] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:40,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-17-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,870] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:40,873] 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-01-27 02:09:40,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-29-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,877] 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-01-27 02:09:40,879] INFO [Broker id=3] Skipped 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-01-27 02:09:40,879] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,882] INFO [Broker id=3] Skipped 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-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,882] 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-01-27 02:09:40,886] INFO [Broker id=3] Skipped 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-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,887] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:40,891] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,891] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-3 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-01-27 02:09:40,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 HEALTH_CHECK_TOPIC-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,894] 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-01-27 02:09:40,901] 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-01-27 02:09:40,904] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,906] 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-01-27 02:09:40,908] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:40,911] 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-01-27 02:09:40,914] INFO [Broker id=3] Skipped 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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,914] 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-01-27 02:09:40,916] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:40,920] 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-01-27 02:09:40,926] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:40,930] INFO [Broker id=3] Skipped 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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,930] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,933] INFO [Broker id=3] Skipped 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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,933] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:40,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-19-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,937] 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-01-27 02:09:40,940] 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-01-27 02:09:40,943] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:40,946] 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-01-27 02:09:40,948] INFO [Broker id=3] Skipped 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-01-27 02:09:40,949] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,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-25-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,951] 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-01-27 02:09:40,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-12-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,956] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:40,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-27-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,959] 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-01-27 02:09:40,961] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:40,964] 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-01-27 02:09:40,966] 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-01-27 02:09:40,969] INFO [Broker id=3] Skipped 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-01-27 02:09:40,969] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:40,972] INFO [Broker id=3] Skipped 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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,972] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:40,975] INFO [Broker id=3] Skipped 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-01-27 02:09:40,975] 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-01-27 02:09:40,978] 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-01-27 02:09:40,980] INFO [Broker id=3] Skipped 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-01-27 02:09:40,980] 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-01-27 02:09:40,983] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:40,986] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:40,988] 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-01-27 02:09:40,991] INFO [Broker id=3] Skipped 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-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:40,991] 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-01-27 02:09:40,993] 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-01-27 02:09:40,996] 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-01-27 02:09:40,999] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-19 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-01-27 02:09:41,003] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:41,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-22-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,006] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:41,009] INFO [Broker id=3] Skipped 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-01-27 02:09:41,009] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:41,012] 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-01-27 02:09:41,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-29-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,015] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:41,018] 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-01-27 02:09:41,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 structured_syslog_topic-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,020] 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-01-27 02:09:41,023] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,025] INFO [Broker id=3] Skipped 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-01-27 02:09:41,025] 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-01-27 02:09:41,027] 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-01-27 02:09:41,030] INFO [Broker id=3] Skipped 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-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,030] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:41,032] 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-01-27 02:09:41,035] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:41,038] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-0 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-01-27 02:09:41,042] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,044] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,047] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,050] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,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-11-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,052] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,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-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,055] 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-01-27 02:09:41,057] INFO [Broker id=3] Skipped 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-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,057] INFO [Broker id=3] Leader -uve-topic-12-0 starts at leader epoch 5 from offset 168 with high watermark 168 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:41,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-12-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,060] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:41,062] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,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-5-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,065] 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-01-27 02:09:41,069] INFO [Broker id=3] Skipped 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-01-27 02:09:41,069] 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-01-27 02:09:41,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 -uve-topic-9-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,072] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,075] INFO [Broker id=3] Skipped 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-01-27 02:09:41,075] 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-01-27 02:09:41,078] 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-01-27 02:09:41,081] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:41,085] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,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-0-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,088] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,091] INFO [Broker id=3] Skipped 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-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,091] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,094] INFO [Broker id=3] Skipped 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-01-27 02:09:41,094] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:41,097] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,100] INFO [Broker id=3] Skipped 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-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,100] 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-01-27 02:09:41,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-12-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,103] 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-01-27 02:09:41,106] 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-01-27 02:09:41,108] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 4 from offset 7 with high watermark 7 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:41,111] INFO [Broker id=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-01-27 02:09:41,111] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,113] INFO [Broker id=3] Skipped 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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,113] 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-01-27 02:09:41,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-6-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,117] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,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-10-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,119] INFO [Broker id=3] Leader -uve-topic-27-0 starts at leader epoch 5 from offset 1394 with high watermark 1394 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:41,122] 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-01-27 02:09:41,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-23-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,125] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:41,128] 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-01-27 02:09:41,130] INFO [Broker id=3] Skipped 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-01-27 02:09:41,130] 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-01-27 02:09:41,133] INFO [Broker id=3] Skipped 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-01-27 02:09:41,133] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,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-19-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,136] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:41,138] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,141] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,143] 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-01-27 02:09:41,145] 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-01-27 02:09:41,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-23-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,148] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-28 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-01-27 02:09:41,152] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,154] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,157] INFO [Broker id=3] Skipped 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-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,157] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,159] INFO [Broker id=3] Skipped 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-01-27 02:09:41,159] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,161] INFO [Broker id=3] Skipped 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-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,161] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,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-4-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,163] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:41,167] INFO [Broker id=3] Skipped 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-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,167] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,169] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,171] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:41,174] 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-01-27 02:09:41,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-2-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,176] 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-01-27 02:09:41,179] INFO [Broker id=3] Skipped 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-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,179] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,181] INFO [Broker id=3] Skipped 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-01-27 02:09:41,181] 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-01-27 02:09:41,184] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,184] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,187] INFO [Broker id=3] Skipped 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-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,187] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:41,189] 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-01-27 02:09:41,192] INFO [Broker id=3] Skipped 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-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,192] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,197] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:41,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-15-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,202] 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-01-27 02:09:41,205] INFO [Broker id=3] Skipped 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-01-27 02:09:41,205] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,209] 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-01-27 02:09:41,211] 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-01-27 02:09:41,214] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:41,217] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,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-25-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,220] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,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-12-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,223] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,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-19-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,225] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,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-24-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,228] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,231] INFO [Broker id=3] Skipped 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-01-27 02:09:41,231] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,235] INFO [Broker id=3] Skipped 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-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,235] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,238] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,241] INFO [Broker id=3] Skipped 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-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,241] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,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-5-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,244] 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-01-27 02:09:41,246] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,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-27-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,249] 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-01-27 02:09:41,251] 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-01-27 02:09:41,256] 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-01-27 02:09:41,260] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,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-10-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,264] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:41,267] INFO [Broker id=3] Skipped 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-01-27 02:09:41,267] 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-01-27 02:09:41,270] 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-01-27 02:09:41,273] INFO [Broker id=3] Skipped 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-01-27 02:09:41,273] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,275] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,278] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,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-26-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,280] 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-01-27 02:09:41,283] INFO [Broker id=3] Skipped 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-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,283] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,286] 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-01-27 02:09:41,289] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,292] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:41,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-22-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,294] 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-01-27 02:09:41,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-16-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,297] 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-01-27 02:09:41,308] INFO [Broker id=3] Skipped 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-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,308] INFO [Broker id=3] Leader -uve-topic-21-0 starts at leader epoch 4 from offset 1883 with high watermark 1883 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:41,311] INFO [Broker id=3] Skipped 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-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,311] 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-01-27 02:09:41,314] INFO [Broker id=3] Skipped 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-01-27 02:09:41,314] 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-01-27 02:09:41,317] 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-01-27 02:09:41,319] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:41,324] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,327] INFO [Broker id=3] Skipped 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-01-27 02:09:41,327] 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-01-27 02:09:41,329] 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-01-27 02:09:41,332] INFO [Broker id=3] Skipped 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-01-27 02:09:41,332] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,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-1-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,334] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:41,337] 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-01-27 02:09:41,340] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,343] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-6 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-01-27 02:09:41,346] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,350] INFO [Broker id=3] Skipped 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-01-27 02:09:41,350] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:41,352] INFO [Broker id=3] Skipped 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-01-27 02:09:41,352] 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-01-27 02:09:41,355] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,355] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,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-19-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,359] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 5 from offset 7 with high watermark 7 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:41,365] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:41,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-17-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,368] 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-01-27 02:09:41,371] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,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-1-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,374] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,376] INFO [Broker id=3] Skipped 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-01-27 02:09:41,376] 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-01-27 02:09:41,379] INFO [Broker id=3] Skipped 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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,379] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,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-5-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,382] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,386] INFO [Broker id=3] Skipped 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-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,386] 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-01-27 02:09:41,389] INFO [Broker id=3] Skipped 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-01-27 02:09:41,389] 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-01-27 02:09:41,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-23-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,392] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,395] INFO [Broker id=3] Skipped 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-01-27 02:09:41,395] 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-01-27 02:09:41,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-3-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,398] 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-01-27 02:09:41,400] INFO [Broker id=3] Skipped 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-01-27 02:09:41,400] 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-01-27 02:09:41,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-18-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,403] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,405] INFO [Broker id=3] Skipped 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-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,405] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,408] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,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-5-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,411] 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-01-27 02:09:41,413] INFO [Broker id=3] Skipped 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-01-27 02:09:41,413] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,415] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,424] INFO [Broker id=3] Skipped 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-01-27 02:09:41,424] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,427] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,430] INFO [Broker id=3] Skipped 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-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,430] 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-01-27 02:09:41,433] INFO [Broker id=3] Skipped 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-01-27 02:09:41,433] 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-01-27 02:09:41,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-18-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,435] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,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-1-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,437] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:41,442] 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-01-27 02:09:41,446] 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-01-27 02:09:41,449] INFO [Broker id=3] Skipped 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-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,449] 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-01-27 02:09:41,451] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,454] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,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-11-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,457] 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-01-27 02:09:41,460] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:41,463] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:41,466] 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-01-27 02:09:41,469] INFO [Broker id=3] Skipped 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-01-27 02:09:41,469] 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-01-27 02:09:41,471] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,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-7-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,474] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,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-27-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,476] 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-01-27 02:09:41,479] 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-01-27 02:09:41,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-16-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,481] 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-01-27 02:09:41,486] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,488] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,491] 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-01-27 02:09:41,493] INFO [Broker id=3] Leader -uve-topic-24-0 starts at leader epoch 4 from offset 738 with high watermark 738 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:41,496] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,498] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,498] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:41,501] 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-01-27 02:09:41,504] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,506] INFO [Broker id=3] Skipped 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-01-27 02:09:41,506] 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-01-27 02:09:41,508] INFO [Broker id=3] Skipped 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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,508] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:41,511] 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-01-27 02:09:41,515] 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-01-27 02:09:41,518] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,520] 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-01-27 02:09:41,523] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,525] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,528] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,531] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,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-26-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,533] 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-01-27 02:09:41,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-13-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,536] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:41,540] INFO [Broker id=3] Skipped 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-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,540] 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-01-27 02:09:41,543] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-29 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-01-27 02:09:41,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 HEALTH_CHECK_TOPIC-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,547] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:41,550] INFO [Broker id=3] Skipped 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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,550] 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-01-27 02:09:41,552] INFO [Broker id=3] Skipped 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-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,552] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,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 -uve-topic-19-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,555] 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-01-27 02:09:41,558] 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-01-27 02:09:41,560] INFO [Broker id=3] Skipped 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-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,560] 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-01-27 02:09:41,563] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,563] 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-01-27 02:09:41,566] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,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-10-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,569] 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-01-27 02:09:41,573] INFO [Broker id=3] Skipped 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-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,573] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,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-19-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,576] 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-01-27 02:09:41,578] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,581] 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-01-27 02:09:41,584] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:41,587] 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-01-27 02:09:41,590] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:41,594] 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-01-27 02:09:41,598] INFO [Broker id=3] Skipped 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-01-27 02:09:41,598] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,601] INFO [Broker id=3] Skipped 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-01-27 02:09:41,601] 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-01-27 02:09:41,603] INFO [Broker id=3] Skipped 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-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,603] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,606] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,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-1-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,608] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:41,611] INFO [Broker id=3] Skipped 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-01-27 02:09:41,611] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,617] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,620] 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-01-27 02:09:41,624] INFO [Broker id=3] Skipped 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-01-27 02:09:41,624] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,627] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,629] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,633] INFO [Broker id=3] Skipped 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-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,633] 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-01-27 02:09:41,635] INFO [Broker id=3] Skipped 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-01-27 02:09:41,635] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,637] 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-01-27 02:09:41,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-16-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,640] 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-01-27 02:09:41,642] INFO [Broker id=3] Skipped 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-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,642] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,644] 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-01-27 02:09:41,648] 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-01-27 02:09:41,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-2-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,651] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,653] 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-01-27 02:09:41,658] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,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-7-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,662] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,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-27-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,665] 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-01-27 02:09:41,668] 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-01-27 02:09:41,672] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,674] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,678] INFO [Broker id=3] Skipped 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-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,678] 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-01-27 02:09:41,680] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:41,688] 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-01-27 02:09:41,691] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,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-10-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,694] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,697] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,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 -uve-topic-1-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,699] 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-01-27 02:09:41,702] INFO [Broker id=3] Skipped 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-01-27 02:09:41,702] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,704] 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-01-27 02:09:41,706] INFO [Broker id=3] Skipped 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-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,706] 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-01-27 02:09:41,710] INFO [Broker id=3] Skipped 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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,710] 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-01-27 02:09:41,714] 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-01-27 02:09:41,718] INFO [Broker id=3] Skipped 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-01-27 02:09:41,718] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,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-1-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,722] 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-01-27 02:09:41,725] INFO [Broker id=3] Skipped 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-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,725] 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-01-27 02:09:41,728] INFO [Broker id=3] Skipped 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-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,728] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,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-19-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,731] 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-01-27 02:09:41,734] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,737] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,739] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,747] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,747] 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-01-27 02:09:41,750] 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-01-27 02:09:41,753] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:41,756] 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-01-27 02:09:41,759] INFO [Broker id=3] Skipped 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-01-27 02:09:41,759] 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-01-27 02:09:41,762] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:41,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-21-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,764] 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-01-27 02:09:41,767] 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-01-27 02:09:41,769] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:41,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-5-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,772] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,779] INFO [Broker id=3] Skipped 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-01-27 02:09:41,779] 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-01-27 02:09:41,782] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,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-7-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,786] 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-01-27 02:09:41,789] INFO [Broker id=3] Skipped 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-01-27 02:09:41,789] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,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-27-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,794] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,797] INFO [Broker id=3] Skipped 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-01-27 02:09:41,797] 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-01-27 02:09:41,800] INFO [Broker id=3] Skipped 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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,800] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:41,803] INFO [Broker id=3] Skipped 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-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,803] 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-01-27 02:09:41,806] INFO [Broker id=3] Skipped 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-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,806] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,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-10-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,811] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,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-19-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,816] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:41,818] 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-01-27 02:09:41,821] INFO [Broker id=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-01-27 02:09:41,821] 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-01-27 02:09:41,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-24-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,824] 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-01-27 02:09:41,826] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,829] INFO [Broker id=3] Skipped 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-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,829] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,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-25-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,832] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,835] INFO [Broker id=3] Skipped 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-01-27 02:09:41,835] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:41,840] 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-01-27 02:09:41,844] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-7 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-01-27 02:09:41,854] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:41,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-17-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,857] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:41,860] 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-01-27 02:09:41,863] INFO [Broker id=3] Leader -uve-topic-0-0 starts at leader epoch 4 from offset 3417 with high watermark 3417 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:41,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-0-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,870] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,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-10-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,874] 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-01-27 02:09:41,878] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:41,881] 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-01-27 02:09:41,885] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,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-10-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,888] 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-01-27 02:09:41,893] 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-01-27 02:09:41,897] INFO [Broker id=3] Skipped 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-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,897] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:41,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-15-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,901] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-26 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-01-27 02:09:41,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 HEALTH_CHECK_TOPIC-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,903] 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-01-27 02:09:41,906] INFO [Broker id=3] Skipped 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-01-27 02:09:41,906] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:41,908] INFO [Broker id=3] Skipped 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-01-27 02:09:41,908] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:41,916] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,920] INFO [Broker id=3] Leader -uve-topic-25-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-01-27 02:09:41,923] 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-01-27 02:09:41,926] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,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-27-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,931] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:41,935] INFO [Broker id=3] Skipped 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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,935] 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-01-27 02:09:41,937] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:41,942] 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-01-27 02:09:41,945] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:41,948] INFO [Broker id=3] Leader -uve-topic-24-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-01-27 02:09:41,951] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:41,953] INFO [Broker id=3] Skipped 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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,953] 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-01-27 02:09:41,957] INFO [Broker id=3] Skipped 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-01-27 02:09:41,957] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:41,965] 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-01-27 02:09:41,969] 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-01-27 02:09:41,971] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:41,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-1-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,974] 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-01-27 02:09:41,977] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:41,980] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:41,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-14-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:41,984] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:41,987] 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-01-27 02:09:41,990] 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-01-27 02:09:41,993] 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-01-27 02:09:41,998] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:42,002] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,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-9-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,005] 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-01-27 02:09:42,008] 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-01-27 02:09:42,010] INFO [Broker id=3] Skipped 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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,010] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:42,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-26-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,013] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:42,016] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,021] INFO [Broker id=3] Skipped 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-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,021] 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-01-27 02:09:42,024] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:42,027] INFO [Broker id=3] Skipped 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-01-27 02:09:42,027] 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-01-27 02:09:42,029] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:42,032] INFO [Broker id=3] Skipped 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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,032] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:42,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-3-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,034] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:42,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-19-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,037] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:42,040] INFO [Broker id=3] Skipped 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-01-27 02:09:42,040] 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-01-27 02:09:42,042] INFO [Broker id=3] Leader -uve-topic-23-0 starts at leader epoch 4 from offset 549 with high watermark 549 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:42,045] INFO [Broker id=3] Skipped 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-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,045] 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-01-27 02:09:42,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-24-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,047] 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-01-27 02:09:42,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-28-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,050] 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-01-27 02:09:42,053] INFO [Broker id=3] Skipped 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-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,053] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:42,055] INFO [Broker id=3] Skipped 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-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,055] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-23 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:42,058] INFO [Broker id=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-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,058] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:42,061] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,061] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,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-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,064] 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-01-27 02:09:42,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-20-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,067] 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-01-27 02:09:42,071] INFO [Broker id=3] Skipped 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-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,071] 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-01-27 02:09:42,073] INFO [Broker id=3] Skipped 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-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,073] 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-01-27 02:09:42,076] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:42,082] 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-01-27 02:09:42,085] 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-01-27 02:09:42,087] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:42,090] INFO [Broker id=3] Skipped 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-01-27 02:09:42,090] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-4 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-01-27 02:09:42,094] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,096] 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-01-27 02:09:42,099] 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-01-27 02:09:42,102] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:42,104] 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-01-27 02:09:42,106] INFO [Broker id=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-01-27 02:09:42,107] 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-01-27 02:09:42,109] INFO [Broker id=3] Skipped 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-01-27 02:09:42,109] 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-01-27 02:09:42,111] 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-01-27 02:09:42,114] INFO [Broker id=3] Skipped 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-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,114] 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-01-27 02:09:42,117] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:42,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-5-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,119] 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-01-27 02:09:42,126] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:42,129] INFO [Broker id=3] Skipped 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-01-27 02:09:42,129] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:42,132] INFO [Broker id=3] Skipped 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-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,132] 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-01-27 02:09:42,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-20-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,134] 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-01-27 02:09:42,137] INFO [Broker id=3] Skipped 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-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,137] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,140] 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-01-27 02:09:42,143] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,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-17-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,145] 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-01-27 02:09:42,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 structured_syslog_topic-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,148] 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-01-27 02:09:42,150] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:42,153] 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-01-27 02:09:42,155] 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-01-27 02:09:42,161] INFO [Broker id=3] Skipped 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-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,161] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:42,164] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:42,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-12-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,168] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:42,171] INFO [Broker id=3] Skipped 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-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,171] 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-01-27 02:09:42,175] 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-01-27 02:09:42,179] INFO [Broker id=3] Skipped 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-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,179] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,181] 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-01-27 02:09:42,184] 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-01-27 02:09:42,187] INFO [Broker id=3] Skipped 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-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,187] 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-01-27 02:09:42,190] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-1 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-01-27 02:09:42,195] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,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-17-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,198] 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-01-27 02:09:42,201] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:42,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-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,204] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:42,209] 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-01-27 02:09:42,211] INFO [Broker id=3] Leader -uve-topic-11-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-01-27 02:09:42,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-11-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,214] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:42,217] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:42,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-21-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,220] 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-01-27 02:09:42,223] 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-01-27 02:09:42,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-28-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,225] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:42,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-15-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,228] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-20 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-01-27 02:09:42,231] INFO [Broker id=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-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,231] 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-01-27 02:09:42,234] 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-01-27 02:09:42,237] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:42,241] INFO [Broker id=3] Skipped 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-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,241] 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-01-27 02:09:42,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-13-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,245] INFO [Broker id=3] Leader -uve-topic-26-0 starts at leader epoch 5 from offset 1592 with high watermark 1592 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:42,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-26-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,249] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:42,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-27-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,252] 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-01-27 02:09:42,255] INFO [Broker id=3] Skipped 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-01-27 02:09:42,255] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:42,258] INFO [Broker id=3] Skipped 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-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,258] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:42,261] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:42,264] 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-01-27 02:09:42,266] 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-01-27 02:09:42,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-3-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,269] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,272] INFO [Broker id=3] Leader -uve-topic-28-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-01-27 02:09:42,274] 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-01-27 02:09:42,277] 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-01-27 02:09:42,279] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:42,282] 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-01-27 02:09:42,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-8-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,285] 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-01-27 02:09:42,288] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:42,291] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,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-9-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,294] 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-01-27 02:09:42,300] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:42,307] 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-01-27 02:09:42,314] 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-01-27 02:09:42,320] 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-01-27 02:09:42,324] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:42,327] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,331] 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-01-27 02:09:42,334] 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-01-27 02:09:42,337] INFO [Broker id=3] Leader -uve-topic-5-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-01-27 02:09:42,340] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,345] INFO [Broker id=3] Skipped 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-01-27 02:09:42,345] 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-01-27 02:09:42,349] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:42,352] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,357] INFO [Broker id=3] Skipped 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-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,357] INFO [Broker id=3] Leader -uve-topic-3-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-01-27 02:09:42,361] INFO [Broker id=3] Skipped 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-01-27 02:09:42,361] INFO [Broker id=3] Leader -uve-topic-19-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-01-27 02:09:42,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-19-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,364] INFO [Broker id=3] Leader -uve-topic-4-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-01-27 02:09:42,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-4-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,367] 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-01-27 02:09:42,369] INFO [Broker id=3] Leader -uve-topic-20-0 starts at leader epoch 5 from offset 1081 with high watermark 1081 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-01-27 02:09:42,372] 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-01-27 02:09:42,375] INFO [Broker id=3] Skipped 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-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,375] 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-01-27 02:09:42,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-3-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,378] INFO [Broker id=3] Leader -uve-topic-15-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-01-27 02:09:42,381] INFO [Broker id=3] Skipped 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-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,381] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-17 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-01-27 02:09:42,384] INFO [Broker id=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-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,384] 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-01-27 02:09:42,387] INFO [Broker id=3] Skipped 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-01-27 02:09:42,387] INFO [Broker id=3] Leader -uve-topic-0-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-01-27 02:09:42,390] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,396] INFO [Broker id=3] Skipped 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-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,396] 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-01-27 02:09:42,399] INFO [Broker id=3] Skipped 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-01-27 02:09:42,399] INFO [Broker id=3] Leader -uve-topic-29-0 starts at leader epoch 4 from offset 2349 with high watermark 2349 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-01-27 02:09:42,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-29-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,402] 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-01-27 02:09:42,407] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,407] 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-01-27 02:09:42,410] 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-01-27 02:09:42,415] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,429] INFO [Broker id=3] Leader -uve-topic-1-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-01-27 02:09:42,432] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,432] 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-01-27 02:09:42,436] INFO [Broker id=3] Leader -uve-topic-10-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-01-27 02:09:42,439] INFO [Broker id=3] Leader -uve-topic-17-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-01-27 02:09:42,441] 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-01-27 02:09:42,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 structured_syslog_topic-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,445] 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-01-27 02:09:42,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-2-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,448] INFO [Broker id=3] Leader -uve-topic-14-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-01-27 02:09:42,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-14-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,451] INFO [Broker id=3] Leader -uve-topic-27-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-01-27 02:09:42,453] 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-01-27 02:09:42,456] 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-01-27 02:09:42,459] INFO [Broker id=3] Leader -uve-topic-13-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-01-27 02:09:42,461] INFO [Broker id=3] Skipped 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-01-27 02:09:42,461] INFO [Broker id=3] Leader -uve-topic-26-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-01-27 02:09:42,474] 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-01-27 02:09:42,477] 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-01-27 02:09:42,480] 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-01-27 02:09:42,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-0-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,483] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:42,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-21-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,488] INFO [Broker id=3] Leader -uve-topic-12-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-01-27 02:09:42,491] 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-01-27 02:09:42,494] INFO [Broker id=3] Leader -uve-topic-21-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-01-27 02:09:42,496] INFO [Broker id=3] Skipped 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-01-27 02:09:42,497] 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-01-27 02:09:42,500] INFO [Broker id=3] Skipped 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-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,500] INFO [Broker id=3] Leader -uve-topic-22-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-01-27 02:09:42,503] INFO [Broker id=3] Skipped 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-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,503] INFO [Broker id=3] Leader -uve-topic-9-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-01-27 02:09:42,506] 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-01-27 02:09:42,509] INFO [Broker id=3] Skipped 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-01-27 02:09:42,509] 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-01-27 02:09:42,511] INFO [Broker id=3] Skipped 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-01-27 02:09:42,511] 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-01-27 02:09:42,514] 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-01-27 02:09:42,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-24-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-01-27 02:09:42,517] 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-01-27 02:09:42,520] 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-01-27 02:09:42,523] 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-01-27 02:09:42,528] INFO [Broker id=3] Leader -uve-topic-16-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-01-27 02:09:42,532] INFO [Broker id=3] Skipped 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-01-27 02:09:42,532] INFO [Broker id=3] Leader -uve-topic-7-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-01-27 02:09:42,546] 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-01-27 02:09:42,551] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 3 from controller 2 for 960 partitions (state.change.logger)
[2025-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,552] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,553] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,553] 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-01-27 02:09:42,554] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,554] 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-01-27 02:09:42,554] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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-01-27 02:09:42,555] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,555] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,556] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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-01-27 02:09:42,557] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,557] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,558] 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-01-27 02:09:42,566] 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-01-27 02:09:42,979] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 5 from controller 2 for 960 partitions (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,979] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,980] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,981] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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-01-27 02:09:42,982] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,982] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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-01-27 02:09:42,983] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,983] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:42,984] 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-01-27 02:09:43,002] 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-01-27 02:09:44,387] INFO [Controller id=3 epoch=4] Sending UpdateMetadata request to brokers Set(3) for 0 partitions (state.change.logger)
[2025-01-27 02:09:44,451] 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-01-27 02:09:44,456] INFO [Controller id=3 epoch=4] Sending UpdateMetadata request to brokers Set(3) for 960 partitions (state.change.logger)
[2025-01-27 02:09:44,466] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 3 for 960 partitions (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,466] 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-01-27 02:09:44,466] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,467] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,467] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,468] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,469] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,470] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,471] 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-01-27 02:09:44,483] 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-01-27 02:09:44,539] 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-01-27 02:09:44,540] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,540] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,540] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,540] 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-01-27 02:09:44,540] 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-01-27 02:09:44,540] 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-01-27 02:09:44,540] 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-01-27 02:09:44,540] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,541] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,541] 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-01-27 02:09:44,541] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,542] 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-01-27 02:09:44,542] 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-01-27 02:09:44,542] 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-01-27 02:09:44,542] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,543] 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-01-27 02:09:44,543] 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-01-27 02:09:44,543] 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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,543] 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-01-27 02:09:44,543] 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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,543] 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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,543] 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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,543] 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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,543] 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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,543] 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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,543] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] 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-01-27 02:09:44,544] 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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,544] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,544] 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-01-27 02:09:44,544] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,545] 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-01-27 02:09:44,545] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,545] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,546] 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-01-27 02:09:44,546] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-29 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-8 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-17 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-24 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,547] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,547] 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-01-27 02:09:44,547] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,548] 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-01-27 02:09:44,548] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,548] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,549] 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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,549] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-21 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,550] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,550] 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-01-27 02:09:44,550] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,551] 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-01-27 02:09:44,551] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-5 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,552] 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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,552] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-18 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,553] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-26 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-17 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-25 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-2 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,554] 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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,554] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-28 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,555] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,555] 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-01-27 02:09:44,555] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-23 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-14 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,556] 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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,556] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,556] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] 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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,557] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-20 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 2 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,558] 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-01-27 02:09:44,558] 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-01-27 02:09:44,558] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,559] 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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,559] 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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,559] 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-01-27 02:09:44,559] 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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,559] 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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,559] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,631] 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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,631] 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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,631] 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-01-27 02:09:44,631] 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-01-27 02:09:44,631] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,631] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,632] 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-01-27 02:09:44,632] 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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,632] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,633] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] 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-01-27 02:09:44,634] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-29 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-8 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-17 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-24 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,635] 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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,635] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,636] 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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,636] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-21 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,637] 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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,637] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,637] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-5 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,638] 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-01-27 02:09:44,638] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,638] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-6-18 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,639] 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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,639] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-26 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-17 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-25 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-2 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,640] 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-01-27 02:09:44,640] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-28 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-23 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,641] 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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,641] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,641] 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-01-27 02:09:44,641] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-14 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,642] 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-01-27 02:09:44,642] 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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-12-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-01-27 02:09:44,642] INFO [Controller id=3 epoch=4] Partition -uve-topic-22-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition HEALTH_CHECK_TOPIC-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-19-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-21-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-11-20 state changed to (Leader:3,ISR:3,LeaderEpoch:6,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-01-27 02:09:44,643] 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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-5-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-01-27 02:09:44,643] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,643] 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-01-27 02:09:44,643] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-7-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-26-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-3-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-1-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-4-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-17-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-10-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-16-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-28-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-13-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-0-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-9-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-01-27 02:09:44,644] 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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-27-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-24-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-14-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-15-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-01-27 02:09:44,644] INFO [Controller id=3 epoch=4] Partition -uve-topic-25-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-01-27 02:09:44,645] 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-01-27 02:09:44,646] INFO [Controller id=3 epoch=4] Sending UpdateMetadata request to brokers Set(3) for 960 partitions (state.change.logger)
[2025-01-27 02:09:44,649] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 3 from controller 3 for 960 partitions (state.change.logger)
[2025-01-27 02:09:44,649] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,649] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,649] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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-01-27 02:09:44,650] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,650] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,651] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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 6 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,652] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,653] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,653] 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-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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 4 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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 5 matches the current leader epoch (state.change.logger)
[2025-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,654] 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-01-27 02:09:44,660] 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)
[2025-01-27 02:11:33,821] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 0 (state.change.logger)
[2025-01-27 02:11:33,850] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 2 for 960 partitions (state.change.logger)
[2025-01-27 02:11:34,526] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,648] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,653] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,657] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,667] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,681] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,687] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,700] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,706] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,719] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,731] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,746] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,758] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,767] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,792] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,798] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,802] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,805] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,808] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,812] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,816] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,819] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,823] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,826] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,830] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,833] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,838] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,841] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,845] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,854] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,862] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,868] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,879] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,884] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,891] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,899] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,906] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,917] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,924] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,931] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,940] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,947] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,953] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,966] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,975] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,983] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,991] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:34,997] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,007] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,016] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,021] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,027] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,031] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,035] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,040] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,044] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,048] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,052] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,057] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,062] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,065] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,069] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,078] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,086] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,092] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,096] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,100] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,103] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,110] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,113] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,117] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,125] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,128] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,131] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,134] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,137] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,140] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,147] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,151] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,157] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,160] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,162] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,165] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,171] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,173] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,185] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,193] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,196] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,199] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,204] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,206] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,209] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,212] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,215] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,219] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,222] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,234] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,238] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,240] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,244] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,247] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,249] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,252] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,255] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,257] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,260] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,263] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,266] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,270] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,274] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,278] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,281] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,284] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,287] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,290] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,293] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,296] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,330] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,334] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,339] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,342] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,345] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,348] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,351] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,354] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,356] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,359] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,361] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,368] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,377] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,379] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,382] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,386] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,388] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,391] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,393] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,395] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,397] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,399] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,401] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,403] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,405] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,407] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,409] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,411] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,413] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,415] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,417] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,419] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,421] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,423] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,425] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,427] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,429] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,431] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,433] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,435] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,437] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,439] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,441] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,447] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,450] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,452] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,455] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,457] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,459] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,461] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,463] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,465] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,469] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,472] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,474] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,476] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,479] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,481] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,483] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,485] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,487] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,489] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,491] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,493] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,495] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,497] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,499] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,501] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,503] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,505] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,506] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,508] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,510] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,519] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,522] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,525] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,527] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,529] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,531] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,533] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,536] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,538] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,539] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,541] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,543] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,545] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,547] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,549] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,551] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,553] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,555] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,558] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,560] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,562] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,565] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,588] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,592] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,596] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,598] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,603] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,607] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,610] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,614] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,616] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,619] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,625] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,631] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,636] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,640] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,643] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,645] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,648] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,651] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,653] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,656] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,661] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,663] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,667] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,670] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,673] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,675] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,677] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,679] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,683] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,685] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,687] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,689] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,691] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,693] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,695] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,700] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,702] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,704] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,706] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,708] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,710] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,712] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,714] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,716] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,719] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,721] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,723] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,725] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,727] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,729] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,731] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,733] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,734] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,736] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,738] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,739] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,741] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,743] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,744] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,746] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,748] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,749] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,751] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,753] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,755] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,760] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,762] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,764] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,766] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,768] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,769] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,773] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,776] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,778] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,780] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,782] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,784] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,786] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,788] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,790] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,792] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,794] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,796] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,798] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,800] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,802] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,804] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,806] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,809] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,811] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,813] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,815] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,817] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,819] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,823] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,825] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,828] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,830] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,832] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,834] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,836] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,838] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,840] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,843] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,847] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,850] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,852] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,855] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,858] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,861] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,863] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,865] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,867] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,869] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,871] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,873] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,875] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,877] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,884] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,886] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,888] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,890] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,892] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,894] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,896] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,898] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,899] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,901] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,904] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,907] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,912] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,915] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,918] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,921] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,923] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,926] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,929] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,932] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,934] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,936] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,940] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,943] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,946] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,948] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,950] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,952] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,955] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,957] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,959] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,961] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,964] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,965] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,967] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,970] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,973] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,974] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,977] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,979] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,981] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,983] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:35,985] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,004] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,006] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,009] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,011] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,012] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,014] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,016] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,018] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,020] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,022] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,025] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,027] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,029] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,031] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,033] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,034] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,036] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,038] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,039] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,041] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,042] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,044] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,045] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,047] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,048] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,050] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,051] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,053] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,055] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,056] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,058] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,060] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,061] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,063] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,064] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,066] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,068] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,069] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,071] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,072] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,074] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,075] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,077] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,078] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,080] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,081] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,083] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,085] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,086] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,088] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,090] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,092] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,093] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,095] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,097] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,098] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,100] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,101] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,103] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,105] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,106] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,108] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,110] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,111] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,113] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,114] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,116] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,117] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,129] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,131] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,133] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,135] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,136] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,138] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,140] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,142] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,144] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,146] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,151] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,152] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,154] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,156] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,157] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,159] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,160] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,162] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,164] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,165] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,167] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,169] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,170] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,172] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,173] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,175] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,177] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,179] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,181] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,182] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,185] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,187] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,189] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,191] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,193] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,195] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,197] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,199] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,202] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,204] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,206] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,208] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,210] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,211] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,213] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,215] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,217] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,218] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,220] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,222] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,224] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,225] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,227] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,229] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,231] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,232] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,235] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,237] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,241] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,247] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,249] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,251] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,252] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,254] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,255] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,257] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,259] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,264] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,266] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,269] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,272] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,275] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,280] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,282] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,284] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,286] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,288] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,290] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,291] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,293] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,295] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,297] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,298] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,300] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,301] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,302] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,304] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,305] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,307] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,308] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,314] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,315] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,317] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,318] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,320] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,321] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,323] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,324] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,325] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,327] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,328] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,330] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,332] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,333] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,335] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,338] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,339] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,341] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,342] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,344] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,346] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,347] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,349] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,351] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,352] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,354] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,355] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,357] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,358] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,360] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,361] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,363] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,364] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,366] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,367] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,369] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,370] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,372] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,374] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,375] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,377] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,378] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,380] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,381] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,383] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,384] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,386] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,387] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,389] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,390] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,392] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,394] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,395] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,402] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,404] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,406] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,407] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,409] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,410] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,412] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,413] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,415] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,416] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,418] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,420] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,421] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,423] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,424] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,426] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,427] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,429] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,431] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,432] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,434] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,435] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,437] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,445] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,449] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,451] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,453] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,456] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,457] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,459] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,461] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,463] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,465] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,467] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,469] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,472] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,474] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,476] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,477] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,480] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,482] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,483] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,485] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,486] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,491] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,495] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,497] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,499] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,502] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,504] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,505] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,507] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,508] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,510] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,511] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,514] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,515] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,517] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,518] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,520] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,522] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,523] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,526] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,528] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,529] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,532] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,534] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,536] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,538] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,539] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,545] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,547] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,549] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,551] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,554] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,556] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,558] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,560] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,563] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,565] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,566] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,568] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,570] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,594] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,596] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,598] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,599] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,601] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,603] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,604] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,606] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,607] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,609] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,610] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,612] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,614] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,616] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,619] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,621] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,623] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,625] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,626] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,628] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,629] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,631] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,633] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,634] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,636] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,639] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,641] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,643] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,647] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,648] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,650] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,651] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,653] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,654] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,656] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,657] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,659] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,660] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,662] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,667] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,668] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,670] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,672] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,673] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,676] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,678] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,680] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,681] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,683] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,684] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,688] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,690] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,691] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,695] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,705] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,708] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,710] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,713] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,715] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,720] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,725] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,731] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,733] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,735] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,740] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,747] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,764] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,765] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,771] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,772] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,776] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,778] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,780] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,781] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,783] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,785] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,787] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,788] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,790] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,793] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,795] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,796] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,803] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,805] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,807] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,809] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,812] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,813] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,816] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,817] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,819] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,821] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,824] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,826] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,828] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,830] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,832] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,833] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,835] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,836] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,839] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,845] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,847] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,848] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,850] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,852] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,853] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,855] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,857] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,859] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,860] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,862] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,864] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,866] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,868] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,870] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,872] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,874] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,875] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,877] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,879] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,883] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,885] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,887] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,889] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,890] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,892] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,895] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,897] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,898] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,901] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,903] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,905] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,907] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,914] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,917] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,921] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,924] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,926] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,927] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,929] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,931] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,933] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,935] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,944] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,945] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,947] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,949] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,950] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,952] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,953] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,955] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,958] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,961] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,962] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,966] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,968] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,974] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,976] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,984] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,985] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,987] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,988] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,992] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,994] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,995] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,997] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:36,998] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,000] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,002] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,003] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,007] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,009] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,011] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,013] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,014] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,015] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,017] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,019] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,021] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,023] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,025] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,027] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,029] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,031] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,033] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,035] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,037] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,039] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,041] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,043] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,045] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,047] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,048] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,050] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,051] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,053] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,054] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,057] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,058] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,060] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,061] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,063] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,065] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,066] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,068] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,069] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,071] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,072] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,074] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,076] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,077] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,079] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,081] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,083] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,084] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,086] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,087] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,121] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,124] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,125] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,128] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,129] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,131] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,132] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,134] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,136] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,138] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,140] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,142] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,144] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,147] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,149] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,151] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,152] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,156] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,157] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,159] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,161] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,162] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,164] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,165] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,167] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,168] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,170] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,171] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,173] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,174] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,176] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,180] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,181] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,183] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,184] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,186] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,187] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,189] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,191] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,192] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,194] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,195] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,197] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,198] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,200] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,201] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,203] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,204] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,206] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,207] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,209] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,211] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,212] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,214] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,216] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,217] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,219] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,220] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,222] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,224] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,225] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,227] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,228] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,230] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,231] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,233] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,235] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,236] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,238] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,239] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,240] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,242] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,243] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,245] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,246] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-01-27 02:11:37,249] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 1 for 0 partitions (state.change.logger)
[2025-01-27 02:11:37,288] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 2 (state.change.logger)
[2025-01-27 02:11:37,293] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 3 from controller 2 for 960 partitions (state.change.logger)
[2025-01-27 02:11:37,307] INFO [Broker id=3] Stopped fetchers as part of LeaderAndIsr request correlationId 3 from controller 2 epoch 5 as part of the become-leader transition for 960 partitions (state.change.logger)
[2025-01-27 02:11:37,317] INFO [Broker id=3] Leader -uve-topic-22-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,336] INFO [Broker id=3] Leader -uve-topic-23-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,340] INFO [Broker id=3] Leader -uve-topic-17-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,343] INFO [Broker id=3] Leader -uve-topic-16-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,346] INFO [Broker id=3] Leader -uve-topic-29-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,349] INFO [Broker id=3] Leader -uve-topic-2-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,352] INFO [Broker id=3] Leader -uve-topic-18-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,354] INFO [Broker id=3] Leader -uve-topic-27-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,357] INFO [Broker id=3] Leader -uve-topic-14-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,360] INFO [Broker id=3] Leader -uve-topic-5-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,362] INFO [Broker id=3] Leader -uve-topic-16-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,366] INFO [Broker id=3] Leader -uve-topic-29-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,371] INFO [Broker id=3] Leader -uve-topic-17-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,374] INFO [Broker id=3] Leader -uve-topic-21-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,377] INFO [Broker id=3] Leader -uve-topic-11-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,380] INFO [Broker id=3] Leader -uve-topic-24-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,383] INFO [Broker id=3] Leader -uve-topic-13-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,386] INFO [Broker id=3] Leader -uve-topic-26-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,389] INFO [Broker id=3] Leader -uve-topic-8-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,394] INFO [Broker id=3] Leader -uve-topic-0-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,397] INFO [Broker id=3] Leader -uve-topic-17-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,400] INFO [Broker id=3] Leader -uve-topic-9-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,403] INFO [Broker id=3] Leader -uve-topic-0-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,405] INFO [Broker id=3] Leader -uve-topic-20-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,408] INFO [Broker id=3] Leader -uve-topic-1-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,411] INFO [Broker id=3] Leader -uve-topic-3-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,648] INFO [Broker id=3] Leader -uve-topic-2-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,653] INFO [Broker id=3] Leader -uve-topic-7-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,657] INFO [Broker id=3] Leader -uve-topic-6-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,662] INFO [Broker id=3] Leader -uve-topic-15-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,665] INFO [Broker id=3] Leader -uve-topic-28-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,670] INFO [Broker id=3] Leader -uve-topic-6-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,676] INFO [Broker id=3] Leader -uve-topic-7-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,681] INFO [Broker id=3] Leader -uve-topic-22-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,685] INFO [Broker id=3] Leader -uve-topic-0-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,688] INFO [Broker id=3] Leader -uve-topic-9-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,693] INFO [Broker id=3] Leader -uve-topic-21-8 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,696] INFO [Broker id=3] Leader structured_syslog_topic-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,699] INFO [Broker id=3] Leader -uve-topic-5-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,703] INFO [Broker id=3] Leader -uve-topic-4-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,706] INFO [Broker id=3] Leader -uve-topic-17-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,708] INFO [Broker id=3] Leader -uve-topic-8-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,712] INFO [Broker id=3] Leader -uve-topic-3-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,721] INFO [Broker id=3] Leader -uve-topic-4-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,724] INFO [Broker id=3] Leader -uve-topic-10-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,728] INFO [Broker id=3] Leader -uve-topic-23-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,731] INFO [Broker id=3] Leader -uve-topic-25-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,735] INFO [Broker id=3] Leader -uve-topic-20-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,737] INFO [Broker id=3] Leader -uve-topic-12-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,741] INFO [Broker id=3] Leader -uve-topic-19-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,745] INFO [Broker id=3] Leader -uve-topic-29-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,748] INFO [Broker id=3] Leader -uve-topic-16-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,751] INFO [Broker id=3] Leader -uve-topic-8-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,754] INFO [Broker id=3] Leader -uve-topic-21-17 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,756] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,759] INFO [Broker id=3] Leader -uve-topic-2-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,763] INFO [Broker id=3] Leader -uve-topic-9-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,770] INFO [Broker id=3] Leader -uve-topic-18-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,775] INFO [Broker id=3] Leader -uve-topic-10-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,779] INFO [Broker id=3] Leader -uve-topic-23-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,782] INFO [Broker id=3] Leader -uve-topic-14-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,784] INFO [Broker id=3] Leader -uve-topic-27-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,787] INFO [Broker id=3] Leader -uve-topic-7-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,790] INFO [Broker id=3] Leader -uve-topic-6-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,793] INFO [Broker id=3] Leader -uve-topic-8-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,796] INFO [Broker id=3] Leader -uve-topic-21-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,799] INFO [Broker id=3] Leader -uve-topic-20-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,802] INFO [Broker id=3] Leader -uve-topic-0-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,805] INFO [Broker id=3] Leader -uve-topic-17-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,808] INFO [Broker id=3] Leader -uve-topic-29-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,811] INFO [Broker id=3] Leader -uve-topic-16-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,813] INFO [Broker id=3] Leader -uve-topic-4-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,816] INFO [Broker id=3] Leader -uve-topic-13-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,819] INFO [Broker id=3] Leader -uve-topic-26-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,821] INFO [Broker id=3] Leader -uve-topic-6-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,824] INFO [Broker id=3] Leader -uve-topic-5-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,827] INFO [Broker id=3] Leader -uve-topic-12-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,829] INFO [Broker id=3] Leader -uve-topic-26-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,835] INFO [Broker id=3] Leader -uve-topic-25-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,838] INFO [Broker id=3] Leader -uve-topic-29-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,841] INFO [Broker id=3] Leader -uve-topic-16-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,844] INFO [Broker id=3] Leader -uve-topic-10-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,847] INFO [Broker id=3] Leader -uve-topic-23-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,850] INFO [Broker id=3] Leader -uve-topic-19-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,853] INFO [Broker id=3] Leader -uve-topic-25-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,855] INFO [Broker id=3] Leader -uve-topic-11-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,858] INFO [Broker id=3] Leader -uve-topic-24-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,863] INFO [Broker id=3] Leader -uve-topic-19-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,866] INFO [Broker id=3] Leader -uve-topic-28-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,868] INFO [Broker id=3] Leader -uve-topic-15-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,871] INFO [Broker id=3] Leader -uve-topic-20-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,874] INFO [Broker id=3] Leader -uve-topic-29-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,877] INFO [Broker id=3] Leader -uve-topic-16-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,879] INFO [Broker id=3] Leader -uve-topic-7-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,882] INFO [Broker id=3] Leader -uve-topic-8-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,885] INFO [Broker id=3] Leader -uve-topic-22-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,888] INFO [Broker id=3] Leader -uve-topic-18-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,891] INFO [Broker id=3] Leader -uve-topic-24-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,894] INFO [Broker id=3] Leader -uve-topic-11-29 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,898] INFO [Broker id=3] Leader -uve-topic-17-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,901] INFO [Broker id=3] Leader -uve-topic-22-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,904] INFO [Broker id=3] Leader -uve-topic-1-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,906] INFO [Broker id=3] Leader structured_syslog_topic-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,909] INFO [Broker id=3] Leader -uve-topic-5-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,912] INFO [Broker id=3] Leader -uve-topic-15-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,915] INFO [Broker id=3] Leader -uve-topic-28-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,919] INFO [Broker id=3] Leader -uve-topic-20-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,922] INFO [Broker id=3] Leader -uve-topic-21-5 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,925] INFO [Broker id=3] Leader -uve-topic-7-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,929] INFO [Broker id=3] Leader -uve-topic-3-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,932] INFO [Broker id=3] Leader -uve-topic-8-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,935] INFO [Broker id=3] Leader -uve-topic-21-14 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,938] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,941] INFO [Broker id=3] Leader -uve-topic-0-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,944] INFO [Broker id=3] Leader -uve-topic-24-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,947] INFO [Broker id=3] Leader -uve-topic-23-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,950] INFO [Broker id=3] Leader -uve-topic-11-26 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,953] INFO [Broker id=3] Leader -uve-topic-10-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,956] INFO [Broker id=3] Leader -uve-topic-19-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,959] INFO [Broker id=3] Leader -uve-topic-20-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,962] INFO [Broker id=3] Leader -uve-topic-3-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,964] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,967] INFO [Broker id=3] Leader -uve-topic-7-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,970] INFO [Broker id=3] Leader -uve-topic-17-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,973] INFO [Broker id=3] Leader -uve-topic-16-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,975] INFO [Broker id=3] Leader -uve-topic-29-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,978] INFO [Broker id=3] Leader -uve-topic-0-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,980] INFO [Broker id=3] Leader structured_syslog_topic-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,983] INFO [Broker id=3] Leader -uve-topic-9-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,986] INFO [Broker id=3] Leader -uve-topic-6-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,989] INFO [Broker id=3] Leader -uve-topic-26-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,992] INFO [Broker id=3] Leader -uve-topic-13-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,995] INFO [Broker id=3] Leader -uve-topic-5-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:37,998] INFO [Broker id=3] Leader -uve-topic-7-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,000] INFO [Broker id=3] Leader -uve-topic-8-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,002] INFO [Broker id=3] Leader -uve-topic-19-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,005] INFO [Broker id=3] Leader -uve-topic-4-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,007] INFO [Broker id=3] Leader -uve-topic-25-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,010] INFO [Broker id=3] Leader -uve-topic-20-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,012] INFO [Broker id=3] Leader -uve-topic-12-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,016] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,019] INFO [Broker id=3] Leader -uve-topic-16-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,022] INFO [Broker id=3] Leader -uve-topic-29-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,025] INFO [Broker id=3] Leader -uve-topic-8-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,028] INFO [Broker id=3] Leader -uve-topic-18-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,030] INFO [Broker id=3] Leader -uve-topic-1-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,033] INFO [Broker id=3] Leader -uve-topic-22-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,036] INFO [Broker id=3] Leader -uve-topic-23-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,038] INFO [Broker id=3] Leader -uve-topic-10-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,041] INFO [Broker id=3] Leader -uve-topic-2-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,049] INFO [Broker id=3] Leader -uve-topic-18-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,053] INFO [Broker id=3] Leader -uve-topic-27-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,057] INFO [Broker id=3] Leader -uve-topic-14-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,080] INFO [Broker id=3] Leader -uve-topic-15-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,085] INFO [Broker id=3] Leader -uve-topic-28-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,103] INFO [Broker id=3] Leader -uve-topic-28-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,106] INFO [Broker id=3] Leader -uve-topic-27-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,109] INFO [Broker id=3] Leader -uve-topic-14-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,112] INFO [Broker id=3] Leader -uve-topic-8-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,116] INFO [Broker id=3] Leader -uve-topic-22-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,119] INFO [Broker id=3] Leader -uve-topic-16-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,122] INFO [Broker id=3] Leader -uve-topic-15-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,126] INFO [Broker id=3] Leader -uve-topic-29-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,129] INFO [Broker id=3] Leader -uve-topic-28-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,132] INFO [Broker id=3] Leader -uve-topic-21-2 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,135] INFO [Broker id=3] Leader -uve-topic-17-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,138] INFO [Broker id=3] Leader -uve-topic-20-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,140] INFO [Broker id=3] Leader -uve-topic-21-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,143] INFO [Broker id=3] Leader structured_syslog_topic-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,146] INFO [Broker id=3] Leader -uve-topic-25-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,149] INFO [Broker id=3] Leader -uve-topic-12-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,152] INFO [Broker id=3] Leader -uve-topic-24-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,155] INFO [Broker id=3] Leader -uve-topic-11-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,158] INFO [Broker id=3] Leader -uve-topic-26-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,161] INFO [Broker id=3] Leader -uve-topic-13-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,164] INFO [Broker id=3] Leader -uve-topic-15-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,167] INFO [Broker id=3] Leader -uve-topic-28-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,171] INFO [Broker id=3] Leader -uve-topic-20-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,175] INFO [Broker id=3] Leader -uve-topic-7-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,178] INFO [Broker id=3] Leader -uve-topic-3-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,181] INFO [Broker id=3] Leader -uve-topic-19-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,186] INFO [Broker id=3] Leader -uve-topic-23-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,190] INFO [Broker id=3] Leader -uve-topic-10-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,193] INFO [Broker id=3] Leader -uve-topic-25-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,196] INFO [Broker id=3] Leader -uve-topic-12-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,198] INFO [Broker id=3] Leader -uve-topic-24-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,203] INFO [Broker id=3] Leader -uve-topic-11-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,567] INFO [Broker id=3] Leader -uve-topic-15-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,572] INFO [Broker id=3] Leader -uve-topic-28-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,575] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,578] INFO [Broker id=3] Leader -uve-topic-20-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,581] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,584] INFO [Broker id=3] Leader -uve-topic-6-24 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,586] INFO [Broker id=3] Leader -uve-topic-9-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,589] INFO [Broker id=3] Leader -uve-topic-19-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,592] INFO [Broker id=3] Leader -uve-topic-18-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,594] INFO [Broker id=3] Leader -uve-topic-22-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,597] INFO [Broker id=3] Leader -uve-topic-10-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,600] INFO [Broker id=3] Leader -uve-topic-23-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,602] INFO [Broker id=3] Leader -uve-topic-18-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,605] INFO [Broker id=3] Leader -uve-topic-17-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,608] INFO [Broker id=3] Leader -uve-topic-22-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,610] INFO [Broker id=3] Leader -uve-topic-14-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,613] INFO [Broker id=3] Leader -uve-topic-27-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,616] INFO [Broker id=3] Leader -uve-topic-5-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,619] INFO [Broker id=3] Leader -uve-topic-21-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,621] INFO [Broker id=3] Leader -uve-topic-28-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,624] INFO [Broker id=3] Leader -uve-topic-15-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,627] INFO [Broker id=3] Leader -uve-topic-16-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,629] INFO [Broker id=3] Leader -uve-topic-17-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,632] INFO [Broker id=3] Leader -uve-topic-13-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,635] INFO [Broker id=3] Leader -uve-topic-12-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,637] INFO [Broker id=3] Leader -uve-topic-25-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,640] INFO [Broker id=3] Leader -uve-topic-26-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,643] INFO [Broker id=3] Leader -uve-topic-14-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,646] INFO [Broker id=3] Leader -uve-topic-27-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,649] INFO [Broker id=3] Leader -uve-topic-7-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,652] INFO [Broker id=3] Leader -uve-topic-2-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,655] INFO [Broker id=3] Leader -uve-topic-14-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,658] INFO [Broker id=3] Leader -uve-topic-27-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,661] INFO [Broker id=3] Leader -uve-topic-28-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,664] INFO [Broker id=3] Leader -uve-topic-15-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,667] INFO [Broker id=3] Leader -uve-topic-7-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,670] INFO [Broker id=3] Leader -uve-topic-0-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,672] INFO [Broker id=3] Leader -uve-topic-1-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,675] INFO [Broker id=3] Leader -uve-topic-2-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,679] INFO [Broker id=3] Leader -uve-topic-9-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,681] INFO [Broker id=3] Leader -uve-topic-8-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,689] INFO [Broker id=3] Leader structured_syslog_topic-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,692] INFO [Broker id=3] Leader -uve-topic-1-28 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,695] INFO [Broker id=3] Leader -uve-topic-0-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,703] INFO [Broker id=3] Leader structured_syslog_topic-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,707] INFO [Broker id=3] Leader -uve-topic-4-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,710] INFO [Broker id=3] Leader -uve-topic-13-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,712] INFO [Broker id=3] Leader -uve-topic-26-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,715] INFO [Broker id=3] Leader -uve-topic-6-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,717] INFO [Broker id=3] Leader -uve-topic-8-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,719] INFO [Broker id=3] Leader -uve-topic-7-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,722] INFO [Broker id=3] Leader -uve-topic-20-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,724] INFO [Broker id=3] Leader -uve-topic-11-23 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,727] INFO [Broker id=3] Leader -uve-topic-24-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,730] INFO [Broker id=3] Leader -uve-topic-29-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,732] INFO [Broker id=3] Leader -uve-topic-16-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,735] INFO [Broker id=3] Leader -uve-topic-3-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,739] INFO [Broker id=3] Leader -uve-topic-11-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,742] INFO [Broker id=3] Leader -uve-topic-4-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,752] INFO [Broker id=3] Leader -uve-topic-5-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,755] INFO [Broker id=3] Leader -uve-topic-6-21 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,758] INFO [Broker id=3] Leader -uve-topic-2-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,761] INFO [Broker id=3] Leader -uve-topic-1-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,764] INFO [Broker id=3] Leader -uve-topic-18-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,767] INFO [Broker id=3] Leader structured_syslog_topic-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,770] INFO [Broker id=3] Leader -uve-topic-3-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,773] INFO [Broker id=3] Leader -uve-topic-2-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,776] INFO [Broker id=3] Leader -uve-topic-14-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,779] INFO [Broker id=3] Leader -uve-topic-27-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,782] INFO [Broker id=3] Leader -uve-topic-28-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,785] INFO [Broker id=3] Leader -uve-topic-15-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,788] INFO [Broker id=3] Leader -uve-topic-8-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,791] INFO [Broker id=3] Leader -uve-topic-1-25 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,793] INFO [Broker id=3] Leader -uve-topic-0-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,796] INFO [Broker id=3] Leader -uve-topic-20-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,798] INFO [Broker id=3] Leader structured_syslog_topic-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,801] INFO [Broker id=3] Leader -uve-topic-9-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,804] INFO [Broker id=3] Leader -uve-topic-22-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,806] INFO [Broker id=3] Leader -uve-topic-13-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,809] INFO [Broker id=3] Leader -uve-topic-12-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,812] INFO [Broker id=3] Leader -uve-topic-25-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,818] INFO [Broker id=3] Leader -uve-topic-26-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,822] INFO [Broker id=3] Leader -uve-topic-5-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,825] INFO [Broker id=3] Leader -uve-topic-12-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,829] INFO [Broker id=3] Leader -uve-topic-25-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,831] INFO [Broker id=3] Leader -uve-topic-13-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,834] INFO [Broker id=3] Leader -uve-topic-26-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,837] INFO [Broker id=3] Leader -uve-topic-7-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,839] INFO [Broker id=3] Leader -uve-topic-6-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,844] INFO [Broker id=3] Leader -uve-topic-28-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,849] INFO [Broker id=3] Leader -uve-topic-15-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,853] INFO [Broker id=3] Leader -uve-topic-7-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,857] INFO [Broker id=3] Leader -uve-topic-19-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,859] INFO [Broker id=3] Leader -uve-topic-10-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,862] INFO [Broker id=3] Leader -uve-topic-11-20 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,865] INFO [Broker id=3] Leader -uve-topic-24-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,867] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,870] INFO [Broker id=3] Leader -uve-topic-19-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,872] INFO [Broker id=3] Leader structured_syslog_topic-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,875] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,884] INFO [Broker id=3] Leader -uve-topic-14-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,887] INFO [Broker id=3] Leader -uve-topic-27-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,890] INFO [Broker id=3] Leader -uve-topic-10-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,892] INFO [Broker id=3] Leader -uve-topic-23-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,895] INFO [Broker id=3] Leader -uve-topic-17-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,898] INFO [Broker id=3] Leader -uve-topic-9-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,902] INFO [Broker id=3] Leader -uve-topic-14-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,904] INFO [Broker id=3] Leader -uve-topic-27-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,908] INFO [Broker id=3] Leader -uve-topic-6-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,911] INFO [Broker id=3] Leader -uve-topic-29-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,914] INFO [Broker id=3] Leader -uve-topic-16-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,916] INFO [Broker id=3] Leader -uve-topic-21-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,918] INFO [Broker id=3] Leader -uve-topic-0-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,921] INFO [Broker id=3] Leader -uve-topic-4-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,923] INFO [Broker id=3] Leader -uve-topic-8-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,926] INFO [Broker id=3] Leader -uve-topic-28-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,928] INFO [Broker id=3] Leader -uve-topic-14-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,931] INFO [Broker id=3] Leader -uve-topic-27-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,934] INFO [Broker id=3] Leader -uve-topic-29-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,936] INFO [Broker id=3] Leader -uve-topic-16-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,938] INFO [Broker id=3] Leader -uve-topic-10-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,941] INFO [Broker id=3] Leader -uve-topic-23-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,944] INFO [Broker id=3] Leader -uve-topic-12-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,947] INFO [Broker id=3] Leader -uve-topic-25-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,950] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,953] INFO [Broker id=3] Leader -uve-topic-27-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,955] INFO [Broker id=3] Leader -uve-topic-13-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,958] INFO [Broker id=3] Leader -uve-topic-26-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,984] INFO [Broker id=3] Leader -uve-topic-18-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,989] INFO [Broker id=3] Leader -uve-topic-9-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,992] INFO [Broker id=3] Leader -uve-topic-0-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,994] INFO [Broker id=3] Leader -uve-topic-1-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,997] INFO [Broker id=3] Leader -uve-topic-2-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:38,999] INFO [Broker id=3] Leader structured_syslog_topic-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,002] INFO [Broker id=3] Leader -uve-topic-6-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,005] INFO [Broker id=3] Leader -uve-topic-5-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,008] INFO [Broker id=3] Leader -uve-topic-14-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,011] INFO [Broker id=3] Leader -uve-topic-27-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,014] INFO [Broker id=3] Leader -uve-topic-5-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,016] INFO [Broker id=3] Leader -uve-topic-13-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,020] INFO [Broker id=3] Leader -uve-topic-6-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,023] INFO [Broker id=3] Leader -uve-topic-7-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,026] INFO [Broker id=3] Leader -uve-topic-8-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,029] INFO [Broker id=3] Leader -uve-topic-20-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,032] INFO [Broker id=3] Leader -uve-topic-11-17 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,035] INFO [Broker id=3] Leader -uve-topic-24-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,037] INFO [Broker id=3] Leader -uve-topic-4-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,040] INFO [Broker id=3] Leader -uve-topic-3-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,043] INFO [Broker id=3] Leader structured_syslog_topic-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,046] INFO [Broker id=3] Leader -uve-topic-5-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,048] INFO [Broker id=3] Leader -uve-topic-7-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,052] INFO [Broker id=3] Leader -uve-topic-13-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,055] INFO [Broker id=3] Leader -uve-topic-26-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,058] INFO [Broker id=3] Leader -uve-topic-6-18 starts at leader epoch 8 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,061] INFO [Broker id=3] Leader -uve-topic-3-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,065] INFO [Broker id=3] Leader -uve-topic-2-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,068] INFO [Broker id=3] Leader -uve-topic-22-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,071] INFO [Broker id=3] Leader -uve-topic-19-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,074] INFO [Broker id=3] Leader structured_syslog_topic-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,076] INFO [Broker id=3] Leader -uve-topic-14-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,079] INFO [Broker id=3] Leader -uve-topic-9-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,084] INFO [Broker id=3] Leader -uve-topic-8-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,088] INFO [Broker id=3] Leader -uve-topic-21-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,091] INFO [Broker id=3] Leader -uve-topic-28-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,095] INFO [Broker id=3] Leader -uve-topic-15-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,102] INFO [Broker id=3] Leader -uve-topic-1-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,106] INFO [Broker id=3] Leader -uve-topic-0-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,110] INFO [Broker id=3] Leader -uve-topic-17-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,113] INFO [Broker id=3] Leader structured_syslog_topic-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,116] INFO [Broker id=3] Leader -uve-topic-13-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,119] INFO [Broker id=3] Leader -uve-topic-26-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,122] INFO [Broker id=3] Leader -uve-topic-4-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,125] INFO [Broker id=3] Leader structured_syslog_topic-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,128] INFO [Broker id=3] Leader -uve-topic-28-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,131] INFO [Broker id=3] Leader -uve-topic-15-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,134] INFO [Broker id=3] Leader -uve-topic-0-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,137] INFO [Broker id=3] Leader -uve-topic-7-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,140] INFO [Broker id=3] Leader -uve-topic-20-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,146] INFO [Broker id=3] Leader -uve-topic-28-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,151] INFO [Broker id=3] Leader -uve-topic-15-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,155] INFO [Broker id=3] Leader -uve-topic-12-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,158] INFO [Broker id=3] Leader -uve-topic-25-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,162] INFO [Broker id=3] Leader -uve-topic-3-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,165] INFO [Broker id=3] Leader -uve-topic-19-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,167] INFO [Broker id=3] Leader -uve-topic-4-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,171] INFO [Broker id=3] Leader -uve-topic-11-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,174] INFO [Broker id=3] Leader -uve-topic-24-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,179] INFO [Broker id=3] Leader structured_syslog_topic-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,182] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,186] INFO [Broker id=3] Leader -uve-topic-6-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,189] INFO [Broker id=3] Leader -uve-topic-13-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,194] INFO [Broker id=3] Leader -uve-topic-26-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,198] INFO [Broker id=3] Leader -uve-topic-14-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,201] INFO [Broker id=3] Leader -uve-topic-27-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,212] INFO [Broker id=3] Leader -uve-topic-18-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,215] INFO [Broker id=3] Leader -uve-topic-22-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,218] INFO [Broker id=3] Leader -uve-topic-10-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,221] INFO [Broker id=3] Leader -uve-topic-23-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,224] INFO [Broker id=3] Leader -uve-topic-6-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,228] INFO [Broker id=3] Leader -uve-topic-20-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,231] INFO [Broker id=3] Leader -uve-topic-21-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,237] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,240] INFO [Broker id=3] Leader -uve-topic-16-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,243] INFO [Broker id=3] Leader -uve-topic-29-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,246] INFO [Broker id=3] Leader -uve-topic-21-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,249] INFO [Broker id=3] Leader -uve-topic-4-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,252] INFO [Broker id=3] Leader -uve-topic-27-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,258] INFO [Broker id=3] Leader -uve-topic-14-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,261] INFO [Broker id=3] Leader -uve-topic-16-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,264] INFO [Broker id=3] Leader -uve-topic-29-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,267] INFO [Broker id=3] Leader -uve-topic-2-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,270] INFO [Broker id=3] Leader -uve-topic-2-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,274] INFO [Broker id=3] Leader -uve-topic-1-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,277] INFO [Broker id=3] Leader -uve-topic-3-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,281] INFO [Broker id=3] Leader -uve-topic-26-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,284] INFO [Broker id=3] Leader -uve-topic-13-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,293] INFO [Broker id=3] Leader -uve-topic-5-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,296] INFO [Broker id=3] Leader -uve-topic-9-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,299] INFO [Broker id=3] Leader -uve-topic-17-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,301] INFO [Broker id=3] Leader -uve-topic-1-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,304] INFO [Broker id=3] Leader -uve-topic-8-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,306] INFO [Broker id=3] Leader structured_syslog_topic-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,310] INFO [Broker id=3] Leader -uve-topic-5-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,313] INFO [Broker id=3] Leader -uve-topic-22-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,316] INFO [Broker id=3] Leader -uve-topic-26-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,319] INFO [Broker id=3] Leader -uve-topic-13-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,322] INFO [Broker id=3] Leader -uve-topic-5-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,324] INFO [Broker id=3] Leader -uve-topic-16-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,327] INFO [Broker id=3] Leader -uve-topic-29-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,330] INFO [Broker id=3] Leader -uve-topic-15-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,333] INFO [Broker id=3] Leader -uve-topic-28-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,335] INFO [Broker id=3] Leader -uve-topic-8-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,339] INFO [Broker id=3] Leader -uve-topic-5-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,341] INFO [Broker id=3] Leader -uve-topic-4-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,345] INFO [Broker id=3] Leader -uve-topic-24-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,347] INFO [Broker id=3] Leader -uve-topic-11-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,351] INFO [Broker id=3] Leader -uve-topic-4-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,354] INFO [Broker id=3] Leader structured_syslog_topic-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,358] INFO [Broker id=3] Leader -uve-topic-5-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,361] INFO [Broker id=3] Leader -uve-topic-7-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,364] INFO [Broker id=3] Leader -uve-topic-18-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,366] INFO [Broker id=3] Leader -uve-topic-1-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,383] INFO [Broker id=3] Leader -uve-topic-3-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,386] INFO [Broker id=3] Leader -uve-topic-19-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,389] INFO [Broker id=3] Leader structured_syslog_topic-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,392] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,395] INFO [Broker id=3] Leader -uve-topic-4-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,398] INFO [Broker id=3] Leader -uve-topic-25-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,400] INFO [Broker id=3] Leader -uve-topic-26-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,403] INFO [Broker id=3] Leader -uve-topic-12-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,406] INFO [Broker id=3] Leader -uve-topic-13-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,409] INFO [Broker id=3] Leader -uve-topic-4-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,413] INFO [Broker id=3] Leader -uve-topic-0-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,416] INFO [Broker id=3] Leader -uve-topic-17-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,419] INFO [Broker id=3] Leader -uve-topic-16-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,422] INFO [Broker id=3] Leader -uve-topic-29-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,426] INFO [Broker id=3] Leader -uve-topic-2-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,431] INFO [Broker id=3] Leader -uve-topic-22-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,433] INFO [Broker id=3] Leader -uve-topic-9-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,436] INFO [Broker id=3] Leader -uve-topic-21-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,438] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,443] INFO [Broker id=3] Leader -uve-topic-17-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,446] INFO [Broker id=3] Leader -uve-topic-26-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,448] INFO [Broker id=3] Leader -uve-topic-13-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,451] INFO [Broker id=3] Leader -uve-topic-15-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,455] INFO [Broker id=3] Leader -uve-topic-28-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,457] INFO [Broker id=3] Leader -uve-topic-20-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,460] INFO [Broker id=3] Leader -uve-topic-21-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,463] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,466] INFO [Broker id=3] Leader -uve-topic-27-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,469] INFO [Broker id=3] Leader -uve-topic-14-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,471] INFO [Broker id=3] Leader -uve-topic-25-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,474] INFO [Broker id=3] Leader -uve-topic-19-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,477] INFO [Broker id=3] Leader -uve-topic-20-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,479] INFO [Broker id=3] Leader -uve-topic-10-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,482] INFO [Broker id=3] Leader -uve-topic-24-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,485] INFO [Broker id=3] Leader -uve-topic-23-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,487] INFO [Broker id=3] Leader -uve-topic-25-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,491] INFO [Broker id=3] Leader -uve-topic-12-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,494] INFO [Broker id=3] Leader -uve-topic-27-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,497] INFO [Broker id=3] Leader -uve-topic-26-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,499] INFO [Broker id=3] Leader -uve-topic-13-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,502] INFO [Broker id=3] Leader -uve-topic-14-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,507] INFO [Broker id=3] Leader -uve-topic-6-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,510] INFO [Broker id=3] Leader -uve-topic-10-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,513] INFO [Broker id=3] Leader -uve-topic-22-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,517] INFO [Broker id=3] Leader -uve-topic-23-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,520] INFO [Broker id=3] Leader -uve-topic-18-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,524] INFO [Broker id=3] Leader -uve-topic-5-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,530] INFO [Broker id=3] Leader -uve-topic-25-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,532] INFO [Broker id=3] Leader -uve-topic-12-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,535] INFO [Broker id=3] Leader -uve-topic-18-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,538] INFO [Broker id=3] Leader -uve-topic-17-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,541] INFO [Broker id=3] Leader -uve-topic-20-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,544] INFO [Broker id=3] Leader -uve-topic-21-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,546] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,549] INFO [Broker id=3] Leader -uve-topic-22-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,552] INFO [Broker id=3] Leader -uve-topic-17-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,555] INFO [Broker id=3] Leader -uve-topic-16-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,558] INFO [Broker id=3] Leader -uve-topic-29-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,560] INFO [Broker id=3] Leader -uve-topic-21-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,563] INFO [Broker id=3] Leader structured_syslog_topic-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,566] INFO [Broker id=3] Leader -uve-topic-20-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,569] INFO [Broker id=3] Leader -uve-topic-27-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,572] INFO [Broker id=3] Leader -uve-topic-14-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,575] INFO [Broker id=3] Leader -uve-topic-16-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,578] INFO [Broker id=3] Leader -uve-topic-15-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,581] INFO [Broker id=3] Leader -uve-topic-29-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,584] INFO [Broker id=3] Leader -uve-topic-28-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,586] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,590] INFO [Broker id=3] Leader -uve-topic-25-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,593] INFO [Broker id=3] Leader -uve-topic-12-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,597] INFO [Broker id=3] Leader -uve-topic-24-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,601] INFO [Broker id=3] Leader -uve-topic-11-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,605] INFO [Broker id=3] Leader -uve-topic-26-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,608] INFO [Broker id=3] Leader -uve-topic-13-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,613] INFO [Broker id=3] Leader -uve-topic-12-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,616] INFO [Broker id=3] Leader -uve-topic-13-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,620] INFO [Broker id=3] Leader -uve-topic-5-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,623] INFO [Broker id=3] Leader -uve-topic-6-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,626] INFO [Broker id=3] Leader -uve-topic-9-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,630] INFO [Broker id=3] Leader -uve-topic-1-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,633] INFO [Broker id=3] Leader -uve-topic-8-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,637] INFO [Broker id=3] Leader -uve-topic-15-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,642] INFO [Broker id=3] Leader -uve-topic-28-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,646] INFO [Broker id=3] Leader -uve-topic-0-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,649] INFO [Broker id=3] Leader -uve-topic-7-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,652] INFO [Broker id=3] Leader -uve-topic-4-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,656] INFO [Broker id=3] Leader -uve-topic-3-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,659] INFO [Broker id=3] Leader -uve-topic-25-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,662] INFO [Broker id=3] Leader -uve-topic-12-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,665] INFO [Broker id=3] Leader -uve-topic-19-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,667] INFO [Broker id=3] Leader structured_syslog_topic-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,671] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,674] INFO [Broker id=3] Leader -uve-topic-7-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,677] INFO [Broker id=3] Leader -uve-topic-6-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,681] INFO [Broker id=3] Leader -uve-topic-10-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,685] INFO [Broker id=3] Leader -uve-topic-27-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,695] INFO [Broker id=3] Leader -uve-topic-23-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,704] INFO [Broker id=3] Leader -uve-topic-14-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,709] INFO [Broker id=3] Leader -uve-topic-2-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,713] INFO [Broker id=3] Leader -uve-topic-18-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,716] INFO [Broker id=3] Leader -uve-topic-19-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,720] INFO [Broker id=3] Leader -uve-topic-22-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,723] INFO [Broker id=3] Leader -uve-topic-24-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,725] INFO [Broker id=3] Leader -uve-topic-11-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,728] INFO [Broker id=3] Leader -uve-topic-10-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,731] INFO [Broker id=3] Leader -uve-topic-23-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,733] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,736] INFO [Broker id=3] Leader -uve-topic-4-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,739] INFO [Broker id=3] Leader -uve-topic-25-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,742] INFO [Broker id=3] Leader -uve-topic-12-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,745] INFO [Broker id=3] Leader -uve-topic-5-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,748] INFO [Broker id=3] Leader -uve-topic-4-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,752] INFO [Broker id=3] Leader -uve-topic-17-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,755] INFO [Broker id=3] Leader -uve-topic-0-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,758] INFO [Broker id=3] Leader -uve-topic-1-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,763] INFO [Broker id=3] Leader -uve-topic-16-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,769] INFO [Broker id=3] Leader -uve-topic-2-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,775] INFO [Broker id=3] Leader -uve-topic-9-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,778] INFO [Broker id=3] Leader -uve-topic-25-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,781] INFO [Broker id=3] Leader -uve-topic-12-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,784] INFO [Broker id=3] Leader -uve-topic-4-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,786] INFO [Broker id=3] Leader -uve-topic-3-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,789] INFO [Broker id=3] Leader -uve-topic-3-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,793] INFO [Broker id=3] Leader -uve-topic-0-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,795] INFO [Broker id=3] Leader -uve-topic-15-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,798] INFO [Broker id=3] Leader -uve-topic-6-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,801] INFO [Broker id=3] Leader -uve-topic-7-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,804] INFO [Broker id=3] Leader -uve-topic-8-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,807] INFO [Broker id=3] Leader -uve-topic-21-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,811] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,815] INFO [Broker id=3] Leader -uve-topic-25-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,817] INFO [Broker id=3] Leader -uve-topic-12-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,821] INFO [Broker id=3] Leader -uve-topic-19-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,825] INFO [Broker id=3] Leader -uve-topic-24-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,828] INFO [Broker id=3] Leader -uve-topic-11-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,830] INFO [Broker id=3] Leader -uve-topic-4-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,834] INFO [Broker id=3] Leader -uve-topic-24-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,837] INFO [Broker id=3] Leader -uve-topic-11-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,840] INFO [Broker id=3] Leader -uve-topic-5-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,843] INFO [Broker id=3] Leader -uve-topic-6-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,847] INFO [Broker id=3] Leader -uve-topic-27-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,850] INFO [Broker id=3] Leader -uve-topic-14-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,853] INFO [Broker id=3] Leader -uve-topic-18-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,856] INFO [Broker id=3] Leader -uve-topic-19-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,858] INFO [Broker id=3] Leader -uve-topic-10-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,862] INFO [Broker id=3] Leader -uve-topic-22-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,865] INFO [Broker id=3] Leader -uve-topic-23-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,869] INFO [Broker id=3] Leader -uve-topic-18-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,872] INFO [Broker id=3] Leader -uve-topic-24-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,875] INFO [Broker id=3] Leader -uve-topic-11-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,877] INFO [Broker id=3] Leader -uve-topic-26-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,882] INFO [Broker id=3] Leader -uve-topic-13-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,885] INFO [Broker id=3] Leader -uve-topic-25-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,888] INFO [Broker id=3] Leader -uve-topic-20-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,891] INFO [Broker id=3] Leader -uve-topic-12-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,894] INFO [Broker id=3] Leader -uve-topic-22-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,896] INFO [Broker id=3] Leader -uve-topic-16-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,904] INFO [Broker id=3] Leader -uve-topic-29-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,907] INFO [Broker id=3] Leader -uve-topic-21-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,911] INFO [Broker id=3] Leader -uve-topic-8-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,914] INFO [Broker id=3] Leader -uve-topic-17-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,917] INFO [Broker id=3] Leader -uve-topic-15-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,919] INFO [Broker id=3] Leader -uve-topic-28-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,922] INFO [Broker id=3] Leader -uve-topic-7-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,925] INFO [Broker id=3] Leader -uve-topic-10-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,929] INFO [Broker id=3] Leader -uve-topic-23-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,932] INFO [Broker id=3] Leader -uve-topic-1-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,935] INFO [Broker id=3] Leader -uve-topic-3-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,938] INFO [Broker id=3] Leader structured_syslog_topic-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,942] INFO [Broker id=3] Leader -uve-topic-5-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,945] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,947] INFO [Broker id=3] Leader -uve-topic-4-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,950] INFO [Broker id=3] Leader -uve-topic-9-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,953] INFO [Broker id=3] Leader -uve-topic-9-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,956] INFO [Broker id=3] Leader -uve-topic-19-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,959] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,962] INFO [Broker id=3] Leader -uve-topic-17-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,965] INFO [Broker id=3] Leader -uve-topic-8-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,968] INFO [Broker id=3] Leader -uve-topic-1-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,971] INFO [Broker id=3] Leader -uve-topic-0-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,974] INFO [Broker id=3] Leader -uve-topic-24-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,977] INFO [Broker id=3] Leader -uve-topic-5-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,981] INFO [Broker id=3] Leader -uve-topic-7-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,984] INFO [Broker id=3] Leader -uve-topic-6-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,987] INFO [Broker id=3] Leader -uve-topic-23-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,991] INFO [Broker id=3] Leader -uve-topic-10-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,994] INFO [Broker id=3] Leader -uve-topic-3-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:39,997] INFO [Broker id=3] Leader -uve-topic-2-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,005] INFO [Broker id=3] Leader -uve-topic-18-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,010] INFO [Broker id=3] Leader -uve-topic-19-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,013] INFO [Broker id=3] Leader -uve-topic-4-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,016] INFO [Broker id=3] Leader -uve-topic-5-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,019] INFO [Broker id=3] Leader -uve-topic-6-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,023] INFO [Broker id=3] Leader -uve-topic-25-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,025] INFO [Broker id=3] Leader -uve-topic-12-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,028] INFO [Broker id=3] Leader -uve-topic-0-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,032] INFO [Broker id=3] Leader -uve-topic-4-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,036] INFO [Broker id=3] Leader -uve-topic-2-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,038] INFO [Broker id=3] Leader -uve-topic-18-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,041] INFO [Broker id=3] Leader -uve-topic-1-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,044] INFO [Broker id=3] Leader -uve-topic-9-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,046] INFO [Broker id=3] Leader -uve-topic-21-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,049] INFO [Broker id=3] Leader -uve-topic-3-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,056] INFO [Broker id=3] Leader -uve-topic-23-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,060] INFO [Broker id=3] Leader -uve-topic-24-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,064] INFO [Broker id=3] Leader -uve-topic-11-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,068] INFO [Broker id=3] Leader -uve-topic-15-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,075] INFO [Broker id=3] Leader -uve-topic-3-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,078] INFO [Broker id=3] Leader -uve-topic-28-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,081] INFO [Broker id=3] Leader -uve-topic-8-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,084] INFO [Broker id=3] Leader -uve-topic-20-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,087] INFO [Broker id=3] Leader -uve-topic-7-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,090] INFO [Broker id=3] Leader -uve-topic-27-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,096] INFO [Broker id=3] Leader -uve-topic-14-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,099] INFO [Broker id=3] Leader -uve-topic-16-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,102] INFO [Broker id=3] Leader -uve-topic-29-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,104] INFO [Broker id=3] Leader -uve-topic-24-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,107] INFO [Broker id=3] Leader -uve-topic-11-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,109] INFO [Broker id=3] Leader -uve-topic-19-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,115] INFO [Broker id=3] Leader -uve-topic-24-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,118] INFO [Broker id=3] Leader -uve-topic-11-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,121] INFO [Broker id=3] Leader -uve-topic-3-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,124] INFO [Broker id=3] Leader structured_syslog_topic-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,136] INFO [Broker id=3] Leader -uve-topic-26-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,141] INFO [Broker id=3] Leader -uve-topic-13-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,165] INFO [Broker id=3] Leader -uve-topic-22-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,169] INFO [Broker id=3] Leader -uve-topic-10-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,173] INFO [Broker id=3] Leader structured_syslog_topic-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,176] INFO [Broker id=3] Leader -uve-topic-5-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,179] INFO [Broker id=3] Leader -uve-topic-25-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,182] INFO [Broker id=3] Leader -uve-topic-12-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,185] INFO [Broker id=3] Leader -uve-topic-24-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,188] INFO [Broker id=3] Leader -uve-topic-11-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,191] INFO [Broker id=3] Leader -uve-topic-26-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,195] INFO [Broker id=3] Leader -uve-topic-13-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,198] INFO [Broker id=3] Leader -uve-topic-17-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,201] INFO [Broker id=3] Leader -uve-topic-20-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,206] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,211] INFO [Broker id=3] Leader -uve-topic-22-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,214] INFO [Broker id=3] Leader -uve-topic-9-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,216] INFO [Broker id=3] Leader -uve-topic-19-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,219] INFO [Broker id=3] Leader -uve-topic-18-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,222] INFO [Broker id=3] Leader -uve-topic-24-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,225] INFO [Broker id=3] Leader -uve-topic-23-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,228] INFO [Broker id=3] Leader -uve-topic-11-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,230] INFO [Broker id=3] Leader -uve-topic-10-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,233] INFO [Broker id=3] Leader -uve-topic-3-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,236] INFO [Broker id=3] Leader -uve-topic-19-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,241] INFO [Broker id=3] Leader -uve-topic-23-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,245] INFO [Broker id=3] Leader -uve-topic-10-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,249] INFO [Broker id=3] Leader -uve-topic-15-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,254] INFO [Broker id=3] Leader -uve-topic-28-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,256] INFO [Broker id=3] Leader -uve-topic-21-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,258] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,261] INFO [Broker id=3] Leader -uve-topic-6-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,268] INFO [Broker id=3] Leader -uve-topic-19-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,276] INFO [Broker id=3] Leader -uve-topic-3-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,279] INFO [Broker id=3] Leader -uve-topic-26-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,282] INFO [Broker id=3] Leader -uve-topic-1-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,284] INFO [Broker id=3] Leader -uve-topic-9-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,287] INFO [Broker id=3] Leader -uve-topic-0-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,291] INFO [Broker id=3] Leader -uve-topic-1-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,294] INFO [Broker id=3] Leader -uve-topic-2-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,297] INFO [Broker id=3] Leader -uve-topic-25-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,301] INFO [Broker id=3] Leader -uve-topic-12-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,304] INFO [Broker id=3] Leader -uve-topic-4-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,306] INFO [Broker id=3] Leader -uve-topic-8-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,314] INFO [Broker id=3] Leader -uve-topic-0-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,317] INFO [Broker id=3] Leader -uve-topic-16-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,320] INFO [Broker id=3] Leader -uve-topic-29-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,324] INFO [Broker id=3] Leader -uve-topic-7-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,329] INFO [Broker id=3] Leader -uve-topic-8-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,332] INFO [Broker id=3] Leader -uve-topic-2-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,335] INFO [Broker id=3] Leader -uve-topic-27-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,338] INFO [Broker id=3] Leader -uve-topic-6-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,341] INFO [Broker id=3] Leader -uve-topic-7-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,345] INFO [Broker id=3] Leader -uve-topic-27-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,348] INFO [Broker id=3] Leader -uve-topic-14-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,351] INFO [Broker id=3] Leader -uve-topic-2-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,354] INFO [Broker id=3] Leader -uve-topic-24-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,356] INFO [Broker id=3] Leader -uve-topic-11-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,370] INFO [Broker id=3] Leader -uve-topic-18-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,373] INFO [Broker id=3] Leader -uve-topic-3-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,375] INFO [Broker id=3] Leader -uve-topic-23-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,378] INFO [Broker id=3] Leader -uve-topic-10-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,381] INFO [Broker id=3] Leader -uve-topic-4-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,384] INFO [Broker id=3] Leader -uve-topic-1-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,388] INFO [Broker id=3] Leader -uve-topic-6-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,527] INFO [Broker id=3] Leader -uve-topic-0-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,530] INFO [Broker id=3] Leader -uve-topic-9-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,534] INFO [Broker id=3] Leader -uve-topic-16-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,540] INFO [Broker id=3] Leader -uve-topic-29-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,543] INFO [Broker id=3] Leader -uve-topic-2-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,546] INFO [Broker id=3] Leader -uve-topic-1-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,549] INFO [Broker id=3] Leader -uve-topic-18-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,553] INFO [Broker id=3] Leader -uve-topic-3-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,556] INFO [Broker id=3] Leader -uve-topic-19-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,559] INFO [Broker id=3] Leader -uve-topic-25-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,562] INFO [Broker id=3] Leader -uve-topic-12-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,564] INFO [Broker id=3] Leader -uve-topic-24-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,567] INFO [Broker id=3] Leader -uve-topic-11-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,569] INFO [Broker id=3] Leader -uve-topic-15-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,572] INFO [Broker id=3] Leader -uve-topic-29-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,575] INFO [Broker id=3] Leader -uve-topic-28-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,579] INFO [Broker id=3] Leader -uve-topic-8-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,582] INFO [Broker id=3] Leader -uve-topic-20-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,585] INFO [Broker id=3] Leader -uve-topic-21-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,587] INFO [Broker id=3] Leader -uve-topic-18-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,590] INFO [Broker id=3] Leader structured_syslog_topic-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,592] INFO [Broker id=3] Leader -uve-topic-5-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,595] INFO [Broker id=3] Leader -uve-topic-27-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,598] INFO [Broker id=3] Leader -uve-topic-14-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,600] INFO [Broker id=3] Leader -uve-topic-7-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,602] INFO [Broker id=3] Leader -uve-topic-20-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,606] INFO [Broker id=3] Leader -uve-topic-27-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,610] INFO [Broker id=3] Leader -uve-topic-26-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,612] INFO [Broker id=3] Leader -uve-topic-13-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,615] INFO [Broker id=3] Leader -uve-topic-14-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,618] INFO [Broker id=3] Leader -uve-topic-23-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,620] INFO [Broker id=3] Leader -uve-topic-10-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,623] INFO [Broker id=3] Leader -uve-topic-19-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,625] INFO [Broker id=3] Leader -uve-topic-22-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,628] INFO [Broker id=3] Leader structured_syslog_topic-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,630] INFO [Broker id=3] Leader -uve-topic-24-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,633] INFO [Broker id=3] Leader -uve-topic-11-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,636] INFO [Broker id=3] Leader -uve-topic-26-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,639] INFO [Broker id=3] Leader -uve-topic-25-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,642] INFO [Broker id=3] Leader -uve-topic-12-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,645] INFO [Broker id=3] Leader -uve-topic-13-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,649] INFO [Broker id=3] Leader -uve-topic-21-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,652] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,655] INFO [Broker id=3] Leader -uve-topic-17-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,657] INFO [Broker id=3] Leader -uve-topic-9-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,660] INFO [Broker id=3] Leader -uve-topic-23-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,663] INFO [Broker id=3] Leader -uve-topic-0-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,666] INFO [Broker id=3] Leader -uve-topic-10-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,670] INFO [Broker id=3] Leader -uve-topic-18-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,673] INFO [Broker id=3] Leader -uve-topic-19-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,676] INFO [Broker id=3] Leader -uve-topic-23-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,682] INFO [Broker id=3] Leader -uve-topic-10-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,685] INFO [Broker id=3] Leader -uve-topic-2-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,688] INFO [Broker id=3] Leader -uve-topic-28-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,692] INFO [Broker id=3] Leader -uve-topic-15-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,695] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,698] INFO [Broker id=3] Leader -uve-topic-2-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,703] INFO [Broker id=3] Leader -uve-topic-13-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,708] INFO [Broker id=3] Leader -uve-topic-26-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,711] INFO [Broker id=3] Leader -uve-topic-12-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,714] INFO [Broker id=3] Leader -uve-topic-25-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,719] INFO [Broker id=3] Leader -uve-topic-14-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,723] INFO [Broker id=3] Leader -uve-topic-27-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,726] INFO [Broker id=3] Leader -uve-topic-10-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,728] INFO [Broker id=3] Leader -uve-topic-23-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,731] INFO [Broker id=3] Leader -uve-topic-12-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,735] INFO [Broker id=3] Leader -uve-topic-25-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,738] INFO [Broker id=3] Leader -uve-topic-11-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,741] INFO [Broker id=3] Leader -uve-topic-24-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,744] INFO [Broker id=3] Leader -uve-topic-4-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,746] INFO [Broker id=3] Leader -uve-topic-8-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,749] INFO [Broker id=3] Leader -uve-topic-0-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,751] INFO [Broker id=3] Leader -uve-topic-18-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,754] INFO [Broker id=3] Leader -uve-topic-2-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,757] INFO [Broker id=3] Leader -uve-topic-1-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,759] INFO [Broker id=3] Leader structured_syslog_topic-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,765] INFO [Broker id=3] Leader -uve-topic-7-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,769] INFO [Broker id=3] Leader -uve-topic-14-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,775] INFO [Broker id=3] Leader -uve-topic-27-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,779] INFO [Broker id=3] Leader -uve-topic-6-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,783] INFO [Broker id=3] Leader -uve-topic-2-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,785] INFO [Broker id=3] Leader -uve-topic-18-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,788] INFO [Broker id=3] Leader -uve-topic-5-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,790] INFO [Broker id=3] Leader -uve-topic-9-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,793] INFO [Broker id=3] Leader -uve-topic-22-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,796] INFO [Broker id=3] Leader -uve-topic-13-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,798] INFO [Broker id=3] Leader -uve-topic-26-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,801] INFO [Broker id=3] Leader -uve-topic-1-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,803] INFO [Broker id=3] Leader -uve-topic-17-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,806] INFO [Broker id=3] Leader -uve-topic-18-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,809] INFO [Broker id=3] Leader -uve-topic-21-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,811] INFO [Broker id=3] Leader -uve-topic-20-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,814] INFO [Broker id=3] Leader -uve-topic-22-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,817] INFO [Broker id=3] Leader -uve-topic-3-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,820] INFO [Broker id=3] Leader -uve-topic-19-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,822] INFO [Broker id=3] Leader -uve-topic-10-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,825] INFO [Broker id=3] Leader -uve-topic-11-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,828] INFO [Broker id=3] Leader -uve-topic-23-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,832] INFO [Broker id=3] Leader -uve-topic-24-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,835] INFO [Broker id=3] Leader -uve-topic-28-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,837] INFO [Broker id=3] Leader -uve-topic-3-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,840] INFO [Broker id=3] Leader -uve-topic-15-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,843] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,846] INFO [Broker id=3] Leader -uve-topic-19-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,848] INFO [Broker id=3] Leader -uve-topic-17-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,853] INFO [Broker id=3] Leader -uve-topic-20-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,855] INFO [Broker id=3] Leader -uve-topic-29-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,858] INFO [Broker id=3] Leader -uve-topic-16-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,861] INFO [Broker id=3] Leader -uve-topic-21-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,863] INFO [Broker id=3] Leader -uve-topic-28-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,866] INFO [Broker id=3] Leader -uve-topic-29-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,869] INFO [Broker id=3] Leader -uve-topic-15-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,878] INFO [Broker id=3] Leader -uve-topic-16-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,882] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,886] INFO [Broker id=3] Leader -uve-topic-9-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,888] INFO [Broker id=3] Leader -uve-topic-1-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,892] INFO [Broker id=3] Leader -uve-topic-23-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,895] INFO [Broker id=3] Leader -uve-topic-10-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,898] INFO [Broker id=3] Leader structured_syslog_topic-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,902] INFO [Broker id=3] Leader -uve-topic-2-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,907] INFO [Broker id=3] Leader -uve-topic-22-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,910] INFO [Broker id=3] Leader -uve-topic-18-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,912] INFO [Broker id=3] Leader -uve-topic-6-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,915] INFO [Broker id=3] Leader -uve-topic-5-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,917] INFO [Broker id=3] Leader -uve-topic-14-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,920] INFO [Broker id=3] Leader -uve-topic-27-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,923] INFO [Broker id=3] Leader -uve-topic-7-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,926] INFO [Broker id=3] Leader -uve-topic-20-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,929] INFO [Broker id=3] Leader -uve-topic-0-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,931] INFO [Broker id=3] Leader -uve-topic-9-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,934] INFO [Broker id=3] Leader -uve-topic-1-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,937] INFO [Broker id=3] Leader -uve-topic-17-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,940] INFO [Broker id=3] Leader structured_syslog_topic-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,943] INFO [Broker id=3] Leader -uve-topic-5-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,947] INFO [Broker id=3] Leader -uve-topic-4-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,949] INFO [Broker id=3] Leader -uve-topic-11-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,952] INFO [Broker id=3] Leader -uve-topic-24-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,955] INFO [Broker id=3] Leader -uve-topic-13-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,958] INFO [Broker id=3] Leader -uve-topic-12-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,960] INFO [Broker id=3] Leader -uve-topic-26-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,963] INFO [Broker id=3] Leader -uve-topic-29-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,965] INFO [Broker id=3] Leader -uve-topic-16-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,968] INFO [Broker id=3] Leader -uve-topic-17-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,974] INFO [Broker id=3] Leader -uve-topic-22-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,976] INFO [Broker id=3] Leader -uve-topic-18-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,980] INFO [Broker id=3] Leader -uve-topic-21-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,983] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,986] INFO [Broker id=3] Leader -uve-topic-17-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,988] INFO [Broker id=3] Leader -uve-topic-23-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,991] INFO [Broker id=3] Leader -uve-topic-10-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,994] INFO [Broker id=3] Leader -uve-topic-12-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,997] INFO [Broker id=3] Leader -uve-topic-25-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:40,999] INFO [Broker id=3] Leader -uve-topic-11-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,002] INFO [Broker id=3] Leader -uve-topic-19-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,005] INFO [Broker id=3] Leader -uve-topic-21-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,007] INFO [Broker id=3] Leader -uve-topic-20-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,010] INFO [Broker id=3] Leader -uve-topic-28-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,012] INFO [Broker id=3] Leader -uve-topic-15-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,015] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,018] INFO [Broker id=3] Leader -uve-topic-22-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,022] INFO [Broker id=3] Leader -uve-topic-18-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,024] INFO [Broker id=3] Leader -uve-topic-14-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,028] INFO [Broker id=3] Leader -uve-topic-13-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,031] INFO [Broker id=3] Leader -uve-topic-26-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,033] INFO [Broker id=3] Leader -uve-topic-27-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,036] INFO [Broker id=3] Leader -uve-topic-6-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,038] INFO [Broker id=3] Leader -uve-topic-1-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,045] INFO [Broker id=3] Leader -uve-topic-0-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,049] INFO [Broker id=3] Leader -uve-topic-22-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,054] INFO [Broker id=3] Leader -uve-topic-4-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,056] INFO [Broker id=3] Leader -uve-topic-3-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,059] INFO [Broker id=3] Leader -uve-topic-9-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,062] INFO [Broker id=3] Leader -uve-topic-28-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,065] INFO [Broker id=3] Leader -uve-topic-29-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,068] INFO [Broker id=3] Leader -uve-topic-15-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,070] INFO [Broker id=3] Leader -uve-topic-16-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,073] INFO [Broker id=3] Leader -uve-topic-8-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,075] INFO [Broker id=3] Leader -uve-topic-2-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,078] INFO [Broker id=3] Leader -uve-topic-3-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,080] INFO [Broker id=3] Leader -uve-topic-9-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,083] INFO [Broker id=3] Leader -uve-topic-2-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,085] INFO [Broker id=3] Leader -uve-topic-1-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,088] INFO [Broker id=3] Leader structured_syslog_topic-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,091] INFO [Broker id=3] Leader -uve-topic-22-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,095] INFO [Broker id=3] Leader -uve-topic-1-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,101] INFO [Broker id=3] Leader -uve-topic-0-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,105] INFO [Broker id=3] Leader -uve-topic-9-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,108] INFO [Broker id=3] Leader -uve-topic-4-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,110] INFO [Broker id=3] Leader -uve-topic-6-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,113] INFO [Broker id=3] Leader -uve-topic-5-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,115] INFO [Broker id=3] Leader -uve-topic-9-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,118] INFO [Broker id=3] Leader -uve-topic-22-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,121] INFO [Broker id=3] Leader -uve-topic-1-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,128] INFO [Broker id=3] Leader -uve-topic-17-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,131] INFO [Broker id=3] Leader -uve-topic-3-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,133] INFO [Broker id=3] Leader -uve-topic-19-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,136] INFO [Broker id=3] Leader -uve-topic-4-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,139] INFO [Broker id=3] Leader -uve-topic-5-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,141] INFO [Broker id=3] Leader -uve-topic-20-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,148] INFO [Broker id=3] Leader -uve-topic-28-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,151] INFO [Broker id=3] Leader -uve-topic-3-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,154] INFO [Broker id=3] Leader -uve-topic-15-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,157] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,160] INFO [Broker id=3] Leader -uve-topic-8-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,163] INFO [Broker id=3] Leader -uve-topic-0-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,166] INFO [Broker id=3] Leader -uve-topic-17-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,169] INFO [Broker id=3] Leader -uve-topic-20-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,171] INFO [Broker id=3] Leader -uve-topic-29-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,174] INFO [Broker id=3] Leader -uve-topic-16-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,176] INFO [Broker id=3] Leader -uve-topic-21-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,180] INFO [Broker id=3] Leader -uve-topic-2-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,183] INFO [Broker id=3] Leader -uve-topic-9-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,186] INFO [Broker id=3] Leader -uve-topic-1-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,189] INFO [Broker id=3] Leader -uve-topic-23-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,195] INFO [Broker id=3] Leader -uve-topic-10-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,199] INFO [Broker id=3] Leader -uve-topic-17-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,202] INFO [Broker id=3] Leader structured_syslog_topic-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,205] INFO [Broker id=3] Leader -uve-topic-2-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,209] INFO [Broker id=3] Leader -uve-topic-14-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,211] INFO [Broker id=3] Leader -uve-topic-27-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,214] INFO [Broker id=3] Leader -uve-topic-7-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,217] INFO [Broker id=3] Leader -uve-topic-6-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,220] INFO [Broker id=3] Leader -uve-topic-13-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,222] INFO [Broker id=3] Leader -uve-topic-26-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,225] INFO [Broker id=3] Leader -uve-topic-14-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,228] INFO [Broker id=3] Leader -uve-topic-8-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,233] INFO [Broker id=3] Leader -uve-topic-0-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,236] INFO [Broker id=3] Leader -uve-topic-21-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,239] INFO [Broker id=3] Leader -uve-topic-12-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,243] INFO [Broker id=3] Leader -uve-topic-25-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,246] INFO [Broker id=3] Leader -uve-topic-21-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,249] INFO [Broker id=3] Leader -uve-topic-0-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,252] INFO [Broker id=3] Leader -uve-topic-22-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,255] INFO [Broker id=3] Leader -uve-topic-9-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,258] INFO [Broker id=3] Leader -uve-topic-8-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,261] INFO [Broker id=3] Leader -uve-topic-29-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,263] INFO [Broker id=3] Leader -uve-topic-11-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,266] INFO [Broker id=3] Leader -uve-topic-24-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,269] INFO [Broker id=3] Leader -uve-topic-18-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,272] INFO [Broker id=3] Leader -uve-topic-29-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,274] INFO [Broker id=3] Leader -uve-topic-15-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,277] INFO [Broker id=3] Leader -uve-topic-16-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,280] INFO [Broker id=3] Leader -uve-topic-7-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-01-27 02:11:41,297] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 4 (state.change.logger)
[2025-01-27 02:11:41,302] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 6 (state.change.logger)
[2025-01-27 02:11:54,648] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 7 (state.change.logger)
[2025-01-27 02:16:38,928] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 8 from controller 2 for 320 partitions (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-22-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-18-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-17-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-29-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-2-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-16-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-11-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-0-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-1-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-7-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-6-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-9-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-5-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-23-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-4-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-12-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-25-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-29-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-2-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-9-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-18-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-23-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-7-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,931] INFO [Broker id=3] Follower -uve-topic-17-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-4-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-29-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-6-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-26-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-25-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-12-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-16-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-10-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-19-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-11-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-29-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-22-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-1-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-5-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-7-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-0-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-23-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-7-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-17-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-29-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-9-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-6-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-26-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-13-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-5-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-4-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-19-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-12-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-25-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-29-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-1-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-2-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-22-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-10-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-27-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-18-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-8-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-16-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-11-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-7-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-10-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,932] INFO [Broker id=3] Follower -uve-topic-11-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-9-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-19-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-18-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-23-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-22-0 starts at leader epoch 8 from offset 287 with high watermark 287. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-27-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-5-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-17-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-13-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-12-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-25-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-26-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-27-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-2-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-7-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-1-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-6-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-4-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-8-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-7-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-16-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-11-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-3-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-4-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-1-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-2-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-27-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-8-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-9-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-25-0 starts at leader epoch 8 from offset 34 with high watermark 34. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-26-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-12-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-13-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-5-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-6-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-19-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-7-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-27-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-17-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-10-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-6-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-16-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-28-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-16-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,933] INFO [Broker id=3] Follower -uve-topic-27-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-10-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-9-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-1-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-5-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-27-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-6-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-7-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-8-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-26-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-13-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-19-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-2-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-3-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower structured_syslog_topic-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-17-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-4-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-26-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-13-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-15-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-28-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-20-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-19-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-3-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-4-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower structured_syslog_topic-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-27-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-10-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-6-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-21-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-16-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-14-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-2-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-1-0 starts at leader epoch 8 from offset 77 with high watermark 77. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-26-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-13-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-17-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-8-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-26-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-13-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,934] INFO [Broker id=3] Follower -uve-topic-5-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-8-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-4-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-19-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-3-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower structured_syslog_topic-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-16-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-17-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-26-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-13-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-15-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-28-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-27-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-21-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-20-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-10-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-24-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-14-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-26-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-13-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-5-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-17-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-21-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-16-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,935] INFO [Broker id=3] Follower -uve-topic-14-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-20-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-13-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-8-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-15-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-28-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-3-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-19-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower structured_syslog_topic-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-27-0 starts at leader epoch 8 from offset 80 with high watermark 80. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-24-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-10-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,939] INFO [Broker id=3] Follower -uve-topic-16-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-3-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-0-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-8-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-21-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-24-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-14-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-19-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-24-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-20-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-17-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-28-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-15-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-3-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-10-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower structured_syslog_topic-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,940] INFO [Broker id=3] Follower -uve-topic-8-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-0-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-21-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-23-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-24-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-3-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-28-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-15-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-20-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-14-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-24-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-19-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-3-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower structured_syslog_topic-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-10-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower structured_syslog_topic-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-12-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-25-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-24-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-20-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-11-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-18-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-23-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-21-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-28-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-15-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-0-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-8-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-14-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-24-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-3-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-0-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-12-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-25-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-29-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-24-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-28-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-15-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-20-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower structured_syslog_topic-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-18-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,941] INFO [Broker id=3] Follower -uve-topic-14-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-11-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-21-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-23-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-14-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-12-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-25-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-24-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-0-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-18-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-2-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower structured_syslog_topic-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-22-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-18-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-20-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-11-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-21-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-29-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-28-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-15-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-9-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-1-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-23-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-22-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-14-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-6-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-9-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-1-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-11-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-5-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-22-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-21-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-23-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-12-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-25-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-20-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-22-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-18-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-0-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-4-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-29-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-28-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-15-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-2-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower structured_syslog_topic-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-22-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-1-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-0-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-4-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-6-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-22-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-5-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-20-0 starts at leader epoch 8 from offset 188 with high watermark 188. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-0-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-21-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-2-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-9-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-23-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-7-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-14-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-12-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-25-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-9-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-11-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,942] INFO [Broker id=3] Follower -uve-topic-18-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,943] INFO [Broker id=3] Follower -uve-topic-29-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,943] INFO [Broker id=3] Follower -uve-topic-15-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-01-27 02:16:38,944] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 8 for 320 partitions (state.change.logger)
[2025-01-27 02:16:39,007] INFO [Broker id=3] Add 320 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 9 (state.change.logger)
[2025-01-27 02:16:39,135] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 10 from controller 2 for 320 partitions (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-16-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-27-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-5-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-17-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-21-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-26-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-13-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-8-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-9-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-20-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-2-0 starts at leader epoch 7 from offset 80 with high watermark 80. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-3-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-6-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-7-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-4-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-17-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-8-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-10-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-19-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-16-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-10-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-27-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-6-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-8-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-21-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-16-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-26-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-13-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-5-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-19-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,136] INFO [Broker id=3] Follower -uve-topic-16-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-7-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-8-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-17-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-24-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-15-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-28-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-20-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-3-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-10-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-24-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-19-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-20-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-3-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-16-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower structured_syslog_topic-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-8-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-16-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-14-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-28-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-27-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-21-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-17-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-13-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-26-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-28-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-15-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-20-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-3-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-19-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-10-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-17-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-14-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-21-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-28-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-15-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-16-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-14-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-27-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-28-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-15-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-0-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-8-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower structured_syslog_topic-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-13-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-26-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-20-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-24-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-3-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-14-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower structured_syslog_topic-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-20-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-13-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-26-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-28-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-15-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-24-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-10-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-19-0 starts at leader epoch 7 from offset 14 with high watermark 14. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower structured_syslog_topic-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-14-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-27-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-21-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-0-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-8-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-14-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-0-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-14-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-13-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,137] INFO [Broker id=3] Follower -uve-topic-20-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-24-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-3-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower structured_syslog_topic-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-15-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-28-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-21-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-8-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower structured_syslog_topic-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower structured_syslog_topic-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-0-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-15-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-28-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-24-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-14-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-22-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-20-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-21-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-29-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-3-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower structured_syslog_topic-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-15-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-29-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-28-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-24-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower structured_syslog_topic-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-18-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-4-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-0-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-22-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-21-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-14-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-25-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-20-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-23-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-25-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-12-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-18-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-20-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-21-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower structured_syslog_topic-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-15-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-29-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-28-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-24-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-25-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-12-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-6-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-0-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-7-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-14-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-23-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-22-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-11-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-4-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-25-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-12-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-5-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-0-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-1-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-4-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-15-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-7-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-24-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-25-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-12-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-11-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-6-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,138] INFO [Broker id=3] Follower -uve-topic-18-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-23-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-11-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-25-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-12-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-29-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-21-0 starts at leader epoch 7 from offset 280 with high watermark 280. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-22-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-5-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-9-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-1-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-0-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-5-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-7-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-23-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-4-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-12-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-25-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-6-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-2-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-9-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-18-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-11-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-11-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,139] INFO [Broker id=3] Follower -uve-topic-29-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-24-0 starts at leader epoch 7 from offset 77 with high watermark 77. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-22-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-5-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-11-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-22-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-19-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-23-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-10-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-26-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-9-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-1-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-0-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-12-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-25-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-4-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-29-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-7-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-2-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-27-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-6-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-11-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-2-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-18-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-23-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-4-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-1-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-6-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-29-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-2-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-18-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-11-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-5-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-7-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-23-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-27-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-22-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-13-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-12-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-25-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-26-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-9-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-0-0 starts at leader epoch 7 from offset 957 with high watermark 957. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-10-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-19-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,140] INFO [Broker id=3] Follower -uve-topic-18-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-2-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-23-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-13-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-12-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-25-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-26-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-23-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-11-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-4-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-1-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-7-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-27-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-6-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-2-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-18-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-5-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-9-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,141] INFO [Broker id=3] Follower -uve-topic-1-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-22-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-3-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-19-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-23-0 starts at leader epoch 7 from offset 48 with high watermark 48. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-17-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-29-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-16-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-10-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-2-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-18-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-7-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-5-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-17-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-4-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-13-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-12-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-26-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,164] INFO [Broker id=3] Follower -uve-topic-29-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-17-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-18-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-10-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-11-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-19-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-27-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-1-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-6-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-22-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-9-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-16-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-3-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-2-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-9-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-1-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-9-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-5-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-9-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-1-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-3-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-19-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-4-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-8-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-29-0 starts at leader epoch 7 from offset 174 with high watermark 174. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-17-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-1-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-10-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-17-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-2-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-27-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-13-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-26-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-6-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-8-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-22-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-7-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,165] INFO [Broker id=3] Follower -uve-topic-16-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-01-27 02:16:39,175] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 10 for 320 partitions (state.change.logger)
[2025-01-27 02:16:39,215] INFO [Broker id=3] Add 320 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 11 (state.change.logger)