[2025-02-10 02:00:42,650] INFO [Broker id=1] 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-02-10 02:00:42,809] INFO [Broker id=1] Handling LeaderAndIsr request correlationId 1 from controller 2 for 960 partitions (state.change.logger)
[2025-02-10 02:00:43,902] ERROR [Broker id=1] 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-02-10 02:00:44,041] ERROR [Broker id=1] 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-02-10 02:00:44,056] ERROR [Broker id=1] 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-02-10 02:00:44,069] ERROR [Broker id=1] 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-02-10 02:00:44,078] ERROR [Broker id=1] 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-02-10 02:00:44,096] ERROR [Broker id=1] 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-02-10 02:00:44,107] ERROR [Broker id=1] 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-02-10 02:00:44,120] ERROR [Broker id=1] 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-02-10 02:00:44,132] ERROR [Broker id=1] 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-02-10 02:00:44,147] ERROR [Broker id=1] 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-02-10 02:00:44,156] ERROR [Broker id=1] 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-02-10 02:00:44,173] ERROR [Broker id=1] 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-02-10 02:00:44,182] ERROR [Broker id=1] 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-02-10 02:00:44,190] ERROR [Broker id=1] 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-02-10 02:00:44,198] ERROR [Broker id=1] 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-02-10 02:00:44,208] ERROR [Broker id=1] 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-02-10 02:00:44,218] ERROR [Broker id=1] 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-02-10 02:00:44,227] ERROR [Broker id=1] 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-02-10 02:00:44,253] ERROR [Broker id=1] 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-02-10 02:00:44,282] ERROR [Broker id=1] 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-02-10 02:00:44,300] ERROR [Broker id=1] 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-02-10 02:00:44,331] ERROR [Broker id=1] 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-02-10 02:00:44,338] ERROR [Broker id=1] 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-02-10 02:00:44,351] ERROR [Broker id=1] 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-02-10 02:00:44,363] ERROR [Broker id=1] 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-02-10 02:00:44,370] ERROR [Broker id=1] 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-02-10 02:00:44,375] ERROR [Broker id=1] 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-02-10 02:00:44,388] ERROR [Broker id=1] 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-02-10 02:00:44,424] ERROR [Broker id=1] 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-02-10 02:00:44,441] ERROR [Broker id=1] 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-02-10 02:00:44,459] ERROR [Broker id=1] 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-02-10 02:00:44,502] ERROR [Broker id=1] 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-02-10 02:00:44,542] ERROR [Broker id=1] 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-02-10 02:00:44,574] ERROR [Broker id=1] 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-02-10 02:00:44,604] ERROR [Broker id=1] 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-02-10 02:00:44,623] ERROR [Broker id=1] 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-02-10 02:00:44,630] ERROR [Broker id=1] 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-02-10 02:00:44,640] ERROR [Broker id=1] 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-02-10 02:00:44,648] ERROR [Broker id=1] 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-02-10 02:00:44,656] ERROR [Broker id=1] 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-02-10 02:00:44,665] ERROR [Broker id=1] 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-02-10 02:00:44,675] ERROR [Broker id=1] 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-02-10 02:00:44,681] ERROR [Broker id=1] 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-02-10 02:00:44,690] ERROR [Broker id=1] 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-02-10 02:00:44,704] ERROR [Broker id=1] 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-02-10 02:00:44,711] ERROR [Broker id=1] 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-02-10 02:00:44,718] ERROR [Broker id=1] 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-02-10 02:00:44,738] ERROR [Broker id=1] 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-02-10 02:00:44,752] ERROR [Broker id=1] 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-02-10 02:00:44,767] ERROR [Broker id=1] 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-02-10 02:00:44,775] ERROR [Broker id=1] 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-02-10 02:00:44,783] ERROR [Broker id=1] 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-02-10 02:00:44,811] ERROR [Broker id=1] 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-02-10 02:00:44,828] ERROR [Broker id=1] 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-02-10 02:00:44,849] ERROR [Broker id=1] 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-02-10 02:00:44,865] ERROR [Broker id=1] 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-02-10 02:00:44,889] ERROR [Broker id=1] 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-02-10 02:00:44,901] ERROR [Broker id=1] 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-02-10 02:00:44,922] ERROR [Broker id=1] 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-02-10 02:00:44,936] ERROR [Broker id=1] 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-02-10 02:00:44,955] ERROR [Broker id=1] 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-02-10 02:00:44,969] ERROR [Broker id=1] 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-02-10 02:00:45,007] ERROR [Broker id=1] 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-02-10 02:00:45,024] ERROR [Broker id=1] 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-02-10 02:00:45,068] ERROR [Broker id=1] 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-02-10 02:00:45,083] ERROR [Broker id=1] 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-02-10 02:00:45,119] ERROR [Broker id=1] 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-02-10 02:00:45,131] ERROR [Broker id=1] 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-02-10 02:00:45,149] ERROR [Broker id=1] 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-02-10 02:00:45,164] ERROR [Broker id=1] 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-02-10 02:00:45,179] ERROR [Broker id=1] 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-02-10 02:00:45,183] ERROR [Broker id=1] 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-02-10 02:00:45,193] ERROR [Broker id=1] 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-02-10 02:00:45,204] ERROR [Broker id=1] 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-02-10 02:00:45,229] ERROR [Broker id=1] 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-02-10 02:00:45,247] ERROR [Broker id=1] 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-02-10 02:00:45,267] ERROR [Broker id=1] 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-02-10 02:00:45,276] ERROR [Broker id=1] 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-02-10 02:00:45,296] ERROR [Broker id=1] 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-02-10 02:00:45,320] ERROR [Broker id=1] 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-02-10 02:00:45,352] ERROR [Broker id=1] 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-02-10 02:00:45,358] ERROR [Broker id=1] 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-02-10 02:00:45,399] ERROR [Broker id=1] 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-02-10 02:00:45,432] ERROR [Broker id=1] 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-02-10 02:00:45,456] ERROR [Broker id=1] 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-02-10 02:00:45,481] ERROR [Broker id=1] 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-02-10 02:00:45,503] ERROR [Broker id=1] 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-02-10 02:00:45,537] ERROR [Broker id=1] 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-02-10 02:00:45,550] ERROR [Broker id=1] 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-02-10 02:00:45,567] ERROR [Broker id=1] 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-02-10 02:00:45,583] ERROR [Broker id=1] 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-02-10 02:00:45,620] ERROR [Broker id=1] 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-02-10 02:00:45,625] ERROR [Broker id=1] 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-02-10 02:00:45,639] ERROR [Broker id=1] 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-02-10 02:00:45,657] ERROR [Broker id=1] 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-02-10 02:00:45,681] ERROR [Broker id=1] 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-02-10 02:00:45,724] ERROR [Broker id=1] 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-02-10 02:00:45,728] ERROR [Broker id=1] 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-02-10 02:00:45,738] ERROR [Broker id=1] 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-02-10 02:00:45,761] ERROR [Broker id=1] 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-02-10 02:00:45,773] ERROR [Broker id=1] 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-02-10 02:00:45,781] ERROR [Broker id=1] 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-02-10 02:00:45,790] ERROR [Broker id=1] 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-02-10 02:00:45,811] ERROR [Broker id=1] 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-02-10 02:00:45,831] ERROR [Broker id=1] 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-02-10 02:00:45,849] ERROR [Broker id=1] 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-02-10 02:00:45,874] ERROR [Broker id=1] 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-02-10 02:00:45,884] ERROR [Broker id=1] 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-02-10 02:00:45,908] ERROR [Broker id=1] 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-02-10 02:00:45,923] ERROR [Broker id=1] 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-02-10 02:00:45,927] ERROR [Broker id=1] 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-02-10 02:00:45,941] ERROR [Broker id=1] 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-02-10 02:00:45,949] ERROR [Broker id=1] 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-02-10 02:00:45,973] ERROR [Broker id=1] 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-02-10 02:00:45,995] ERROR [Broker id=1] 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-02-10 02:00:46,002] ERROR [Broker id=1] 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-02-10 02:00:46,009] ERROR [Broker id=1] 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-02-10 02:00:46,026] ERROR [Broker id=1] 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-02-10 02:00:46,056] ERROR [Broker id=1] 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-02-10 02:00:46,081] ERROR [Broker id=1] 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-02-10 02:00:46,084] ERROR [Broker id=1] 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-02-10 02:00:46,094] ERROR [Broker id=1] 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-02-10 02:00:46,103] ERROR [Broker id=1] 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-02-10 02:00:46,121] ERROR [Broker id=1] 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-02-10 02:00:46,126] ERROR [Broker id=1] 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-02-10 02:00:46,140] ERROR [Broker id=1] 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-02-10 02:00:46,149] ERROR [Broker id=1] 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-02-10 02:00:46,155] ERROR [Broker id=1] 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-02-10 02:00:46,176] ERROR [Broker id=1] 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-02-10 02:00:46,194] ERROR [Broker id=1] 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-02-10 02:00:46,220] ERROR [Broker id=1] 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-02-10 02:00:46,230] ERROR [Broker id=1] 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-02-10 02:00:46,247] ERROR [Broker id=1] 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-02-10 02:00:46,258] ERROR [Broker id=1] 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-02-10 02:00:46,276] ERROR [Broker id=1] 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-02-10 02:00:46,316] ERROR [Broker id=1] 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-02-10 02:00:46,348] ERROR [Broker id=1] 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-02-10 02:00:46,358] ERROR [Broker id=1] 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-02-10 02:00:46,403] ERROR [Broker id=1] 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-02-10 02:00:46,422] ERROR [Broker id=1] 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-02-10 02:00:46,426] ERROR [Broker id=1] 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-02-10 02:00:46,446] ERROR [Broker id=1] 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-02-10 02:00:46,467] ERROR [Broker id=1] 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-02-10 02:00:46,472] ERROR [Broker id=1] 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-02-10 02:00:46,513] ERROR [Broker id=1] 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-02-10 02:00:46,523] ERROR [Broker id=1] 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-02-10 02:00:46,530] ERROR [Broker id=1] 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-02-10 02:00:46,563] ERROR [Broker id=1] 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-02-10 02:00:46,599] ERROR [Broker id=1] 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-02-10 02:00:46,648] ERROR [Broker id=1] 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-02-10 02:00:46,664] ERROR [Broker id=1] 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-02-10 02:00:46,680] ERROR [Broker id=1] 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-02-10 02:00:46,685] ERROR [Broker id=1] 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-02-10 02:00:46,744] ERROR [Broker id=1] 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-02-10 02:00:46,760] ERROR [Broker id=1] 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-02-10 02:00:46,773] ERROR [Broker id=1] 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-02-10 02:00:46,795] ERROR [Broker id=1] 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-02-10 02:00:46,811] ERROR [Broker id=1] 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-02-10 02:00:46,827] ERROR [Broker id=1] 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-02-10 02:00:46,878] ERROR [Broker id=1] 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-02-10 02:00:46,931] ERROR [Broker id=1] 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-02-10 02:00:46,959] ERROR [Broker id=1] 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-02-10 02:00:46,977] ERROR [Broker id=1] 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-02-10 02:00:46,989] ERROR [Broker id=1] 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-02-10 02:00:47,005] ERROR [Broker id=1] 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-02-10 02:00:47,025] ERROR [Broker id=1] 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-02-10 02:00:47,069] ERROR [Broker id=1] 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-02-10 02:00:47,109] ERROR [Broker id=1] 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-02-10 02:00:47,136] ERROR [Broker id=1] 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-02-10 02:00:47,149] ERROR [Broker id=1] 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-02-10 02:00:47,157] ERROR [Broker id=1] 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-02-10 02:00:47,174] ERROR [Broker id=1] 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-02-10 02:00:47,189] ERROR [Broker id=1] 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-02-10 02:00:47,245] ERROR [Broker id=1] 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-02-10 02:00:47,267] ERROR [Broker id=1] 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-02-10 02:00:47,279] ERROR [Broker id=1] 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-02-10 02:00:47,300] ERROR [Broker id=1] 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-02-10 02:00:47,334] ERROR [Broker id=1] 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-02-10 02:00:47,351] ERROR [Broker id=1] 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-02-10 02:00:47,366] ERROR [Broker id=1] 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-02-10 02:00:47,394] ERROR [Broker id=1] 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-02-10 02:00:47,415] ERROR [Broker id=1] 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-02-10 02:00:47,430] ERROR [Broker id=1] 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-02-10 02:00:47,449] ERROR [Broker id=1] 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-02-10 02:00:47,454] ERROR [Broker id=1] 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-02-10 02:00:47,461] ERROR [Broker id=1] 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-02-10 02:00:47,473] ERROR [Broker id=1] 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-02-10 02:00:47,480] ERROR [Broker id=1] 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-02-10 02:00:47,492] ERROR [Broker id=1] 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-02-10 02:00:47,510] ERROR [Broker id=1] 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-02-10 02:00:47,539] ERROR [Broker id=1] 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-02-10 02:00:47,554] ERROR [Broker id=1] 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-02-10 02:00:47,563] ERROR [Broker id=1] 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-02-10 02:00:47,591] ERROR [Broker id=1] 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-02-10 02:00:47,595] ERROR [Broker id=1] 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-02-10 02:00:47,627] ERROR [Broker id=1] 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-02-10 02:00:47,631] ERROR [Broker id=1] 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-02-10 02:00:47,642] ERROR [Broker id=1] 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-02-10 02:00:47,650] ERROR [Broker id=1] 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-02-10 02:00:47,656] ERROR [Broker id=1] 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-02-10 02:00:47,661] ERROR [Broker id=1] 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-02-10 02:00:47,674] ERROR [Broker id=1] 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-02-10 02:00:47,693] ERROR [Broker id=1] 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-02-10 02:00:47,706] ERROR [Broker id=1] 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-02-10 02:00:47,708] ERROR [Broker id=1] 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-02-10 02:00:47,712] ERROR [Broker id=1] 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-02-10 02:00:47,735] ERROR [Broker id=1] 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-02-10 02:00:47,742] ERROR [Broker id=1] 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-02-10 02:00:47,755] ERROR [Broker id=1] 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-02-10 02:00:47,762] ERROR [Broker id=1] 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-02-10 02:00:47,765] ERROR [Broker id=1] 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-02-10 02:00:47,813] ERROR [Broker id=1] 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-02-10 02:00:47,819] ERROR [Broker id=1] 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-02-10 02:00:47,827] ERROR [Broker id=1] 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-02-10 02:00:47,845] ERROR [Broker id=1] 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-02-10 02:00:47,853] ERROR [Broker id=1] 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-02-10 02:00:47,870] ERROR [Broker id=1] 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-02-10 02:00:47,886] ERROR [Broker id=1] 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-02-10 02:00:47,889] ERROR [Broker id=1] 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-02-10 02:00:47,892] ERROR [Broker id=1] 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-02-10 02:00:47,906] ERROR [Broker id=1] 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-02-10 02:00:47,908] ERROR [Broker id=1] 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-02-10 02:00:47,918] ERROR [Broker id=1] 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-02-10 02:00:47,939] ERROR [Broker id=1] 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-02-10 02:00:47,963] ERROR [Broker id=1] 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-02-10 02:00:48,001] ERROR [Broker id=1] 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-02-10 02:00:48,008] ERROR [Broker id=1] 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-02-10 02:00:48,013] ERROR [Broker id=1] 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-02-10 02:00:48,016] ERROR [Broker id=1] 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-02-10 02:00:48,024] ERROR [Broker id=1] 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-02-10 02:00:48,027] ERROR [Broker id=1] 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-02-10 02:00:48,030] ERROR [Broker id=1] 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-02-10 02:00:48,041] ERROR [Broker id=1] 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-02-10 02:00:48,052] ERROR [Broker id=1] 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-02-10 02:00:48,057] ERROR [Broker id=1] 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-02-10 02:00:48,070] ERROR [Broker id=1] 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-02-10 02:00:48,077] ERROR [Broker id=1] 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-02-10 02:00:48,085] ERROR [Broker id=1] 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-02-10 02:00:48,092] ERROR [Broker id=1] 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-02-10 02:00:48,100] ERROR [Broker id=1] 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-02-10 02:00:48,109] ERROR [Broker id=1] 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-02-10 02:00:48,121] ERROR [Broker id=1] 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-02-10 02:00:48,126] ERROR [Broker id=1] 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-02-10 02:00:48,128] ERROR [Broker id=1] 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-02-10 02:00:48,131] ERROR [Broker id=1] 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-02-10 02:00:48,140] ERROR [Broker id=1] 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-02-10 02:00:48,146] ERROR [Broker id=1] 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-02-10 02:00:48,160] ERROR [Broker id=1] 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-02-10 02:00:48,167] ERROR [Broker id=1] 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-02-10 02:00:48,172] ERROR [Broker id=1] 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-02-10 02:00:48,231] ERROR [Broker id=1] 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-02-10 02:00:48,234] ERROR [Broker id=1] 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-02-10 02:00:48,242] ERROR [Broker id=1] 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-02-10 02:00:48,245] ERROR [Broker id=1] 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-02-10 02:00:48,250] ERROR [Broker id=1] 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-02-10 02:00:48,262] ERROR [Broker id=1] 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-02-10 02:00:48,280] ERROR [Broker id=1] 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-02-10 02:00:48,285] ERROR [Broker id=1] 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-02-10 02:00:48,311] ERROR [Broker id=1] 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-02-10 02:00:48,314] ERROR [Broker id=1] 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-02-10 02:00:48,319] ERROR [Broker id=1] 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-02-10 02:00:48,322] ERROR [Broker id=1] 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-02-10 02:00:48,328] ERROR [Broker id=1] 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-02-10 02:00:48,339] ERROR [Broker id=1] 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-02-10 02:00:48,343] ERROR [Broker id=1] 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-02-10 02:00:48,349] ERROR [Broker id=1] 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-02-10 02:00:48,362] ERROR [Broker id=1] 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-02-10 02:00:48,385] ERROR [Broker id=1] 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-02-10 02:00:48,389] ERROR [Broker id=1] 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-02-10 02:00:48,405] ERROR [Broker id=1] 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-02-10 02:00:48,413] ERROR [Broker id=1] 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-02-10 02:00:48,416] ERROR [Broker id=1] 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-02-10 02:00:48,430] ERROR [Broker id=1] 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-02-10 02:00:48,435] ERROR [Broker id=1] 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-02-10 02:00:48,448] ERROR [Broker id=1] 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-02-10 02:00:48,484] ERROR [Broker id=1] 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-02-10 02:00:48,504] ERROR [Broker id=1] 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-02-10 02:00:48,520] ERROR [Broker id=1] 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-02-10 02:00:48,537] ERROR [Broker id=1] 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-02-10 02:00:48,539] ERROR [Broker id=1] 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-02-10 02:00:48,541] ERROR [Broker id=1] 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-02-10 02:00:48,547] ERROR [Broker id=1] 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-02-10 02:00:48,564] ERROR [Broker id=1] 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-02-10 02:00:48,580] ERROR [Broker id=1] 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-02-10 02:00:48,588] ERROR [Broker id=1] 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-02-10 02:00:48,590] ERROR [Broker id=1] 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-02-10 02:00:48,622] ERROR [Broker id=1] 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-02-10 02:00:48,644] ERROR [Broker id=1] 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-02-10 02:00:48,649] ERROR [Broker id=1] 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-02-10 02:00:48,663] ERROR [Broker id=1] 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-02-10 02:00:48,679] ERROR [Broker id=1] 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-02-10 02:00:48,683] ERROR [Broker id=1] 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-02-10 02:00:48,691] ERROR [Broker id=1] 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-02-10 02:00:48,695] ERROR [Broker id=1] 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-02-10 02:00:48,703] ERROR [Broker id=1] 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-02-10 02:00:48,705] ERROR [Broker id=1] 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-02-10 02:00:48,707] ERROR [Broker id=1] 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-02-10 02:00:48,709] ERROR [Broker id=1] 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-02-10 02:00:48,711] ERROR [Broker id=1] 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-02-10 02:00:48,714] ERROR [Broker id=1] 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-02-10 02:00:48,716] ERROR [Broker id=1] 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-02-10 02:00:48,719] ERROR [Broker id=1] 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-02-10 02:00:48,721] ERROR [Broker id=1] 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-02-10 02:00:48,724] ERROR [Broker id=1] 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-02-10 02:00:48,729] ERROR [Broker id=1] 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-02-10 02:00:48,742] ERROR [Broker id=1] 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-02-10 02:00:48,767] ERROR [Broker id=1] 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-02-10 02:00:48,782] ERROR [Broker id=1] 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-02-10 02:00:48,798] ERROR [Broker id=1] 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-02-10 02:00:48,824] ERROR [Broker id=1] 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-02-10 02:00:48,837] ERROR [Broker id=1] 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-02-10 02:00:48,844] ERROR [Broker id=1] 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-02-10 02:00:48,849] ERROR [Broker id=1] 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-02-10 02:00:48,851] ERROR [Broker id=1] 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-02-10 02:00:48,853] ERROR [Broker id=1] 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-02-10 02:00:48,855] ERROR [Broker id=1] 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-02-10 02:00:48,859] ERROR [Broker id=1] 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-02-10 02:00:48,862] ERROR [Broker id=1] 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-02-10 02:00:48,865] ERROR [Broker id=1] 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-02-10 02:00:48,868] ERROR [Broker id=1] 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-02-10 02:00:48,872] ERROR [Broker id=1] 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-02-10 02:00:48,877] ERROR [Broker id=1] 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-02-10 02:00:48,880] ERROR [Broker id=1] 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-02-10 02:00:48,882] ERROR [Broker id=1] 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-02-10 02:00:48,884] ERROR [Broker id=1] 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-02-10 02:00:48,887] ERROR [Broker id=1] 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-02-10 02:00:48,889] ERROR [Broker id=1] 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-02-10 02:00:48,894] ERROR [Broker id=1] 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-02-10 02:00:48,900] ERROR [Broker id=1] 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-02-10 02:00:48,903] ERROR [Broker id=1] 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-02-10 02:00:48,910] ERROR [Broker id=1] 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-02-10 02:00:48,913] ERROR [Broker id=1] 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-02-10 02:00:48,922] ERROR [Broker id=1] 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-02-10 02:00:48,926] ERROR [Broker id=1] 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-02-10 02:00:48,929] ERROR [Broker id=1] 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-02-10 02:00:48,932] ERROR [Broker id=1] 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-02-10 02:00:48,935] ERROR [Broker id=1] 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-02-10 02:00:48,938] ERROR [Broker id=1] 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-02-10 02:00:48,940] ERROR [Broker id=1] 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-02-10 02:00:48,962] ERROR [Broker id=1] 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-02-10 02:00:48,971] ERROR [Broker id=1] 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-02-10 02:00:48,986] ERROR [Broker id=1] 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-02-10 02:00:48,990] ERROR [Broker id=1] 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-02-10 02:00:49,007] ERROR [Broker id=1] 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-02-10 02:00:49,017] ERROR [Broker id=1] 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-02-10 02:00:49,022] ERROR [Broker id=1] 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-02-10 02:00:49,035] ERROR [Broker id=1] 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-02-10 02:00:49,040] ERROR [Broker id=1] 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-02-10 02:00:49,044] ERROR [Broker id=1] 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-02-10 02:00:49,049] ERROR [Broker id=1] 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-02-10 02:00:49,052] ERROR [Broker id=1] 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-02-10 02:00:49,055] ERROR [Broker id=1] 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-02-10 02:00:49,061] ERROR [Broker id=1] 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-02-10 02:00:49,070] ERROR [Broker id=1] 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-02-10 02:00:49,073] ERROR [Broker id=1] 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-02-10 02:00:49,076] ERROR [Broker id=1] 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-02-10 02:00:49,079] ERROR [Broker id=1] 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-02-10 02:00:49,081] ERROR [Broker id=1] 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-02-10 02:00:49,083] ERROR [Broker id=1] 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-02-10 02:00:49,086] ERROR [Broker id=1] 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-02-10 02:00:49,088] ERROR [Broker id=1] 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-02-10 02:00:49,102] ERROR [Broker id=1] 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-02-10 02:00:49,105] ERROR [Broker id=1] 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-02-10 02:00:49,111] ERROR [Broker id=1] 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-02-10 02:00:49,118] ERROR [Broker id=1] 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-02-10 02:00:49,130] ERROR [Broker id=1] 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-02-10 02:00:49,140] ERROR [Broker id=1] 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-02-10 02:00:49,148] ERROR [Broker id=1] 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-02-10 02:00:49,155] ERROR [Broker id=1] 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-02-10 02:00:49,161] ERROR [Broker id=1] 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-02-10 02:00:49,164] ERROR [Broker id=1] 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-02-10 02:00:49,167] ERROR [Broker id=1] 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-02-10 02:00:49,169] ERROR [Broker id=1] 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-02-10 02:00:49,173] ERROR [Broker id=1] 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-02-10 02:00:49,176] ERROR [Broker id=1] 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-02-10 02:00:49,206] ERROR [Broker id=1] 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-02-10 02:00:49,209] ERROR [Broker id=1] 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-02-10 02:00:49,213] ERROR [Broker id=1] 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-02-10 02:00:49,218] ERROR [Broker id=1] 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-02-10 02:00:49,229] ERROR [Broker id=1] 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-02-10 02:00:49,233] ERROR [Broker id=1] 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-02-10 02:00:49,237] ERROR [Broker id=1] 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-02-10 02:00:49,243] ERROR [Broker id=1] 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-02-10 02:00:49,246] ERROR [Broker id=1] 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-02-10 02:00:49,261] ERROR [Broker id=1] 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-02-10 02:00:49,265] ERROR [Broker id=1] 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-02-10 02:00:49,268] ERROR [Broker id=1] 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-02-10 02:00:49,274] ERROR [Broker id=1] 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-02-10 02:00:49,285] ERROR [Broker id=1] 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-02-10 02:00:49,290] ERROR [Broker id=1] 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-02-10 02:00:49,295] ERROR [Broker id=1] 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-02-10 02:00:49,297] ERROR [Broker id=1] 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-02-10 02:00:49,300] ERROR [Broker id=1] 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-02-10 02:00:49,302] ERROR [Broker id=1] 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-02-10 02:00:49,308] ERROR [Broker id=1] 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-02-10 02:00:49,310] ERROR [Broker id=1] 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-02-10 02:00:49,312] ERROR [Broker id=1] 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-02-10 02:00:49,314] ERROR [Broker id=1] 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-02-10 02:00:49,316] ERROR [Broker id=1] 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-02-10 02:00:49,334] ERROR [Broker id=1] 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-02-10 02:00:49,338] ERROR [Broker id=1] 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-02-10 02:00:49,340] ERROR [Broker id=1] 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-02-10 02:00:49,343] ERROR [Broker id=1] 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-02-10 02:00:49,345] ERROR [Broker id=1] 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-02-10 02:00:49,348] ERROR [Broker id=1] 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-02-10 02:00:49,350] ERROR [Broker id=1] 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-02-10 02:00:49,352] ERROR [Broker id=1] 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-02-10 02:00:49,356] ERROR [Broker id=1] 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-02-10 02:00:49,358] ERROR [Broker id=1] 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-02-10 02:00:49,360] ERROR [Broker id=1] 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-02-10 02:00:49,373] ERROR [Broker id=1] 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-02-10 02:00:49,378] ERROR [Broker id=1] 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-02-10 02:00:49,380] ERROR [Broker id=1] 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-02-10 02:00:49,382] ERROR [Broker id=1] 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-02-10 02:00:49,384] ERROR [Broker id=1] 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-02-10 02:00:49,386] ERROR [Broker id=1] 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-02-10 02:00:49,390] ERROR [Broker id=1] 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-02-10 02:00:49,392] ERROR [Broker id=1] 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-02-10 02:00:49,396] ERROR [Broker id=1] 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-02-10 02:00:49,398] ERROR [Broker id=1] 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-02-10 02:00:49,399] ERROR [Broker id=1] 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-02-10 02:00:49,401] ERROR [Broker id=1] 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-02-10 02:00:49,403] ERROR [Broker id=1] 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-02-10 02:00:49,405] ERROR [Broker id=1] 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-02-10 02:00:49,407] ERROR [Broker id=1] 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-02-10 02:00:49,417] ERROR [Broker id=1] 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-02-10 02:00:49,419] ERROR [Broker id=1] 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-02-10 02:00:49,421] ERROR [Broker id=1] 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-02-10 02:00:49,423] ERROR [Broker id=1] 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-02-10 02:00:49,426] ERROR [Broker id=1] 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-02-10 02:00:49,430] ERROR [Broker id=1] 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-02-10 02:00:49,432] ERROR [Broker id=1] 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-02-10 02:00:49,434] ERROR [Broker id=1] 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-02-10 02:00:49,436] ERROR [Broker id=1] 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-02-10 02:00:49,439] ERROR [Broker id=1] 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-02-10 02:00:49,443] ERROR [Broker id=1] 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-02-10 02:00:49,446] ERROR [Broker id=1] 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-02-10 02:00:49,450] ERROR [Broker id=1] 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-02-10 02:00:49,454] ERROR [Broker id=1] 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-02-10 02:00:49,456] ERROR [Broker id=1] 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-02-10 02:00:49,463] ERROR [Broker id=1] 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-02-10 02:00:49,465] ERROR [Broker id=1] 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-02-10 02:00:49,472] ERROR [Broker id=1] 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-02-10 02:00:49,479] ERROR [Broker id=1] 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-02-10 02:00:49,484] ERROR [Broker id=1] 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-02-10 02:00:49,486] ERROR [Broker id=1] 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-02-10 02:00:49,490] ERROR [Broker id=1] 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-02-10 02:00:49,492] ERROR [Broker id=1] 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-02-10 02:00:49,530] ERROR [Broker id=1] 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-02-10 02:00:49,533] ERROR [Broker id=1] 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-02-10 02:00:49,536] ERROR [Broker id=1] 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-02-10 02:00:49,540] ERROR [Broker id=1] 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-02-10 02:00:49,543] ERROR [Broker id=1] 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-02-10 02:00:49,546] ERROR [Broker id=1] 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-02-10 02:00:49,550] ERROR [Broker id=1] 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-02-10 02:00:49,554] ERROR [Broker id=1] 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-02-10 02:00:49,556] ERROR [Broker id=1] 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-02-10 02:00:49,559] ERROR [Broker id=1] 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-02-10 02:00:49,563] ERROR [Broker id=1] 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-02-10 02:00:49,567] ERROR [Broker id=1] 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-02-10 02:00:49,570] ERROR [Broker id=1] 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-02-10 02:00:49,574] ERROR [Broker id=1] 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-02-10 02:00:49,577] ERROR [Broker id=1] 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-02-10 02:00:49,579] ERROR [Broker id=1] 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-02-10 02:00:49,581] ERROR [Broker id=1] 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-02-10 02:00:49,584] ERROR [Broker id=1] 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-02-10 02:00:49,585] ERROR [Broker id=1] 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-02-10 02:00:49,587] ERROR [Broker id=1] 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-02-10 02:00:49,594] ERROR [Broker id=1] 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-02-10 02:00:49,596] ERROR [Broker id=1] 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-02-10 02:00:49,598] ERROR [Broker id=1] 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-02-10 02:00:49,600] ERROR [Broker id=1] 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-02-10 02:00:49,601] ERROR [Broker id=1] 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-02-10 02:00:49,604] ERROR [Broker id=1] 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-02-10 02:00:49,606] ERROR [Broker id=1] 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-02-10 02:00:49,608] ERROR [Broker id=1] 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-02-10 02:00:49,610] ERROR [Broker id=1] 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-02-10 02:00:49,614] ERROR [Broker id=1] 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-02-10 02:00:49,616] ERROR [Broker id=1] 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-02-10 02:00:49,618] ERROR [Broker id=1] 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-02-10 02:00:49,620] ERROR [Broker id=1] 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-02-10 02:00:49,622] ERROR [Broker id=1] 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-02-10 02:00:49,623] ERROR [Broker id=1] 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-02-10 02:00:49,625] ERROR [Broker id=1] 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-02-10 02:00:49,626] ERROR [Broker id=1] 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-02-10 02:00:49,628] ERROR [Broker id=1] 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-02-10 02:00:49,629] ERROR [Broker id=1] 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-02-10 02:00:49,663] ERROR [Broker id=1] 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-02-10 02:00:49,667] ERROR [Broker id=1] 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-02-10 02:00:49,671] ERROR [Broker id=1] 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-02-10 02:00:49,676] ERROR [Broker id=1] 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-02-10 02:00:49,680] ERROR [Broker id=1] 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-02-10 02:00:49,683] ERROR [Broker id=1] 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-02-10 02:00:49,685] ERROR [Broker id=1] 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-02-10 02:00:49,688] ERROR [Broker id=1] 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-02-10 02:00:49,694] ERROR [Broker id=1] 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-02-10 02:00:49,696] ERROR [Broker id=1] 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-02-10 02:00:49,710] ERROR [Broker id=1] 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-02-10 02:00:49,718] ERROR [Broker id=1] 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-02-10 02:00:49,720] ERROR [Broker id=1] 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-02-10 02:00:49,724] ERROR [Broker id=1] 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-02-10 02:00:49,726] ERROR [Broker id=1] 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-02-10 02:00:49,728] ERROR [Broker id=1] 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-02-10 02:00:49,732] ERROR [Broker id=1] 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-02-10 02:00:49,735] ERROR [Broker id=1] 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-02-10 02:00:49,742] ERROR [Broker id=1] 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-02-10 02:00:49,746] ERROR [Broker id=1] 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-02-10 02:00:49,749] ERROR [Broker id=1] 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-02-10 02:00:49,754] ERROR [Broker id=1] 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-02-10 02:00:49,758] ERROR [Broker id=1] 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-02-10 02:00:49,761] ERROR [Broker id=1] 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-02-10 02:00:49,768] ERROR [Broker id=1] 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-02-10 02:00:49,772] ERROR [Broker id=1] 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-02-10 02:00:49,778] ERROR [Broker id=1] 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-02-10 02:00:49,780] ERROR [Broker id=1] 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-02-10 02:00:49,782] ERROR [Broker id=1] 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-02-10 02:00:49,785] ERROR [Broker id=1] 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-02-10 02:00:49,787] ERROR [Broker id=1] 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-02-10 02:00:49,792] ERROR [Broker id=1] 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-02-10 02:00:49,796] ERROR [Broker id=1] 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-02-10 02:00:49,799] ERROR [Broker id=1] 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-02-10 02:00:49,806] ERROR [Broker id=1] 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-02-10 02:00:49,809] ERROR [Broker id=1] 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-02-10 02:00:49,813] ERROR [Broker id=1] 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-02-10 02:00:49,817] ERROR [Broker id=1] 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-02-10 02:00:49,823] ERROR [Broker id=1] 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-02-10 02:00:49,825] ERROR [Broker id=1] 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-02-10 02:00:49,827] ERROR [Broker id=1] 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-02-10 02:00:49,829] ERROR [Broker id=1] 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-02-10 02:00:49,831] ERROR [Broker id=1] 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-02-10 02:00:49,833] ERROR [Broker id=1] 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-02-10 02:00:49,837] ERROR [Broker id=1] 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-02-10 02:00:49,839] ERROR [Broker id=1] 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-02-10 02:00:49,842] ERROR [Broker id=1] 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-02-10 02:00:49,844] ERROR [Broker id=1] 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-02-10 02:00:49,846] ERROR [Broker id=1] 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-02-10 02:00:49,851] ERROR [Broker id=1] 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-02-10 02:00:49,854] ERROR [Broker id=1] 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-02-10 02:00:49,862] ERROR [Broker id=1] 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-02-10 02:00:49,868] ERROR [Broker id=1] 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-02-10 02:00:49,871] ERROR [Broker id=1] 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-02-10 02:00:49,872] ERROR [Broker id=1] 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-02-10 02:00:49,874] ERROR [Broker id=1] 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-02-10 02:00:49,875] ERROR [Broker id=1] 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-02-10 02:00:49,878] ERROR [Broker id=1] 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-02-10 02:00:49,880] ERROR [Broker id=1] 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-02-10 02:00:49,883] ERROR [Broker id=1] 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-02-10 02:00:49,886] ERROR [Broker id=1] 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-02-10 02:00:49,888] ERROR [Broker id=1] 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-02-10 02:00:49,890] ERROR [Broker id=1] 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-02-10 02:00:49,892] ERROR [Broker id=1] 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-02-10 02:00:49,894] ERROR [Broker id=1] 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-02-10 02:00:49,896] ERROR [Broker id=1] 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-02-10 02:00:49,898] ERROR [Broker id=1] 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-02-10 02:00:49,900] ERROR [Broker id=1] 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-02-10 02:00:49,901] ERROR [Broker id=1] 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-02-10 02:00:49,903] ERROR [Broker id=1] 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-02-10 02:00:49,904] ERROR [Broker id=1] 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-02-10 02:00:49,906] ERROR [Broker id=1] 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-02-10 02:00:49,907] ERROR [Broker id=1] 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-02-10 02:00:49,908] ERROR [Broker id=1] 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-02-10 02:00:49,910] ERROR [Broker id=1] 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-02-10 02:00:49,912] ERROR [Broker id=1] 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-02-10 02:00:49,913] ERROR [Broker id=1] 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-02-10 02:00:49,915] ERROR [Broker id=1] 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-02-10 02:00:49,916] ERROR [Broker id=1] 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-02-10 02:00:49,918] ERROR [Broker id=1] 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-02-10 02:00:49,919] ERROR [Broker id=1] 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-02-10 02:00:49,921] ERROR [Broker id=1] 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-02-10 02:00:49,923] ERROR [Broker id=1] 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-02-10 02:00:49,927] ERROR [Broker id=1] 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-02-10 02:00:49,928] ERROR [Broker id=1] 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-02-10 02:00:49,932] ERROR [Broker id=1] 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-02-10 02:00:49,934] ERROR [Broker id=1] 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-02-10 02:00:49,935] ERROR [Broker id=1] 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-02-10 02:00:49,937] ERROR [Broker id=1] 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-02-10 02:00:49,938] ERROR [Broker id=1] 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-02-10 02:00:49,940] ERROR [Broker id=1] 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-02-10 02:00:49,942] ERROR [Broker id=1] 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-02-10 02:00:49,943] ERROR [Broker id=1] 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-02-10 02:00:49,945] ERROR [Broker id=1] 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-02-10 02:00:49,947] ERROR [Broker id=1] 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-02-10 02:00:49,948] ERROR [Broker id=1] 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-02-10 02:00:49,950] ERROR [Broker id=1] 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-02-10 02:00:49,952] ERROR [Broker id=1] 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-02-10 02:00:49,954] ERROR [Broker id=1] 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-02-10 02:00:49,956] ERROR [Broker id=1] 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-02-10 02:00:49,957] ERROR [Broker id=1] 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-02-10 02:00:49,959] ERROR [Broker id=1] 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-02-10 02:00:49,962] ERROR [Broker id=1] 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-02-10 02:00:49,966] ERROR [Broker id=1] 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-02-10 02:00:49,968] ERROR [Broker id=1] 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-02-10 02:00:49,979] ERROR [Broker id=1] 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-02-10 02:00:49,981] ERROR [Broker id=1] 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-02-10 02:00:49,983] ERROR [Broker id=1] 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-02-10 02:00:49,986] ERROR [Broker id=1] 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-02-10 02:00:49,989] ERROR [Broker id=1] 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-02-10 02:00:49,998] ERROR [Broker id=1] 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-02-10 02:00:50,000] ERROR [Broker id=1] 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-02-10 02:00:50,004] ERROR [Broker id=1] 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-02-10 02:00:50,008] ERROR [Broker id=1] 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-02-10 02:00:50,011] ERROR [Broker id=1] 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-02-10 02:00:50,013] ERROR [Broker id=1] 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-02-10 02:00:50,014] ERROR [Broker id=1] 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-02-10 02:00:50,016] ERROR [Broker id=1] 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-02-10 02:00:50,022] ERROR [Broker id=1] 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-02-10 02:00:50,027] ERROR [Broker id=1] 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-02-10 02:00:50,032] ERROR [Broker id=1] 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-02-10 02:00:50,043] ERROR [Broker id=1] 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-02-10 02:00:50,045] ERROR [Broker id=1] 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-02-10 02:00:50,047] ERROR [Broker id=1] 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-02-10 02:00:50,049] ERROR [Broker id=1] 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-02-10 02:00:50,052] ERROR [Broker id=1] 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-02-10 02:00:50,055] ERROR [Broker id=1] 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-02-10 02:00:50,058] ERROR [Broker id=1] 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-02-10 02:00:50,060] ERROR [Broker id=1] 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-02-10 02:00:50,067] ERROR [Broker id=1] 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-02-10 02:00:50,069] ERROR [Broker id=1] 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-02-10 02:00:50,071] ERROR [Broker id=1] 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-02-10 02:00:50,073] ERROR [Broker id=1] 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-02-10 02:00:50,075] ERROR [Broker id=1] 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-02-10 02:00:50,077] ERROR [Broker id=1] 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-02-10 02:00:50,091] ERROR [Broker id=1] 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-02-10 02:00:50,099] ERROR [Broker id=1] 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-02-10 02:00:50,107] ERROR [Broker id=1] 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-02-10 02:00:50,110] ERROR [Broker id=1] 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-02-10 02:00:50,112] ERROR [Broker id=1] 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-02-10 02:00:50,116] ERROR [Broker id=1] 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-02-10 02:00:50,118] ERROR [Broker id=1] 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-02-10 02:00:50,120] ERROR [Broker id=1] 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-02-10 02:00:50,121] ERROR [Broker id=1] 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-02-10 02:00:50,125] ERROR [Broker id=1] 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-02-10 02:00:50,130] ERROR [Broker id=1] 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-02-10 02:00:50,133] ERROR [Broker id=1] 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-02-10 02:00:50,137] ERROR [Broker id=1] 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-02-10 02:00:50,140] ERROR [Broker id=1] 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-02-10 02:00:50,147] ERROR [Broker id=1] 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-02-10 02:00:50,152] ERROR [Broker id=1] 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-02-10 02:00:50,169] ERROR [Broker id=1] 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-02-10 02:00:50,183] ERROR [Broker id=1] 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-02-10 02:00:50,197] ERROR [Broker id=1] 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-02-10 02:00:50,203] ERROR [Broker id=1] 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-02-10 02:00:50,211] ERROR [Broker id=1] 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-02-10 02:00:50,215] ERROR [Broker id=1] 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-02-10 02:00:50,225] ERROR [Broker id=1] 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-02-10 02:00:50,227] ERROR [Broker id=1] 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-02-10 02:00:50,230] ERROR [Broker id=1] 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-02-10 02:00:50,232] ERROR [Broker id=1] 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-02-10 02:00:50,234] ERROR [Broker id=1] 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-02-10 02:00:50,236] ERROR [Broker id=1] 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-02-10 02:00:50,238] ERROR [Broker id=1] 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-02-10 02:00:50,247] ERROR [Broker id=1] 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-02-10 02:00:50,251] ERROR [Broker id=1] 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-02-10 02:00:50,254] ERROR [Broker id=1] 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-02-10 02:00:50,257] ERROR [Broker id=1] 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-02-10 02:00:50,259] ERROR [Broker id=1] 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-02-10 02:00:50,261] ERROR [Broker id=1] 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-02-10 02:00:50,264] ERROR [Broker id=1] 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-02-10 02:00:50,265] ERROR [Broker id=1] 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-02-10 02:00:50,268] ERROR [Broker id=1] 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-02-10 02:00:50,270] ERROR [Broker id=1] 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-02-10 02:00:50,271] ERROR [Broker id=1] 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-02-10 02:00:50,279] ERROR [Broker id=1] 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-02-10 02:00:50,281] ERROR [Broker id=1] 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-02-10 02:00:50,284] ERROR [Broker id=1] 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-02-10 02:00:50,287] ERROR [Broker id=1] 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-02-10 02:00:50,290] ERROR [Broker id=1] 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-02-10 02:00:50,292] ERROR [Broker id=1] 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-02-10 02:00:50,294] ERROR [Broker id=1] 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-02-10 02:00:50,295] ERROR [Broker id=1] 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-02-10 02:00:50,297] ERROR [Broker id=1] 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-02-10 02:00:50,298] ERROR [Broker id=1] 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-02-10 02:00:50,300] ERROR [Broker id=1] 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-02-10 02:00:50,303] ERROR [Broker id=1] 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-02-10 02:00:50,304] ERROR [Broker id=1] 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-02-10 02:00:50,317] ERROR [Broker id=1] 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-02-10 02:00:50,320] ERROR [Broker id=1] 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-02-10 02:00:50,321] ERROR [Broker id=1] 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-02-10 02:00:50,323] ERROR [Broker id=1] 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-02-10 02:00:50,325] ERROR [Broker id=1] 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-02-10 02:00:50,326] ERROR [Broker id=1] 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-02-10 02:00:50,328] ERROR [Broker id=1] 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-02-10 02:00:50,330] ERROR [Broker id=1] 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-02-10 02:00:50,332] ERROR [Broker id=1] 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-02-10 02:00:50,334] ERROR [Broker id=1] 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-02-10 02:00:50,336] ERROR [Broker id=1] 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-02-10 02:00:50,337] ERROR [Broker id=1] 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-02-10 02:00:50,343] ERROR [Broker id=1] 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-02-10 02:00:50,346] ERROR [Broker id=1] 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-02-10 02:00:50,348] ERROR [Broker id=1] 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-02-10 02:00:50,349] ERROR [Broker id=1] 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-02-10 02:00:50,351] ERROR [Broker id=1] 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-02-10 02:00:50,353] ERROR [Broker id=1] 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-02-10 02:00:50,354] ERROR [Broker id=1] 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-02-10 02:00:50,356] ERROR [Broker id=1] 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-02-10 02:00:50,359] ERROR [Broker id=1] 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-02-10 02:00:50,361] ERROR [Broker id=1] 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-02-10 02:00:50,362] ERROR [Broker id=1] 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-02-10 02:00:50,364] ERROR [Broker id=1] 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-02-10 02:00:50,367] ERROR [Broker id=1] 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-02-10 02:00:50,370] ERROR [Broker id=1] 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-02-10 02:00:50,372] ERROR [Broker id=1] 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-02-10 02:00:50,373] ERROR [Broker id=1] 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-02-10 02:00:50,375] ERROR [Broker id=1] 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-02-10 02:00:50,377] ERROR [Broker id=1] 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-02-10 02:00:50,381] ERROR [Broker id=1] 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-02-10 02:00:50,383] ERROR [Broker id=1] 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-02-10 02:00:50,385] ERROR [Broker id=1] 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-02-10 02:00:50,386] ERROR [Broker id=1] 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-02-10 02:00:50,388] ERROR [Broker id=1] 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-02-10 02:00:50,389] ERROR [Broker id=1] 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-02-10 02:00:50,391] ERROR [Broker id=1] 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-02-10 02:00:50,392] ERROR [Broker id=1] 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-02-10 02:00:50,439] ERROR [Broker id=1] 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-02-10 02:00:50,445] ERROR [Broker id=1] 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-02-10 02:00:50,447] ERROR [Broker id=1] 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-02-10 02:00:50,451] ERROR [Broker id=1] 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-02-10 02:00:50,452] ERROR [Broker id=1] 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-02-10 02:00:50,454] ERROR [Broker id=1] 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-02-10 02:00:50,456] ERROR [Broker id=1] 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-02-10 02:00:50,458] ERROR [Broker id=1] 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-02-10 02:00:50,459] ERROR [Broker id=1] 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-02-10 02:00:50,461] ERROR [Broker id=1] 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-02-10 02:00:50,463] ERROR [Broker id=1] 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-02-10 02:00:50,466] ERROR [Broker id=1] 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-02-10 02:00:50,469] ERROR [Broker id=1] 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-02-10 02:00:50,479] ERROR [Broker id=1] 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-02-10 02:00:50,487] ERROR [Broker id=1] 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-02-10 02:00:50,489] ERROR [Broker id=1] 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-02-10 02:00:50,490] ERROR [Broker id=1] 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-02-10 02:00:50,492] ERROR [Broker id=1] 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-02-10 02:00:50,497] ERROR [Broker id=1] 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-02-10 02:00:50,498] ERROR [Broker id=1] 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-02-10 02:00:50,500] ERROR [Broker id=1] 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-02-10 02:00:50,501] ERROR [Broker id=1] 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-02-10 02:00:50,507] ERROR [Broker id=1] 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-02-10 02:00:50,509] ERROR [Broker id=1] 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-02-10 02:00:50,510] ERROR [Broker id=1] 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-02-10 02:00:50,512] ERROR [Broker id=1] 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-02-10 02:00:50,514] ERROR [Broker id=1] 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-02-10 02:00:50,517] ERROR [Broker id=1] 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-02-10 02:00:50,518] ERROR [Broker id=1] 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-02-10 02:00:50,520] ERROR [Broker id=1] 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-02-10 02:00:50,522] ERROR [Broker id=1] 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-02-10 02:00:50,523] ERROR [Broker id=1] 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-02-10 02:00:50,525] ERROR [Broker id=1] 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-02-10 02:00:50,526] ERROR [Broker id=1] 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-02-10 02:00:50,528] ERROR [Broker id=1] 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-02-10 02:00:50,529] ERROR [Broker id=1] 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-02-10 02:00:50,531] ERROR [Broker id=1] 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-02-10 02:00:50,532] ERROR [Broker id=1] 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-02-10 02:00:50,534] ERROR [Broker id=1] 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-02-10 02:00:50,536] ERROR [Broker id=1] 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-02-10 02:00:50,538] ERROR [Broker id=1] 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-02-10 02:00:50,539] ERROR [Broker id=1] 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-02-10 02:00:50,541] ERROR [Broker id=1] 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-02-10 02:00:50,543] ERROR [Broker id=1] 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-02-10 02:00:50,544] ERROR [Broker id=1] 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-02-10 02:00:50,546] ERROR [Broker id=1] 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-02-10 02:00:50,548] ERROR [Broker id=1] 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-02-10 02:00:50,550] ERROR [Broker id=1] 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-02-10 02:00:50,551] ERROR [Broker id=1] 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-02-10 02:00:50,553] ERROR [Broker id=1] 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-02-10 02:00:50,555] ERROR [Broker id=1] 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-02-10 02:00:50,558] ERROR [Broker id=1] 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-02-10 02:00:50,565] ERROR [Broker id=1] 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-02-10 02:00:50,567] ERROR [Broker id=1] 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-02-10 02:00:50,569] ERROR [Broker id=1] 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-02-10 02:00:50,573] ERROR [Broker id=1] 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-02-10 02:00:50,579] ERROR [Broker id=1] 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-02-10 02:00:50,581] ERROR [Broker id=1] 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-02-10 02:00:50,584] ERROR [Broker id=1] 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-02-10 02:00:50,586] ERROR [Broker id=1] 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-02-10 02:00:50,587] ERROR [Broker id=1] 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-02-10 02:00:50,589] ERROR [Broker id=1] 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-02-10 02:00:50,590] ERROR [Broker id=1] 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-02-10 02:00:50,592] ERROR [Broker id=1] 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-02-10 02:00:50,593] ERROR [Broker id=1] 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-02-10 02:00:50,595] ERROR [Broker id=1] 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-02-10 02:00:50,596] ERROR [Broker id=1] 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-02-10 02:00:50,598] ERROR [Broker id=1] 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-02-10 02:00:50,599] ERROR [Broker id=1] 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-02-10 02:00:50,602] ERROR [Broker id=1] 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-02-10 02:00:50,605] ERROR [Broker id=1] 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-02-10 02:00:50,607] ERROR [Broker id=1] 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-02-10 02:00:50,609] ERROR [Broker id=1] 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-02-10 02:00:50,611] ERROR [Broker id=1] 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-02-10 02:00:50,613] ERROR [Broker id=1] 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-02-10 02:00:50,615] ERROR [Broker id=1] 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-02-10 02:00:50,617] ERROR [Broker id=1] 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-02-10 02:00:50,619] ERROR [Broker id=1] 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-02-10 02:00:50,622] ERROR [Broker id=1] 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-02-10 02:00:50,624] ERROR [Broker id=1] 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-02-10 02:00:50,626] ERROR [Broker id=1] 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-02-10 02:00:50,628] ERROR [Broker id=1] 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-02-10 02:00:50,630] ERROR [Broker id=1] 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-02-10 02:00:50,632] ERROR [Broker id=1] 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-02-10 02:00:50,634] ERROR [Broker id=1] 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-02-10 02:00:50,637] ERROR [Broker id=1] 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-02-10 02:00:50,638] ERROR [Broker id=1] 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-02-10 02:00:50,641] ERROR [Broker id=1] 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-02-10 02:00:50,643] ERROR [Broker id=1] 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-02-10 02:00:50,644] ERROR [Broker id=1] 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-02-10 02:00:50,645] ERROR [Broker id=1] 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-02-10 02:00:50,646] ERROR [Broker id=1] 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-02-10 02:00:50,648] ERROR [Broker id=1] 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-02-10 02:00:50,649] ERROR [Broker id=1] 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-02-10 02:00:50,650] ERROR [Broker id=1] 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-02-10 02:00:50,651] ERROR [Broker id=1] 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-02-10 02:00:50,653] ERROR [Broker id=1] 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-02-10 02:00:50,654] ERROR [Broker id=1] 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-02-10 02:00:50,655] ERROR [Broker id=1] 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-02-10 02:00:50,657] ERROR [Broker id=1] 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-02-10 02:00:50,658] ERROR [Broker id=1] 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-02-10 02:00:50,659] ERROR [Broker id=1] 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-02-10 02:00:50,660] ERROR [Broker id=1] 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-02-10 02:00:50,662] ERROR [Broker id=1] 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-02-10 02:00:50,663] ERROR [Broker id=1] 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-02-10 02:00:50,665] ERROR [Broker id=1] 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-02-10 02:00:50,669] ERROR [Broker id=1] 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-02-10 02:00:50,670] ERROR [Broker id=1] 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-02-10 02:00:50,672] ERROR [Broker id=1] 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-02-10 02:00:50,673] ERROR [Broker id=1] 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-02-10 02:00:50,674] ERROR [Broker id=1] 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-02-10 02:00:50,676] ERROR [Broker id=1] 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-02-10 02:00:50,677] ERROR [Broker id=1] 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-02-10 02:00:50,678] ERROR [Broker id=1] 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-02-10 02:00:50,679] ERROR [Broker id=1] 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-02-10 02:00:50,681] ERROR [Broker id=1] 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-02-10 02:00:50,682] ERROR [Broker id=1] 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-02-10 02:00:50,683] ERROR [Broker id=1] 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-02-10 02:00:50,684] ERROR [Broker id=1] 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-02-10 02:00:50,686] ERROR [Broker id=1] 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-02-10 02:00:50,688] ERROR [Broker id=1] 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-02-10 02:00:50,695] ERROR [Broker id=1] 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-02-10 02:00:50,697] ERROR [Broker id=1] 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-02-10 02:00:50,698] ERROR [Broker id=1] 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-02-10 02:00:50,699] ERROR [Broker id=1] 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-02-10 02:00:50,701] ERROR [Broker id=1] 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-02-10 02:00:50,702] ERROR [Broker id=1] 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-02-10 02:00:50,703] ERROR [Broker id=1] 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-02-10 02:00:50,704] ERROR [Broker id=1] 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-02-10 02:00:50,705] ERROR [Broker id=1] 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-02-10 02:00:50,710] ERROR [Broker id=1] 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-02-10 02:00:50,712] ERROR [Broker id=1] 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-02-10 02:00:50,716] ERROR [Broker id=1] 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-02-10 02:00:50,743] ERROR [Broker id=1] 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-02-10 02:00:50,747] ERROR [Broker id=1] 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-02-10 02:00:50,750] ERROR [Broker id=1] 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-02-10 02:00:50,752] ERROR [Broker id=1] 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-02-10 02:00:50,759] ERROR [Broker id=1] 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-02-10 02:00:50,762] ERROR [Broker id=1] 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-02-10 02:00:50,765] ERROR [Broker id=1] 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-02-10 02:00:50,766] ERROR [Broker id=1] 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-02-10 02:00:50,768] ERROR [Broker id=1] 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-02-10 02:00:50,772] ERROR [Broker id=1] 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-02-10 02:00:50,778] ERROR [Broker id=1] 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-02-10 02:00:50,779] ERROR [Broker id=1] 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-02-10 02:00:50,781] ERROR [Broker id=1] 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-02-10 02:00:50,782] ERROR [Broker id=1] 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-02-10 02:00:50,783] ERROR [Broker id=1] 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-02-10 02:00:50,785] ERROR [Broker id=1] 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-02-10 02:00:50,786] ERROR [Broker id=1] 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-02-10 02:00:50,787] ERROR [Broker id=1] 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-02-10 02:00:50,790] ERROR [Broker id=1] 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-02-10 02:00:50,793] ERROR [Broker id=1] 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-02-10 02:00:50,797] ERROR [Broker id=1] 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-02-10 02:00:50,798] ERROR [Broker id=1] 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-02-10 02:00:50,800] ERROR [Broker id=1] 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-02-10 02:00:50,801] ERROR [Broker id=1] 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-02-10 02:00:50,803] ERROR [Broker id=1] 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-02-10 02:00:50,804] ERROR [Broker id=1] 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-02-10 02:00:50,805] ERROR [Broker id=1] 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-02-10 02:00:50,807] ERROR [Broker id=1] 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-02-10 02:00:50,809] ERROR [Broker id=1] 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-02-10 02:00:50,814] ERROR [Broker id=1] 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-02-10 02:00:50,816] ERROR [Broker id=1] 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-02-10 02:00:50,819] ERROR [Broker id=1] 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-02-10 02:00:50,822] ERROR [Broker id=1] 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-02-10 02:00:50,825] ERROR [Broker id=1] 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-02-10 02:00:50,828] ERROR [Broker id=1] 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-02-10 02:00:50,831] ERROR [Broker id=1] 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-02-10 02:00:50,833] ERROR [Broker id=1] 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-02-10 02:00:50,835] ERROR [Broker id=1] 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-02-10 02:00:50,838] ERROR [Broker id=1] 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-02-10 02:00:50,843] ERROR [Broker id=1] 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-02-10 02:00:50,847] ERROR [Broker id=1] 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-02-10 02:00:50,872] ERROR [Broker id=1] 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-02-10 02:00:50,874] ERROR [Broker id=1] 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-02-10 02:00:50,877] ERROR [Broker id=1] 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-02-10 02:00:50,879] ERROR [Broker id=1] 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-02-10 02:00:50,880] ERROR [Broker id=1] 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-02-10 02:00:50,884] ERROR [Broker id=1] 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-02-10 02:00:50,886] ERROR [Broker id=1] 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-02-10 02:00:50,887] ERROR [Broker id=1] 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-02-10 02:00:50,889] ERROR [Broker id=1] 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-02-10 02:00:50,890] ERROR [Broker id=1] 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-02-10 02:00:50,893] ERROR [Broker id=1] 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-02-10 02:00:50,895] ERROR [Broker id=1] 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-02-10 02:00:50,897] ERROR [Broker id=1] 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-02-10 02:00:50,898] ERROR [Broker id=1] 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-02-10 02:00:50,900] ERROR [Broker id=1] 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-02-10 02:00:50,903] ERROR [Broker id=1] 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-02-10 02:00:50,909] ERROR [Broker id=1] 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-02-10 02:00:50,911] ERROR [Broker id=1] 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-02-10 02:00:50,913] ERROR [Broker id=1] 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-02-10 02:00:50,914] ERROR [Broker id=1] 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-02-10 02:00:50,916] ERROR [Broker id=1] 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-02-10 02:00:50,918] ERROR [Broker id=1] 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-02-10 02:00:50,920] ERROR [Broker id=1] 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-02-10 02:00:50,922] ERROR [Broker id=1] 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-02-10 02:00:50,924] ERROR [Broker id=1] 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-02-10 02:00:50,925] ERROR [Broker id=1] 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-02-10 02:00:50,927] ERROR [Broker id=1] 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-02-10 02:00:50,931] ERROR [Broker id=1] 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-02-10 02:00:50,933] ERROR [Broker id=1] 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-02-10 02:00:50,938] ERROR [Broker id=1] 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-02-10 02:00:50,939] ERROR [Broker id=1] 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-02-10 02:00:50,942] ERROR [Broker id=1] 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-02-10 02:00:50,946] ERROR [Broker id=1] 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-02-10 02:00:50,950] ERROR [Broker id=1] 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-02-10 02:00:50,952] ERROR [Broker id=1] 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-02-10 02:00:50,954] ERROR [Broker id=1] 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-02-10 02:00:50,956] ERROR [Broker id=1] 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-02-10 02:00:50,959] ERROR [Broker id=1] 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-02-10 02:00:50,960] ERROR [Broker id=1] 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-02-10 02:00:50,962] ERROR [Broker id=1] 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-02-10 02:00:50,963] ERROR [Broker id=1] 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-02-10 02:00:50,965] ERROR [Broker id=1] 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-02-10 02:00:50,966] ERROR [Broker id=1] 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-02-10 02:00:50,967] ERROR [Broker id=1] 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-02-10 02:00:50,969] ERROR [Broker id=1] 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-02-10 02:00:50,970] ERROR [Broker id=1] 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-02-10 02:00:50,971] ERROR [Broker id=1] 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-02-10 02:00:50,972] ERROR [Broker id=1] 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-02-10 02:00:50,974] ERROR [Broker id=1] 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-02-10 02:00:50,975] ERROR [Broker id=1] 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-02-10 02:00:51,013] ERROR [Broker id=1] 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-02-10 02:00:51,016] ERROR [Broker id=1] 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-02-10 02:00:51,018] ERROR [Broker id=1] 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-02-10 02:00:51,020] ERROR [Broker id=1] 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-02-10 02:00:51,021] ERROR [Broker id=1] 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-02-10 02:00:51,023] ERROR [Broker id=1] 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-02-10 02:00:51,024] ERROR [Broker id=1] 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-02-10 02:00:51,026] ERROR [Broker id=1] 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-02-10 02:00:51,027] ERROR [Broker id=1] 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-02-10 02:00:51,029] ERROR [Broker id=1] 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-02-10 02:00:51,030] ERROR [Broker id=1] 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-02-10 02:00:51,031] ERROR [Broker id=1] 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-02-10 02:00:51,033] ERROR [Broker id=1] 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-02-10 02:00:51,034] ERROR [Broker id=1] 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-02-10 02:00:51,039] ERROR [Broker id=1] 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-02-10 02:00:51,041] ERROR [Broker id=1] 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-02-10 02:00:51,042] ERROR [Broker id=1] 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-02-10 02:00:51,044] ERROR [Broker id=1] 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-02-10 02:00:51,045] ERROR [Broker id=1] 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-02-10 02:00:51,046] ERROR [Broker id=1] 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-02-10 02:00:51,048] ERROR [Broker id=1] 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-02-10 02:00:51,049] ERROR [Broker id=1] 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-02-10 02:00:51,051] ERROR [Broker id=1] 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-02-10 02:00:51,055] INFO [Broker id=1] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 1 for 0 partitions (state.change.logger)
[2025-02-10 02:00:51,118] INFO [Broker id=1] 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-02-10 02:00:51,122] INFO [Broker id=1] Handling LeaderAndIsr request correlationId 3 from controller 2 for 960 partitions (state.change.logger)
[2025-02-10 02:00:51,158] INFO [Broker id=1] Follower -uve-topic-22-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,159] INFO [Broker id=1] Follower -uve-topic-23-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,159] INFO [Broker id=1] Follower -uve-topic-17-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,160] INFO [Broker id=1] Follower -uve-topic-16-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,160] INFO [Broker id=1] Follower -uve-topic-29-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,160] INFO [Broker id=1] Follower -uve-topic-2-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,161] INFO [Broker id=1] Follower -uve-topic-18-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,161] INFO [Broker id=1] Follower -uve-topic-27-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,161] INFO [Broker id=1] Follower -uve-topic-14-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,162] INFO [Broker id=1] Follower -uve-topic-5-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,162] INFO [Broker id=1] Follower -uve-topic-16-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,162] INFO [Broker id=1] Follower -uve-topic-29-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,162] INFO [Broker id=1] Follower -uve-topic-17-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,162] INFO [Broker id=1] Follower -uve-topic-21-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,163] INFO [Broker id=1] Follower -uve-topic-11-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-24-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-13-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-26-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-8-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-0-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-17-0 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-9-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-0-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-20-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,164] INFO [Broker id=1] Follower -uve-topic-1-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-3-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-2-0 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-7-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-6-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-15-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-28-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-6-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-7-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-22-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-0-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-9-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-21-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower structured_syslog_topic-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,165] INFO [Broker id=1] Follower -uve-topic-5-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-4-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-17-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-8-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-3-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-4-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-10-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-23-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-25-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-20-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-12-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-19-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,166] INFO [Broker id=1] Follower -uve-topic-29-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,167] INFO [Broker id=1] Follower -uve-topic-16-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-8-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-21-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-2-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-9-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-18-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-10-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-23-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-14-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-27-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-7-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,168] INFO [Broker id=1] Follower -uve-topic-6-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-8-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-21-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-20-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-0-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-17-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-29-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-16-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,169] INFO [Broker id=1] Follower -uve-topic-4-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-13-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-26-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-6-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-5-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-12-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-26-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-25-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,170] INFO [Broker id=1] Follower -uve-topic-29-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,171] INFO [Broker id=1] Follower -uve-topic-16-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,171] INFO [Broker id=1] Follower -uve-topic-10-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,171] INFO [Broker id=1] Follower -uve-topic-23-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,171] INFO [Broker id=1] Follower -uve-topic-19-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,171] INFO [Broker id=1] Follower -uve-topic-25-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-11-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-24-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-19-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-28-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-15-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-20-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-29-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-16-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-7-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,172] INFO [Broker id=1] Follower -uve-topic-8-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-22-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-18-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-24-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-11-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-17-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-22-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-1-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower structured_syslog_topic-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-5-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-15-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-28-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-20-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-21-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-7-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-3-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-8-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,173] INFO [Broker id=1] Follower -uve-topic-21-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-0-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-24-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-23-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-11-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-10-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-19-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-20-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower -uve-topic-3-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,174] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,175] INFO [Broker id=1] Follower -uve-topic-7-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,175] INFO [Broker id=1] Follower -uve-topic-17-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-16-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-29-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-0-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower structured_syslog_topic-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-9-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-6-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-26-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-13-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-5-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-7-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-8-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-19-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-4-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-25-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-20-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,176] INFO [Broker id=1] Follower -uve-topic-12-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-16-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-29-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-8-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-18-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-1-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-22-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-23-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-10-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-2-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-18-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-27-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-14-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-15-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-28-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-28-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-27-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-14-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-8-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,177] INFO [Broker id=1] Follower -uve-topic-22-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-16-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-15-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-29-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-28-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-21-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-17-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-20-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-21-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower structured_syslog_topic-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-25-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-12-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-24-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-11-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-26-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-13-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-15-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-28-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-20-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-7-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-3-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-19-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-23-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-10-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,178] INFO [Broker id=1] Follower -uve-topic-25-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-12-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-24-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-11-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-15-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-28-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-20-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-6-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-9-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-19-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-18-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-22-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,179] INFO [Broker id=1] Follower -uve-topic-10-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-23-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-18-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-17-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-22-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-14-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-27-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-5-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-21-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-28-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-15-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-16-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-17-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-13-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-12-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-25-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-26-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-14-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-27-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-7-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-2-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-14-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-27-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-28-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-15-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-7-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,180] INFO [Broker id=1] Follower -uve-topic-0-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-1-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-2-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-9-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-8-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower structured_syslog_topic-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-1-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-0-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower structured_syslog_topic-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-4-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-13-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-26-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-6-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-8-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-7-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-20-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-11-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-24-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-29-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-16-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-3-27 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-11-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-4-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-5-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,181] INFO [Broker id=1] Follower -uve-topic-6-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-2-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-1-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-18-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower structured_syslog_topic-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-3-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-2-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-14-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-27-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-28-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-15-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-8-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-1-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-0-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-20-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower structured_syslog_topic-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-9-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-22-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-13-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-12-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-25-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,182] INFO [Broker id=1] Follower -uve-topic-26-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-5-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-12-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-25-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-13-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-26-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-7-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-6-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-28-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-15-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-7-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-19-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-10-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-11-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-24-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower -uve-topic-19-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower structured_syslog_topic-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,183] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-14-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-27-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-10-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-23-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-17-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-9-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-14-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-27-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-6-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-29-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-16-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-21-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-0-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-4-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-8-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-28-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-14-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-27-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-29-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-16-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-10-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-23-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-12-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-25-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-27-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-13-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,184] INFO [Broker id=1] Follower -uve-topic-26-27 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-18-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-9-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-0-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-1-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-2-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower structured_syslog_topic-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-6-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-5-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-14-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-27-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-5-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-13-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-6-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-7-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-8-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-20-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-11-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-24-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-4-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-3-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower structured_syslog_topic-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-5-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-7-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,185] INFO [Broker id=1] Follower -uve-topic-13-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-26-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-6-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-3-24 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-2-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-22-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-19-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower structured_syslog_topic-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-14-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-9-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-8-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-21-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-28-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-15-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-1-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-0-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-17-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower structured_syslog_topic-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-13-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-26-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-4-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower structured_syslog_topic-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-28-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-15-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-0-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-7-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-20-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-28-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-15-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-12-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,186] INFO [Broker id=1] Follower -uve-topic-25-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-3-21 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-19-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-4-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-11-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-24-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower structured_syslog_topic-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-6-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-13-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-26-24 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-14-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-27-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-18-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-22-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-10-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-23-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-6-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-20-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-21-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-16-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-29-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-21-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,187] INFO [Broker id=1] Follower -uve-topic-4-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-27-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-14-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-16-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-29-27 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-2-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-2-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-1-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-3-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-26-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-13-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-5-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-9-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-17-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-1-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-8-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower structured_syslog_topic-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-5-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-22-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-26-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-13-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-5-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-16-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-29-24 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-15-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-28-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-8-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-5-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-4-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,188] INFO [Broker id=1] Follower -uve-topic-24-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-11-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-4-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower structured_syslog_topic-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-5-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-7-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-18-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-1-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-3-18 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-19-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower structured_syslog_topic-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-4-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-25-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-26-21 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-12-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-13-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-4-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-0-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-17-27 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-16-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-29-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-2-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-22-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-9-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-21-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-17-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-26-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-13-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-15-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,189] INFO [Broker id=1] Follower -uve-topic-28-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-20-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-21-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-27-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-14-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-25-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-19-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-20-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-10-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-24-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-23-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-25-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-12-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-27-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-26-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-13-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-14-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-6-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-10-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-22-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-23-27 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-18-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-5-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,190] INFO [Broker id=1] Follower -uve-topic-25-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-12-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-18-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-17-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-20-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-21-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-22-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-17-24 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-16-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-29-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-21-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower structured_syslog_topic-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-20-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-27-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-14-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-16-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-15-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-29-21 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-28-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-25-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-12-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-24-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-11-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-26-18 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-13-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-12-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-13-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-5-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-6-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,191] INFO [Broker id=1] Follower -uve-topic-9-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-1-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-8-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-15-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-28-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-0-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-7-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-4-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-3-15 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-25-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-12-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-19-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower structured_syslog_topic-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-7-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-6-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-10-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-27-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-23-24 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-14-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-2-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-18-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,192] INFO [Broker id=1] Follower -uve-topic-19-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-22-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-24-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-11-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-10-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-23-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-4-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-25-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-12-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-5-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-4-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-17-21 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-0-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-1-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-16-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-2-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-9-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-25-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-12-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,193] INFO [Broker id=1] Follower -uve-topic-4-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-3-3 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-3-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-0-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-15-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-6-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-7-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-8-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-21-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-25-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-12-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-19-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-24-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-11-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-4-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-24-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-11-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-5-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-6-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-27-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-14-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-18-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-19-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-10-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-22-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-23-21 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-18-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-24-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-11-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-26-15 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-13-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-25-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-20-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-12-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,194] INFO [Broker id=1] Follower -uve-topic-22-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-16-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-29-18 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-21-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-8-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-17-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-15-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-28-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-7-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-10-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-23-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-1-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-3-12 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower structured_syslog_topic-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-5-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-4-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-9-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-9-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-19-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-17-18 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-8-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-1-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-0-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-24-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-5-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-7-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-6-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-23-18 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-10-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-3-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-2-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-18-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-19-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-4-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,195] INFO [Broker id=1] Follower -uve-topic-5-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-6-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-25-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-12-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-0-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-4-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-2-27 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-18-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-1-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-9-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-21-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-3-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-23-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-24-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-11-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-15-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-3-0 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-28-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-8-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-20-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-7-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-27-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-14-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-16-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-29-15 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-24-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-11-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-19-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-24-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-11-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-3-9 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower structured_syslog_topic-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-26-12 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-13-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-22-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower -uve-topic-10-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,196] INFO [Broker id=1] Follower structured_syslog_topic-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-5-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-25-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-12-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-24-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-11-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-26-9 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-13-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-17-15 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-20-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-22-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-9-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-19-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-18-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-24-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-23-6 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-11-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-10-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-3-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-19-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-23-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-10-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-15-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-28-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-21-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-6-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-19-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-3-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-26-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-1-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-9-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-0-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-1-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,197] INFO [Broker id=1] Follower -uve-topic-2-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-25-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-12-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-4-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-8-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-0-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-16-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-29-12 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-7-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-8-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-2-15 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-27-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-6-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-7-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-27-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-14-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-2-24 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-24-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-11-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-18-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-3-6 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-23-15 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-10-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-4-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-1-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-6-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-0-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-9-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-16-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-29-9 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-2-21 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-1-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-18-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-3-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-19-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-25-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,198] INFO [Broker id=1] Follower -uve-topic-12-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-24-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-11-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-15-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-29-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-28-8 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-8-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-20-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-21-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-18-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower structured_syslog_topic-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-5-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-27-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-14-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-7-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-20-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-27-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-26-6 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-13-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-14-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-23-12 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-10-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-19-14 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-22-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower structured_syslog_topic-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-24-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-11-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-26-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-25-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-12-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-13-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-21-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,199] INFO [Broker id=1] Follower -uve-topic-17-12 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-9-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-23-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-0-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-10-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-18-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-19-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-23-3 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-10-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-2-12 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-28-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-15-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-2-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-13-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-26-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-12-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-25-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-14-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-27-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-10-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-23-9 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-12-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-25-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-11-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-24-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-4-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-8-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-0-16 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-18-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-2-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-1-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower structured_syslog_topic-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,200] INFO [Broker id=1] Follower -uve-topic-7-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-14-25 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-27-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-6-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-2-18 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-18-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-5-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-9-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-22-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-13-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-26-3 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-1-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-17-9 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-18-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-21-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-20-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-22-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-3-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-19-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-10-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-11-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-23-0 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-24-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-28-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-3-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,201] INFO [Broker id=1] Follower -uve-topic-15-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-19-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-17-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-20-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-29-6 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-16-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-21-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-28-5 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-29-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-15-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-16-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-9-26 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-1-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-23-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-10-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower structured_syslog_topic-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-2-9 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-22-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-18-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-6-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-5-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-14-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-27-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-7-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-20-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-0-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-9-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-1-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-17-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower structured_syslog_topic-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-5-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-4-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-11-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-24-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-13-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,202] INFO [Broker id=1] Follower -uve-topic-12-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-26-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-29-3 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-16-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-17-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-22-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-18-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-21-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-17-6 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-23-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-10-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-12-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-25-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-11-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-19-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-21-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-20-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-28-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-15-23 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-22-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-18-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-14-22 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-13-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-26-0 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-27-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-6-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-1-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-0-13 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-22-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-4-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-3-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,203] INFO [Broker id=1] Follower -uve-topic-9-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-28-2 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-29-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-15-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-16-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-8-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-2-6 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-3-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-9-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-2-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-1-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower structured_syslog_topic-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-22-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-1-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-0-1 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-9-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-4-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-6-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-5-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-9-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-22-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-1-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-17-3 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-3-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-19-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-4-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-5-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-20-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-28-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-3-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-15-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,204] INFO [Broker id=1] Follower -uve-topic-8-28 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-0-10 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-17-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-20-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-29-0 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-16-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-21-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-2-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-9-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-1-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-23-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-10-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-17-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower structured_syslog_topic-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-2-3 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-14-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-27-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-7-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-6-7 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-13-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-26-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-14-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-8-19 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-0-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-21-11 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-12-17 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-25-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-21-20 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-0-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-22-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-9-29 starts at leader epoch 6 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-8-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-29-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-11-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-24-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-18-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-29-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-15-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,205] INFO [Broker id=1] Follower -uve-topic-16-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,206] INFO [Broker id=1] Follower -uve-topic-7-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:51,211] INFO [Broker id=1] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 3 for 960 partitions (state.change.logger)
[2025-02-10 02:00:51,421] INFO [Broker id=1] 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-02-10 02:00:59,642] INFO [Broker id=1] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 5 (state.change.logger)
[2025-02-10 02:05:46,316] INFO [Broker id=1] Handling LeaderAndIsr request correlationId 6 from controller 2 for 320 partitions (state.change.logger)
[2025-02-10 02:05:46,318] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-27-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-5-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-17-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-21-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-26-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-24-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-0-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-28-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-7-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-0-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-4-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-17-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-3-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-10-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-19-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-10-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-27-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-21-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-0-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-26-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-5-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-19-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-28-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-24-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-7-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-17-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-15-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-10-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-19-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,321] INFO [Broker id=1] Follower -uve-topic-0-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,321] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-28-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-14-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-27-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-28-0 starts at leader epoch 8 from offset 124 with high watermark 124. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-21-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-17-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-12-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-24-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-26-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-15-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-19-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-12-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-24-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-28-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-10-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-17-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-14-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-21-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-15-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-14-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-27-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-15-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-9-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-0-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-26-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-14-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-28-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-0-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-12-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-26-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-15-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-10-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-19-0 starts at leader epoch 8 from offset 16 with high watermark 16. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-14-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-9-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] 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-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-27-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-21-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-14-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-12-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-13-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,322] INFO [Broker id=1] Follower -uve-topic-14-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-15-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-9-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-21-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-0-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-15-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-12-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-13-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-14-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-22-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-21-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-16-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-9-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-16-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-15-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-4-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-12-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-13-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-9-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-22-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-21-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-14-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-25-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-12-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-25-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-21-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-16-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-15-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-25-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-12-0 starts at leader epoch 8 from offset 17 with high watermark 17. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-13-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-9-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-12-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] 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-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-7-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,323] INFO [Broker id=1] Follower -uve-topic-14-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-22-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-11-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-4-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-25-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-5-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-1-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-9-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-12-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-4-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-3-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-15-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-7-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-25-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-11-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-11-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-13-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-25-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-16-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-21-0 starts at leader epoch 8 from offset 219 with high watermark 219. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-22-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-5-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-9-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-1-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-24-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-5-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-7-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-3-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-4-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-25-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-3-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-11-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-16-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-11-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-13-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-22-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-5-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-13-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] Follower -uve-topic-11-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,324] INFO [Broker id=1] 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-02-10 02:05:46,324] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-22-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-9-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-19-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-3-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-24-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-10-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-3-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-26-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-1-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-25-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-4-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-7-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-16-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-27-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-11-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-4-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-1-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-9-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-16-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-3-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-11-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-5-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-7-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-13-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-27-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-22-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-24-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-25-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-26-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-10-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-19-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-28-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-25-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-26-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-11-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-4-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-1-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,325] INFO [Broker id=1] 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-02-10 02:05:46,325] INFO [Broker id=1] Follower -uve-topic-7-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-27-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-5-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-13-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-1-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-22-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-19-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-24-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-3-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-28-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-17-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-16-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-10-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-7-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-5-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-0-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-17-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-24-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-4-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-26-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-16-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-17-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-10-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-11-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-19-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-28-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-13-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-27-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-1-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-22-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-3-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-1-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] 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-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-5-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-1-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-19-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-4-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-3-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower HEALTH_CHECK_TOPIC-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-20-0 starts at leader epoch 8 from offset 224 with high watermark 224. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-28-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-16-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,326] INFO [Broker id=1] Follower -uve-topic-17-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-1-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] 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-02-10 02:05:46,327] INFO [Broker id=1] 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-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-10-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-17-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-27-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-26-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-0-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-0-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-22-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-24-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,327] INFO [Broker id=1] 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-02-10 02:05:46,327] INFO [Broker id=1] 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-02-10 02:05:46,327] INFO [Broker id=1] Follower -uve-topic-7-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,357] INFO [Broker id=1] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 6 for 320 partitions (state.change.logger)
[2025-02-10 02:05:46,412] INFO [Broker id=1] Add 320 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-02-10 02:05:46,548] INFO [Broker id=1] Handling LeaderAndIsr request correlationId 8 from controller 2 for 320 partitions (state.change.logger)
[2025-02-10 02:05:46,588] INFO [Broker id=1] Stopped fetchers as part of LeaderAndIsr request correlationId 8 from controller 2 epoch 5 as part of the become-leader transition for 320 partitions (state.change.logger)
[2025-02-10 02:05:46,595] INFO [Broker id=1] Leader -uve-topic-14-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,608] INFO [Broker id=1] Leader -uve-topic-16-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,613] INFO [Broker id=1] Leader -uve-topic-17-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,617] INFO [Broker id=1] Leader -uve-topic-0-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,621] INFO [Broker id=1] Leader -uve-topic-8-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,625] INFO [Broker id=1] Leader -uve-topic-20-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,628] INFO [Broker id=1] Leader -uve-topic-2-0 starts at leader epoch 7 from offset 84 with high watermark 84 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,630] INFO [Broker id=1] Leader -uve-topic-6-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,635] INFO [Broker id=1] Leader -uve-topic-15-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,637] INFO [Broker id=1] Leader -uve-topic-22-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,673] INFO [Broker id=1] Leader -uve-topic-9-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,677] INFO [Broker id=1] Leader -uve-topic-21-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,680] INFO [Broker id=1] Leader -uve-topic-8-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,682] INFO [Broker id=1] Leader -uve-topic-12-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,685] INFO [Broker id=1] Leader -uve-topic-21-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,689] INFO [Broker id=1] Leader -uve-topic-9-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,691] INFO [Broker id=1] Leader -uve-topic-14-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,694] INFO [Broker id=1] Leader -uve-topic-6-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,697] INFO [Broker id=1] Leader -uve-topic-8-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,701] INFO [Broker id=1] Leader -uve-topic-12-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,704] INFO [Broker id=1] Leader -uve-topic-16-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,706] INFO [Broker id=1] Leader -uve-topic-25-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,709] INFO [Broker id=1] Leader -uve-topic-15-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,712] INFO [Broker id=1] Leader -uve-topic-8-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,714] INFO [Broker id=1] Leader -uve-topic-22-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,717] INFO [Broker id=1] Leader -uve-topic-11-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,719] INFO [Broker id=1] Leader -uve-topic-20-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,722] INFO [Broker id=1] Leader -uve-topic-21-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,725] INFO [Broker id=1] Leader -uve-topic-21-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,727] INFO [Broker id=1] Leader -uve-topic-0-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,729] INFO [Broker id=1] Leader -uve-topic-11-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,732] INFO [Broker id=1] Leader -uve-topic-20-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,735] INFO [Broker id=1] Leader -uve-topic-9-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,737] INFO [Broker id=1] Leader structured_syslog_topic-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,740] INFO [Broker id=1] Leader -uve-topic-13-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,743] INFO [Broker id=1] Leader -uve-topic-7-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,745] INFO [Broker id=1] Leader -uve-topic-8-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,748] INFO [Broker id=1] Leader -uve-topic-12-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,756] INFO [Broker id=1] Leader -uve-topic-15-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,759] INFO [Broker id=1] Leader -uve-topic-14-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,762] INFO [Broker id=1] Leader -uve-topic-16-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,773] INFO [Broker id=1] Leader -uve-topic-15-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,777] INFO [Broker id=1] Leader -uve-topic-21-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,780] INFO [Broker id=1] Leader -uve-topic-22-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,782] INFO [Broker id=1] Leader -uve-topic-25-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,785] INFO [Broker id=1] Leader -uve-topic-20-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,787] INFO [Broker id=1] Leader -uve-topic-25-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,790] INFO [Broker id=1] Leader -uve-topic-15-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,794] INFO [Broker id=1] Leader -uve-topic-22-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,796] INFO [Broker id=1] Leader -uve-topic-9-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,799] INFO [Broker id=1] Leader -uve-topic-13-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,802] INFO [Broker id=1] Leader -uve-topic-12-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,808] INFO [Broker id=1] Leader -uve-topic-7-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,815] INFO [Broker id=1] Leader -uve-topic-14-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,819] INFO [Broker id=1] Leader -uve-topic-8-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,823] INFO [Broker id=1] Leader structured_syslog_topic-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,827] INFO [Broker id=1] Leader -uve-topic-1-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,830] INFO [Broker id=1] Leader -uve-topic-20-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,832] INFO [Broker id=1] Leader -uve-topic-11-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,835] INFO [Broker id=1] Leader -uve-topic-16-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,838] INFO [Broker id=1] Leader -uve-topic-3-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,841] INFO [Broker id=1] Leader -uve-topic-5-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,844] INFO [Broker id=1] Leader -uve-topic-15-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,847] INFO [Broker id=1] Leader structured_syslog_topic-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,854] INFO [Broker id=1] Leader -uve-topic-1-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,858] INFO [Broker id=1] Leader -uve-topic-20-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,861] INFO [Broker id=1] Leader -uve-topic-22-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,864] INFO [Broker id=1] Leader -uve-topic-9-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,867] INFO [Broker id=1] Leader -uve-topic-13-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,872] INFO [Broker id=1] Leader -uve-topic-12-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,876] INFO [Broker id=1] Leader -uve-topic-25-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,882] INFO [Broker id=1] Leader -uve-topic-7-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,887] INFO [Broker id=1] Leader -uve-topic-11-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,890] INFO [Broker id=1] Leader structured_syslog_topic-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,893] INFO [Broker id=1] Leader -uve-topic-14-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,897] INFO [Broker id=1] Leader -uve-topic-16-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,900] INFO [Broker id=1] Leader -uve-topic-8-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,903] INFO [Broker id=1] Leader -uve-topic-4-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,905] INFO [Broker id=1] Leader -uve-topic-28-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,908] INFO [Broker id=1] Leader -uve-topic-16-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,911] INFO [Broker id=1] Leader -uve-topic-25-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,913] INFO [Broker id=1] Leader -uve-topic-27-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,916] INFO [Broker id=1] Leader -uve-topic-26-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,918] INFO [Broker id=1] Leader -uve-topic-9-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,921] INFO [Broker id=1] Leader -uve-topic-5-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,924] INFO [Broker id=1] Leader -uve-topic-20-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,926] INFO [Broker id=1] Leader -uve-topic-11-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,929] INFO [Broker id=1] Leader -uve-topic-4-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,932] INFO [Broker id=1] Leader structured_syslog_topic-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,937] INFO [Broker id=1] Leader -uve-topic-5-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,945] INFO [Broker id=1] Leader -uve-topic-13-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,949] INFO [Broker id=1] Leader -uve-topic-7-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,952] INFO [Broker id=1] Leader -uve-topic-3-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,955] INFO [Broker id=1] Leader -uve-topic-22-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,957] INFO [Broker id=1] Leader -uve-topic-14-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,960] INFO [Broker id=1] Leader -uve-topic-8-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,963] INFO [Broker id=1] Leader -uve-topic-1-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,965] INFO [Broker id=1] Leader structured_syslog_topic-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,968] INFO [Broker id=1] Leader -uve-topic-13-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,971] INFO [Broker id=1] Leader structured_syslog_topic-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,975] INFO [Broker id=1] Leader -uve-topic-28-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,977] INFO [Broker id=1] Leader -uve-topic-7-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,980] INFO [Broker id=1] Leader -uve-topic-25-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,983] INFO [Broker id=1] Leader -uve-topic-3-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,987] INFO [Broker id=1] Leader -uve-topic-11-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,989] INFO [Broker id=1] Leader -uve-topic-26-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,992] INFO [Broker id=1] Leader -uve-topic-20-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,998] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,000] INFO [Broker id=1] Leader -uve-topic-16-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,003] INFO [Broker id=1] Leader -uve-topic-4-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,005] INFO [Broker id=1] Leader -uve-topic-27-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,008] INFO [Broker id=1] Leader -uve-topic-29-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,010] INFO [Broker id=1] Leader -uve-topic-5-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,013] INFO [Broker id=1] Leader -uve-topic-13-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,017] INFO [Broker id=1] Leader -uve-topic-1-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,020] INFO [Broker id=1] Leader -uve-topic-5-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,023] INFO [Broker id=1] Leader structured_syslog_topic-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,026] INFO [Broker id=1] Leader -uve-topic-22-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,028] INFO [Broker id=1] Leader -uve-topic-13-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,031] INFO [Broker id=1] Leader -uve-topic-29-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,034] INFO [Broker id=1] Leader -uve-topic-5-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,036] INFO [Broker id=1] Leader -uve-topic-11-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,039] INFO [Broker id=1] Leader -uve-topic-4-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,041] INFO [Broker id=1] Leader -uve-topic-5-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,043] INFO [Broker id=1] Leader structured_syslog_topic-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,046] INFO [Broker id=1] Leader -uve-topic-7-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,049] INFO [Broker id=1] Leader -uve-topic-18-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,051] INFO [Broker id=1] Leader -uve-topic-1-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,055] INFO [Broker id=1] Leader -uve-topic-3-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,059] INFO [Broker id=1] Leader -uve-topic-4-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,064] INFO [Broker id=1] Leader -uve-topic-26-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,067] INFO [Broker id=1] Leader -uve-topic-25-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,071] INFO [Broker id=1] Leader -uve-topic-17-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,074] INFO [Broker id=1] Leader -uve-topic-16-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,077] INFO [Broker id=1] Leader -uve-topic-13-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,079] INFO [Broker id=1] Leader -uve-topic-28-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,082] INFO [Broker id=1] Leader -uve-topic-20-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,085] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,088] INFO [Broker id=1] Leader -uve-topic-19-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,092] INFO [Broker id=1] Leader -uve-topic-24-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,095] INFO [Broker id=1] Leader -uve-topic-25-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,097] INFO [Broker id=1] Leader -uve-topic-27-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,100] INFO [Broker id=1] Leader -uve-topic-13-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,102] INFO [Broker id=1] Leader -uve-topic-10-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,105] INFO [Broker id=1] Leader -uve-topic-22-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,107] INFO [Broker id=1] Leader -uve-topic-23-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,110] INFO [Broker id=1] Leader -uve-topic-18-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,113] INFO [Broker id=1] Leader -uve-topic-20-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,115] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,118] INFO [Broker id=1] Leader -uve-topic-17-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,120] INFO [Broker id=1] Leader -uve-topic-16-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,123] INFO [Broker id=1] Leader -uve-topic-22-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,126] INFO [Broker id=1] Leader structured_syslog_topic-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,130] INFO [Broker id=1] Leader -uve-topic-27-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,133] INFO [Broker id=1] Leader -uve-topic-29-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,136] INFO [Broker id=1] Leader -uve-topic-11-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,140] INFO [Broker id=1] Leader -uve-topic-26-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,143] INFO [Broker id=1] Leader -uve-topic-5-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,146] INFO [Broker id=1] Leader -uve-topic-6-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,150] INFO [Broker id=1] Leader -uve-topic-13-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,153] INFO [Broker id=1] Leader -uve-topic-1-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,156] INFO [Broker id=1] Leader -uve-topic-28-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,158] INFO [Broker id=1] Leader -uve-topic-4-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,161] INFO [Broker id=1] Leader -uve-topic-7-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,164] INFO [Broker id=1] Leader -uve-topic-25-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,167] INFO [Broker id=1] Leader -uve-topic-3-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,175] INFO [Broker id=1] Leader -uve-topic-10-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,179] INFO [Broker id=1] Leader -uve-topic-23-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,182] INFO [Broker id=1] Leader -uve-topic-19-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,184] INFO [Broker id=1] Leader -uve-topic-24-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,187] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,190] INFO [Broker id=1] Leader -uve-topic-4-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,192] INFO [Broker id=1] Leader -uve-topic-17-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,195] INFO [Broker id=1] Leader -uve-topic-16-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,198] INFO [Broker id=1] Leader -uve-topic-25-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,202] INFO [Broker id=1] Leader -uve-topic-3-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,205] INFO [Broker id=1] Leader -uve-topic-0-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,207] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,211] INFO [Broker id=1] Leader -uve-topic-19-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,214] INFO [Broker id=1] Leader -uve-topic-4-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,216] INFO [Broker id=1] Leader -uve-topic-11-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,219] INFO [Broker id=1] Leader -uve-topic-24-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,223] INFO [Broker id=1] Leader -uve-topic-5-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,225] INFO [Broker id=1] Leader -uve-topic-6-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,229] INFO [Broker id=1] Leader -uve-topic-27-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,232] INFO [Broker id=1] Leader -uve-topic-18-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,237] INFO [Broker id=1] Leader -uve-topic-10-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,240] INFO [Broker id=1] Leader -uve-topic-22-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,243] INFO [Broker id=1] Leader -uve-topic-23-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,246] INFO [Broker id=1] Leader -uve-topic-24-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,250] INFO [Broker id=1] Leader -uve-topic-26-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,252] INFO [Broker id=1] Leader -uve-topic-29-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,255] INFO [Broker id=1] Leader -uve-topic-28-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,258] INFO [Broker id=1] Leader -uve-topic-7-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,268] INFO [Broker id=1] Leader -uve-topic-1-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,272] INFO [Broker id=1] Leader -uve-topic-3-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,274] INFO [Broker id=1] Leader -uve-topic-4-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,278] INFO [Broker id=1] Leader -uve-topic-19-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,283] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,286] INFO [Broker id=1] Leader -uve-topic-17-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,289] INFO [Broker id=1] Leader -uve-topic-23-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,293] INFO [Broker id=1] Leader -uve-topic-10-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,298] INFO [Broker id=1] Leader -uve-topic-19-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,301] INFO [Broker id=1] Leader -uve-topic-6-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,304] INFO [Broker id=1] Leader -uve-topic-5-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,306] INFO [Broker id=1] Leader -uve-topic-0-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,309] INFO [Broker id=1] Leader -uve-topic-4-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,312] INFO [Broker id=1] Leader -uve-topic-1-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,314] INFO [Broker id=1] Leader -uve-topic-2-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,317] INFO [Broker id=1] Leader -uve-topic-18-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,319] INFO [Broker id=1] Leader -uve-topic-24-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,322] INFO [Broker id=1] Leader -uve-topic-3-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,326] INFO [Broker id=1] Leader -uve-topic-28-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,328] INFO [Broker id=1] Leader -uve-topic-27-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,331] INFO [Broker id=1] Leader -uve-topic-7-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,334] INFO [Broker id=1] Leader -uve-topic-24-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,337] INFO [Broker id=1] Leader -uve-topic-29-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,340] INFO [Broker id=1] Leader -uve-topic-11-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,343] INFO [Broker id=1] Leader -uve-topic-3-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,346] INFO [Broker id=1] Leader -uve-topic-26-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,351] INFO [Broker id=1] Leader -uve-topic-12-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,354] INFO [Broker id=1] Leader -uve-topic-24-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,357] INFO [Broker id=1] Leader -uve-topic-26-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,360] INFO [Broker id=1] Leader -uve-topic-17-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,363] INFO [Broker id=1] Leader -uve-topic-23-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,365] INFO [Broker id=1] Leader -uve-topic-10-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,368] INFO [Broker id=1] Leader -uve-topic-19-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,371] INFO [Broker id=1] Leader -uve-topic-28-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,375] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,377] INFO [Broker id=1] Leader -uve-topic-19-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,380] INFO [Broker id=1] Leader -uve-topic-1-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,385] INFO [Broker id=1] Leader -uve-topic-0-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,388] INFO [Broker id=1] Leader -uve-topic-29-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,391] INFO [Broker id=1] Leader -uve-topic-2-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,394] INFO [Broker id=1] Leader -uve-topic-6-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,396] INFO [Broker id=1] Leader -uve-topic-27-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,400] INFO [Broker id=1] Leader -uve-topic-7-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,405] INFO [Broker id=1] Leader -uve-topic-2-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,408] INFO [Broker id=1] Leader -uve-topic-24-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,410] INFO [Broker id=1] Leader -uve-topic-18-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,416] INFO [Broker id=1] Leader -uve-topic-3-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,421] INFO [Broker id=1] Leader -uve-topic-23-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,423] INFO [Broker id=1] Leader -uve-topic-10-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,426] INFO [Broker id=1] Leader -uve-topic-6-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,428] INFO [Broker id=1] Leader -uve-topic-0-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,432] INFO [Broker id=1] Leader -uve-topic-29-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,435] INFO [Broker id=1] Leader -uve-topic-1-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,438] INFO [Broker id=1] Leader -uve-topic-2-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,440] INFO [Broker id=1] Leader -uve-topic-18-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,443] INFO [Broker id=1] Leader -uve-topic-12-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,445] INFO [Broker id=1] Leader -uve-topic-19-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,448] INFO [Broker id=1] Leader -uve-topic-24-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,451] INFO [Broker id=1] Leader -uve-topic-28-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,454] INFO [Broker id=1] Leader -uve-topic-21-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,456] INFO [Broker id=1] Leader -uve-topic-27-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,461] INFO [Broker id=1] Leader -uve-topic-23-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,485] INFO [Broker id=1] Leader -uve-topic-26-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,493] INFO [Broker id=1] Leader -uve-topic-14-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,503] INFO [Broker id=1] Leader -uve-topic-10-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,509] INFO [Broker id=1] Leader -uve-topic-19-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,523] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,528] INFO [Broker id=1] Leader -uve-topic-17-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,532] INFO [Broker id=1] Leader -uve-topic-18-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,548] INFO [Broker id=1] Leader -uve-topic-2-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,551] INFO [Broker id=1] Leader -uve-topic-23-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,554] INFO [Broker id=1] Leader -uve-topic-10-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,563] INFO [Broker id=1] Leader -uve-topic-15-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,568] INFO [Broker id=1] Leader -uve-topic-27-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,571] INFO [Broker id=1] Leader -uve-topic-23-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,574] INFO [Broker id=1] Leader -uve-topic-10-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,582] INFO [Broker id=1] Leader -uve-topic-12-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,587] INFO [Broker id=1] Leader -uve-topic-24-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,590] INFO [Broker id=1] Leader -uve-topic-0-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,593] INFO [Broker id=1] Leader -uve-topic-14-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,596] INFO [Broker id=1] Leader -uve-topic-6-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,598] INFO [Broker id=1] Leader -uve-topic-2-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,600] INFO [Broker id=1] Leader -uve-topic-18-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,603] INFO [Broker id=1] Leader -uve-topic-26-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,606] INFO [Broker id=1] Leader -uve-topic-17-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,610] INFO [Broker id=1] Leader -uve-topic-21-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,612] INFO [Broker id=1] Leader -uve-topic-23-0 starts at leader epoch 7 from offset 40 with high watermark 40 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,615] INFO [Broker id=1] Leader -uve-topic-10-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,619] INFO [Broker id=1] Leader -uve-topic-19-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,622] INFO [Broker id=1] Leader -uve-topic-15-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,625] INFO [Broker id=1] Leader -uve-topic-29-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,628] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,631] INFO [Broker id=1] Leader -uve-topic-28-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,633] INFO [Broker id=1] Leader -uve-topic-9-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,637] INFO [Broker id=1] Leader -uve-topic-2-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,642] INFO [Broker id=1] Leader -uve-topic-18-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,645] INFO [Broker id=1] Leader -uve-topic-27-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,649] INFO [Broker id=1] Leader -uve-topic-9-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,652] INFO [Broker id=1] Leader -uve-topic-29-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,654] INFO [Broker id=1] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,658] INFO [Broker id=1] Leader -uve-topic-18-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,664] INFO [Broker id=1] Leader -uve-topic-17-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,668] INFO [Broker id=1] Leader -uve-topic-12-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,671] INFO [Broker id=1] Leader -uve-topic-21-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,674] INFO [Broker id=1] Leader -uve-topic-15-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,676] INFO [Broker id=1] Leader -uve-topic-26-0 starts at leader epoch 7 from offset 163 with high watermark 163 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,679] INFO [Broker id=1] Leader -uve-topic-14-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,681] INFO [Broker id=1] Leader -uve-topic-6-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,685] INFO [Broker id=1] Leader -uve-topic-0-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,688] INFO [Broker id=1] Leader -uve-topic-28-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,690] INFO [Broker id=1] Leader -uve-topic-2-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,693] INFO [Broker id=1] Leader -uve-topic-0-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,696] INFO [Broker id=1] Leader -uve-topic-17-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,699] INFO [Broker id=1] Leader -uve-topic-15-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,703] INFO [Broker id=1] Leader -uve-topic-8-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,706] INFO [Broker id=1] Leader -uve-topic-0-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,709] INFO [Broker id=1] Leader -uve-topic-29-0 starts at leader epoch 7 from offset 69 with high watermark 69 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,714] INFO [Broker id=1] Leader -uve-topic-9-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,722] INFO [Broker id=1] Leader -uve-topic-2-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,726] INFO [Broker id=1] Leader -uve-topic-14-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,729] INFO [Broker id=1] Leader -uve-topic-6-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,732] INFO [Broker id=1] Leader -uve-topic-8-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,736] INFO [Broker id=1] Leader -uve-topic-21-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,738] INFO [Broker id=1] Leader -uve-topic-12-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,741] INFO [Broker id=1] Leader -uve-topic-21-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,745] INFO [Broker id=1] Leader -uve-topic-9-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3,2,1] addingReplicas [] removingReplicas []. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:47,756] INFO [Broker id=1] 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)