[2025-02-10 02:00:41,283] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 0 (state.change.logger)
[2025-02-10 02:00:41,331] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 1 from controller 2 for 960 partitions (state.change.logger)
[2025-02-10 02:00:41,643] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,734] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,738] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,743] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,747] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,751] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,755] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,758] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,762] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,765] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,770] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,774] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,778] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,783] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,786] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,791] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,798] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,802] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,805] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,808] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,811] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,814] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,817] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,820] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,823] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,826] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,829] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,832] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,835] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,839] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,842] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,845] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,849] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,852] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,857] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,860] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,863] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,866] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,869] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,873] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,877] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,880] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,883] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,886] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,890] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,895] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,898] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,901] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,904] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,907] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,910] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,913] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,917] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,919] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,923] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,927] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,930] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,933] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,935] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,940] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,943] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,949] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,952] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,955] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,958] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,961] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,965] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,967] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,970] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,973] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,975] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,980] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,983] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,987] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,990] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:41,999] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,002] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,005] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,013] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,015] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,018] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,021] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,024] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,028] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,031] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,033] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,036] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,039] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,041] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,044] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,047] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,054] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,059] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,063] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,067] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,073] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,077] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,084] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,089] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,092] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,097] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,103] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,106] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,120] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,130] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,136] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,141] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,145] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,148] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,157] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,161] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,163] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,166] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,169] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,172] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,174] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,194] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,197] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,200] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,204] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,206] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,209] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,211] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,214] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,217] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,220] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,222] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,231] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,234] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,236] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,238] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,240] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,246] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,248] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,250] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,252] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,254] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,256] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,258] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,260] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,262] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,264] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,268] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,270] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,272] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,274] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,277] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,279] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,283] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,285] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,289] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,292] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,296] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,300] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,306] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,311] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,317] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,320] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,322] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,325] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,327] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,329] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,333] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,335] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,342] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,347] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,354] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,360] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,363] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,366] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,369] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,371] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,375] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,377] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,380] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,382] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,384] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,388] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,390] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,393] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,395] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,397] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,401] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,403] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,408] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,411] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,412] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,417] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,422] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,426] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,428] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,429] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,432] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,434] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,437] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,439] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,441] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,444] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,447] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,449] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,455] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,459] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,461] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,463] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,465] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,467] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,469] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,471] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,481] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,484] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,486] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,488] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,490] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,491] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,493] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,495] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,497] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,499] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,502] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,505] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,508] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,510] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,511] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,513] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,515] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,517] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,519] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,521] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,522] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,524] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,526] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,528] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,530] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,531] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,533] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,535] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,536] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,538] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,540] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,542] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,543] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,545] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,547] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,549] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,551] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,553] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,555] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,557] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,559] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,562] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,564] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,566] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,568] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,570] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,572] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,584] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,591] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,595] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,598] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,603] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,607] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,609] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,611] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,613] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,615] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,617] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,619] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,622] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,624] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,626] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,627] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,629] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,631] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,634] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,636] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,637] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,640] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,642] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,643] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,645] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,647] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,649] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,651] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,660] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,662] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,664] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,666] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,667] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,669] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,671] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,672] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,674] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,676] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,677] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,679] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,681] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,682] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,684] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,685] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,688] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,689] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,691] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,692] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,694] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,696] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,697] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,699] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,700] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,702] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,703] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,705] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,706] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,708] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,709] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,711] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,712] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,714] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,715] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,717] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,718] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,720] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,722] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,724] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,725] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,727] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,728] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,730] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,732] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,735] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,737] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,738] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,740] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,742] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,743] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,745] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,746] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,748] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,750] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,752] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,754] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,756] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,757] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,759] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,761] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,762] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,764] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,766] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,767] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,769] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,770] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,772] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,773] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,775] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,776] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,778] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,780] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,782] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,783] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,785] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,787] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,789] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,790] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,795] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,796] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,798] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,800] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,801] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,802] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,804] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,806] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,808] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,809] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,835] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,837] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,839] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,840] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,842] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,843] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,845] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,847] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,849] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,851] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,853] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,855] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,857] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,858] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,860] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,862] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,863] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,865] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,866] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,868] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,869] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,871] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,872] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,874] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,875] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,877] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,879] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,880] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,882] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,883] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,885] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,886] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,888] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,890] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,891] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,893] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,894] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,896] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,898] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,899] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,901] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,903] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,904] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,906] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,908] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,909] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,911] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,912] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,914] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,915] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,917] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,918] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,920] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,921] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,923] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,924] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,926] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,927] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,929] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,930] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,932] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,933] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,935] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,936] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,938] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,939] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,941] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,942] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,944] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,945] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,947] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,956] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,959] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,961] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,962] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,964] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,966] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,967] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,969] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,970] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,972] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,974] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,975] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,976] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,978] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,979] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,981] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,983] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,984] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,986] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,987] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,989] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,990] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,992] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,994] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,995] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,997] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:42,998] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,000] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,001] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,003] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,004] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,006] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,007] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,009] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,010] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,012] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,014] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,015] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,018] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,019] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,021] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,022] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,024] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,025] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,027] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,028] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,030] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,031] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,033] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,034] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,035] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,037] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,038] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,040] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,041] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,043] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,045] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,047] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,048] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,050] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,052] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,054] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,055] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,057] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,059] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,061] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,062] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,064] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,066] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,069] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,070] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,072] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,073] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,075] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,076] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,079] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,083] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,085] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,086] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,088] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,089] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,091] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,094] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,096] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,101] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,103] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,104] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,106] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,107] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,109] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,111] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,113] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,114] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,120] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,122] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,124] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,125] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,127] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,128] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,130] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,131] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,133] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,134] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,136] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,137] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,139] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,140] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,142] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,143] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,145] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,146] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,148] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,150] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,153] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,154] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,157] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,161] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,178] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,187] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,191] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,195] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,197] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,199] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,200] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,203] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,204] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,206] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,207] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,209] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,210] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,212] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,213] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,215] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,216] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,218] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,220] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,224] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,237] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,239] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,240] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,244] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,248] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,250] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,252] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,254] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,255] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,257] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,258] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,260] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,261] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,263] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,265] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,266] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,268] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,269] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,271] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,272] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,274] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,275] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,277] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,278] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,280] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,281] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,283] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,285] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,286] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,288] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,290] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,291] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,293] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,294] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,296] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,297] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,298] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,300] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,301] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,303] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,304] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,305] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,307] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,308] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,310] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,311] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,313] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,314] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,316] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,317] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,319] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,320] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,322] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,323] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,324] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,326] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,327] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,328] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,330] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,331] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,333] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,335] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,336] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,338] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,340] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,343] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,345] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,346] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,347] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,349] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,350] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,351] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,353] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,354] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,355] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,357] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,358] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,360] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,361] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,362] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,364] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,365] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,367] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,369] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,371] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,372] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,388] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,392] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,394] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,396] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,398] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,399] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,401] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,402] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,404] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,405] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,407] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,408] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,410] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,411] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,413] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,414] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,416] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,417] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,419] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,421] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,422] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,424] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,426] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,427] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,429] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,431] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,432] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,433] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,435] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,437] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,438] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,440] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,441] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,443] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,444] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,445] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,447] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,448] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,449] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,451] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,452] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,454] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,455] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,456] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,457] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,459] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,460] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,461] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,462] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,463] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,465] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,466] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,467] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,468] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,470] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,471] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,473] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,474] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,475] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,477] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,478] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,479] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,481] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,482] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,483] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,484] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,486] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,487] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,488] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,490] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,491] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,492] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,494] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,496] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,498] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,499] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,500] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,502] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,504] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,505] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,507] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,509] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,510] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,512] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,513] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,515] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,516] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,518] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,519] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,520] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,522] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,523] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,525] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,526] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,528] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,530] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,532] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,533] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,535] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,536] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,538] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,539] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,541] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,542] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,544] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,545] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,547] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,549] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,550] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,553] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,554] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,556] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,558] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,559] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,561] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,562] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,564] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,566] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,567] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,569] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,571] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,572] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,574] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,575] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,577] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,578] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,580] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,582] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,583] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,585] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,586] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,588] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,590] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,591] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,593] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,596] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,597] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,599] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,600] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,602] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,604] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,606] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,608] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,610] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,612] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,614] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,615] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,617] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,620] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,621] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,623] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,625] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,626] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,628] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,630] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,631] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,633] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,634] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,636] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,638] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,643] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,645] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,646] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,647] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,651] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,653] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,654] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,655] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,657] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,658] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,660] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,661] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,662] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,664] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,665] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,667] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,669] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,671] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,674] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,676] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,678] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,680] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,682] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,683] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,685] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,686] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,687] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,689] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,690] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,692] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,693] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,694] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,696] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,697] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,698] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,699] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,701] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,703] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,705] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,707] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,708] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,709] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,711] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,713] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,714] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,715] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,716] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,718] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,719] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,720] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,721] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,723] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,724] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,725] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,727] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,728] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,729] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,731] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,766] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,768] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,769] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,786] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,793] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,799] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,802] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,803] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,805] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,806] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,809] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,811] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,815] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,816] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,821] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,823] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,825] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-12 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,827] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,829] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,830] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,831] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-24 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,833] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-26 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,834] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-6 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,835] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,837] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,838] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,840] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,842] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-23 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,843] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-19-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,844] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-4-5 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,846] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-5-25 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,847] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,854] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-28-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,857] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-3-4 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,858] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,860] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition HEALTH_CHECK_TOPIC-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,862] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-28 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,863] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-10 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,864] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,865] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-20-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,867] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,868] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,869] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,871] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-22 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,872] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,873] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-1-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,875] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-23-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,876] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-10-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,878] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-17-13 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,879] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition structured_syslog_topic-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,880] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-2-3 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,882] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,883] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-27-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,885] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-27 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,886] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-6-7 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,888] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-13-18 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,890] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-26-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,891] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-14-0 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,892] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,894] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,895] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-11 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,896] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-12-17 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,897] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-25-15 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,899] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-21-20 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,901] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-0-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,902] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-22-2 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,903] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-9-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,905] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-8-9 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,906] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-29 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,907] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-11-16 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,908] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-24-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,911] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-18-14 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,912] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-29-19 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,913] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-15-1 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,914] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-16-21 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,916] ERROR [Broker id=3] Received LeaderAndIsrRequest with correlation id 1 from controller 2 epoch 5 for partition -uve-topic-7-8 (last update controller epoch 5) but cannot become follower since the new leader -1 is unavailable. (state.change.logger)
[2025-02-10 02:00:43,919] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 1 for 0 partitions (state.change.logger)
[2025-02-10 02:00:43,958] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 2 (state.change.logger)
[2025-02-10 02:00:43,965] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 3 from controller 2 for 960 partitions (state.change.logger)
[2025-02-10 02:00:43,976] INFO [Broker id=3] Stopped fetchers as part of LeaderAndIsr request correlationId 3 from controller 2 epoch 5 as part of the become-leader transition for 960 partitions (state.change.logger)
[2025-02-10 02:00:43,982] INFO [Broker id=3] Leader -uve-topic-22-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:43,994] INFO [Broker id=3] Leader -uve-topic-23-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:43,998] INFO [Broker id=3] Leader -uve-topic-17-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,002] INFO [Broker id=3] Leader -uve-topic-16-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,005] INFO [Broker id=3] Leader -uve-topic-29-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,008] INFO [Broker id=3] Leader -uve-topic-2-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,011] INFO [Broker id=3] Leader -uve-topic-18-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,015] INFO [Broker id=3] Leader -uve-topic-27-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,017] INFO [Broker id=3] Leader -uve-topic-14-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,020] INFO [Broker id=3] Leader -uve-topic-5-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,023] INFO [Broker id=3] Leader -uve-topic-16-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,026] INFO [Broker id=3] Leader -uve-topic-29-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,030] INFO [Broker id=3] Leader -uve-topic-17-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,032] INFO [Broker id=3] Leader -uve-topic-21-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,035] INFO [Broker id=3] Leader -uve-topic-11-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,038] INFO [Broker id=3] Leader -uve-topic-24-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,040] INFO [Broker id=3] Leader -uve-topic-13-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,043] INFO [Broker id=3] Leader -uve-topic-26-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,045] INFO [Broker id=3] Leader -uve-topic-8-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,047] INFO [Broker id=3] Leader -uve-topic-0-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,050] INFO [Broker id=3] Leader -uve-topic-17-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,052] INFO [Broker id=3] Leader -uve-topic-9-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,055] INFO [Broker id=3] Leader -uve-topic-0-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,057] INFO [Broker id=3] Leader -uve-topic-20-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,060] INFO [Broker id=3] Leader -uve-topic-1-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,063] INFO [Broker id=3] Leader -uve-topic-3-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,065] INFO [Broker id=3] Leader -uve-topic-2-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,068] INFO [Broker id=3] Leader -uve-topic-7-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,071] INFO [Broker id=3] Leader -uve-topic-6-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,073] INFO [Broker id=3] Leader -uve-topic-15-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,077] INFO [Broker id=3] Leader -uve-topic-28-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,080] INFO [Broker id=3] Leader -uve-topic-6-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,083] INFO [Broker id=3] Leader -uve-topic-7-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,085] INFO [Broker id=3] Leader -uve-topic-22-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,088] INFO [Broker id=3] Leader -uve-topic-0-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,090] INFO [Broker id=3] Leader -uve-topic-9-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,093] INFO [Broker id=3] Leader -uve-topic-21-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,095] INFO [Broker id=3] Leader structured_syslog_topic-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,098] INFO [Broker id=3] Leader -uve-topic-5-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,100] INFO [Broker id=3] Leader -uve-topic-4-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,102] INFO [Broker id=3] Leader -uve-topic-17-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,105] INFO [Broker id=3] Leader -uve-topic-8-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,107] INFO [Broker id=3] Leader -uve-topic-3-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,110] INFO [Broker id=3] Leader -uve-topic-4-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,112] INFO [Broker id=3] Leader -uve-topic-10-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,115] INFO [Broker id=3] Leader -uve-topic-23-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,117] INFO [Broker id=3] Leader -uve-topic-25-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,120] INFO [Broker id=3] Leader -uve-topic-20-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,122] INFO [Broker id=3] Leader -uve-topic-12-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,125] INFO [Broker id=3] Leader -uve-topic-19-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,128] INFO [Broker id=3] Leader -uve-topic-29-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,130] INFO [Broker id=3] Leader -uve-topic-16-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,133] INFO [Broker id=3] Leader -uve-topic-8-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,135] INFO [Broker id=3] Leader -uve-topic-21-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,138] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,140] INFO [Broker id=3] Leader -uve-topic-2-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,143] INFO [Broker id=3] Leader -uve-topic-9-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,146] INFO [Broker id=3] Leader -uve-topic-18-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,148] INFO [Broker id=3] Leader -uve-topic-10-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,151] INFO [Broker id=3] Leader -uve-topic-23-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,153] INFO [Broker id=3] Leader -uve-topic-14-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,156] INFO [Broker id=3] Leader -uve-topic-27-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,158] INFO [Broker id=3] Leader -uve-topic-7-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,161] INFO [Broker id=3] Leader -uve-topic-6-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,164] INFO [Broker id=3] Leader -uve-topic-8-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,167] INFO [Broker id=3] Leader -uve-topic-21-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,170] INFO [Broker id=3] Leader -uve-topic-20-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,172] INFO [Broker id=3] Leader -uve-topic-0-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,175] INFO [Broker id=3] Leader -uve-topic-17-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,178] INFO [Broker id=3] Leader -uve-topic-29-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,180] INFO [Broker id=3] Leader -uve-topic-16-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,183] INFO [Broker id=3] Leader -uve-topic-4-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,186] INFO [Broker id=3] Leader -uve-topic-13-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,189] INFO [Broker id=3] Leader -uve-topic-26-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,191] INFO [Broker id=3] Leader -uve-topic-6-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,194] INFO [Broker id=3] Leader -uve-topic-5-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,197] INFO [Broker id=3] Leader -uve-topic-12-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,199] INFO [Broker id=3] Leader -uve-topic-26-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,202] INFO [Broker id=3] Leader -uve-topic-25-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,205] INFO [Broker id=3] Leader -uve-topic-29-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,209] INFO [Broker id=3] Leader -uve-topic-16-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,211] INFO [Broker id=3] Leader -uve-topic-10-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,214] INFO [Broker id=3] Leader -uve-topic-23-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,216] INFO [Broker id=3] Leader -uve-topic-19-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,218] INFO [Broker id=3] Leader -uve-topic-25-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,221] INFO [Broker id=3] Leader -uve-topic-11-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,223] INFO [Broker id=3] Leader -uve-topic-24-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,226] INFO [Broker id=3] Leader -uve-topic-19-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,229] INFO [Broker id=3] Leader -uve-topic-28-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,231] INFO [Broker id=3] Leader -uve-topic-15-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,234] INFO [Broker id=3] Leader -uve-topic-20-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,237] INFO [Broker id=3] Leader -uve-topic-29-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,240] INFO [Broker id=3] Leader -uve-topic-16-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,243] INFO [Broker id=3] Leader -uve-topic-7-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,245] INFO [Broker id=3] Leader -uve-topic-8-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,248] INFO [Broker id=3] Leader -uve-topic-22-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,250] INFO [Broker id=3] Leader -uve-topic-18-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,253] INFO [Broker id=3] Leader -uve-topic-24-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,256] INFO [Broker id=3] Leader -uve-topic-11-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,259] INFO [Broker id=3] Leader -uve-topic-17-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,262] INFO [Broker id=3] Leader -uve-topic-22-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,265] INFO [Broker id=3] Leader -uve-topic-1-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,268] INFO [Broker id=3] Leader structured_syslog_topic-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,271] INFO [Broker id=3] Leader -uve-topic-5-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,274] INFO [Broker id=3] Leader -uve-topic-15-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,277] INFO [Broker id=3] Leader -uve-topic-28-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,280] INFO [Broker id=3] Leader -uve-topic-20-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,282] INFO [Broker id=3] Leader -uve-topic-21-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,285] INFO [Broker id=3] Leader -uve-topic-7-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,287] INFO [Broker id=3] Leader -uve-topic-3-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,290] INFO [Broker id=3] Leader -uve-topic-8-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,292] INFO [Broker id=3] Leader -uve-topic-21-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,294] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,297] INFO [Broker id=3] Leader -uve-topic-0-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,300] INFO [Broker id=3] Leader -uve-topic-24-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,303] INFO [Broker id=3] Leader -uve-topic-23-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,306] INFO [Broker id=3] Leader -uve-topic-11-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,308] INFO [Broker id=3] Leader -uve-topic-10-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,311] INFO [Broker id=3] Leader -uve-topic-19-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,313] INFO [Broker id=3] Leader -uve-topic-20-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,316] INFO [Broker id=3] Leader -uve-topic-3-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,318] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,320] INFO [Broker id=3] Leader -uve-topic-7-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,323] INFO [Broker id=3] Leader -uve-topic-17-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,325] INFO [Broker id=3] Leader -uve-topic-16-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,328] INFO [Broker id=3] Leader -uve-topic-29-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,330] INFO [Broker id=3] Leader -uve-topic-0-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,333] INFO [Broker id=3] Leader structured_syslog_topic-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,336] INFO [Broker id=3] Leader -uve-topic-9-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,339] INFO [Broker id=3] Leader -uve-topic-6-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,342] INFO [Broker id=3] Leader -uve-topic-26-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,344] INFO [Broker id=3] Leader -uve-topic-13-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,347] INFO [Broker id=3] Leader -uve-topic-5-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,349] INFO [Broker id=3] Leader -uve-topic-7-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,351] INFO [Broker id=3] Leader -uve-topic-8-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,355] INFO [Broker id=3] Leader -uve-topic-19-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,357] INFO [Broker id=3] Leader -uve-topic-4-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,360] INFO [Broker id=3] Leader -uve-topic-25-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,362] INFO [Broker id=3] Leader -uve-topic-20-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,365] INFO [Broker id=3] Leader -uve-topic-12-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,368] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,372] INFO [Broker id=3] Leader -uve-topic-16-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,376] INFO [Broker id=3] Leader -uve-topic-29-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,380] INFO [Broker id=3] Leader -uve-topic-8-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,383] INFO [Broker id=3] Leader -uve-topic-18-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,385] INFO [Broker id=3] Leader -uve-topic-1-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,388] INFO [Broker id=3] Leader -uve-topic-22-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,390] INFO [Broker id=3] Leader -uve-topic-23-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,394] INFO [Broker id=3] Leader -uve-topic-10-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,397] INFO [Broker id=3] Leader -uve-topic-2-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,400] INFO [Broker id=3] Leader -uve-topic-18-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,403] INFO [Broker id=3] Leader -uve-topic-27-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,405] INFO [Broker id=3] Leader -uve-topic-14-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,408] INFO [Broker id=3] Leader -uve-topic-15-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,410] INFO [Broker id=3] Leader -uve-topic-28-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,413] INFO [Broker id=3] Leader -uve-topic-28-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,415] INFO [Broker id=3] Leader -uve-topic-27-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,418] INFO [Broker id=3] Leader -uve-topic-14-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,420] INFO [Broker id=3] Leader -uve-topic-8-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,423] INFO [Broker id=3] Leader -uve-topic-22-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,425] INFO [Broker id=3] Leader -uve-topic-16-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,428] INFO [Broker id=3] Leader -uve-topic-15-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,430] INFO [Broker id=3] Leader -uve-topic-29-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,433] INFO [Broker id=3] Leader -uve-topic-28-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,435] INFO [Broker id=3] Leader -uve-topic-21-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,455] INFO [Broker id=3] Leader -uve-topic-17-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,459] INFO [Broker id=3] Leader -uve-topic-20-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,462] INFO [Broker id=3] Leader -uve-topic-21-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,466] INFO [Broker id=3] Leader structured_syslog_topic-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,470] INFO [Broker id=3] Leader -uve-topic-25-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,472] INFO [Broker id=3] Leader -uve-topic-12-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,476] INFO [Broker id=3] Leader -uve-topic-24-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,479] INFO [Broker id=3] Leader -uve-topic-11-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,481] INFO [Broker id=3] Leader -uve-topic-26-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,484] INFO [Broker id=3] Leader -uve-topic-13-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,488] INFO [Broker id=3] Leader -uve-topic-15-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,491] INFO [Broker id=3] Leader -uve-topic-28-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,494] INFO [Broker id=3] Leader -uve-topic-20-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,497] INFO [Broker id=3] Leader -uve-topic-7-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,500] INFO [Broker id=3] Leader -uve-topic-3-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,503] INFO [Broker id=3] Leader -uve-topic-19-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,506] INFO [Broker id=3] Leader -uve-topic-23-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,509] INFO [Broker id=3] Leader -uve-topic-10-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,512] INFO [Broker id=3] Leader -uve-topic-25-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,515] INFO [Broker id=3] Leader -uve-topic-12-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,521] INFO [Broker id=3] Leader -uve-topic-24-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,526] INFO [Broker id=3] Leader -uve-topic-11-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,531] INFO [Broker id=3] Leader -uve-topic-15-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,533] INFO [Broker id=3] Leader -uve-topic-28-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,536] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,539] INFO [Broker id=3] Leader -uve-topic-20-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,542] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,544] INFO [Broker id=3] Leader -uve-topic-6-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,554] INFO [Broker id=3] Leader -uve-topic-9-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,557] INFO [Broker id=3] Leader -uve-topic-19-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,562] INFO [Broker id=3] Leader -uve-topic-18-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,565] INFO [Broker id=3] Leader -uve-topic-22-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,568] INFO [Broker id=3] Leader -uve-topic-10-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,570] INFO [Broker id=3] Leader -uve-topic-23-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,572] INFO [Broker id=3] Leader -uve-topic-18-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,575] INFO [Broker id=3] Leader -uve-topic-17-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,577] INFO [Broker id=3] Leader -uve-topic-22-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,579] INFO [Broker id=3] Leader -uve-topic-14-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,582] INFO [Broker id=3] Leader -uve-topic-27-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,584] INFO [Broker id=3] Leader -uve-topic-5-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,587] INFO [Broker id=3] Leader -uve-topic-21-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,589] INFO [Broker id=3] Leader -uve-topic-28-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,591] INFO [Broker id=3] Leader -uve-topic-15-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,594] INFO [Broker id=3] Leader -uve-topic-16-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,608] INFO [Broker id=3] Leader -uve-topic-17-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,613] INFO [Broker id=3] Leader -uve-topic-13-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,615] INFO [Broker id=3] Leader -uve-topic-12-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,618] INFO [Broker id=3] Leader -uve-topic-25-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,620] INFO [Broker id=3] Leader -uve-topic-26-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,623] INFO [Broker id=3] Leader -uve-topic-14-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,625] INFO [Broker id=3] Leader -uve-topic-27-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,628] INFO [Broker id=3] Leader -uve-topic-7-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,631] INFO [Broker id=3] Leader -uve-topic-2-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,635] INFO [Broker id=3] Leader -uve-topic-14-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,639] INFO [Broker id=3] Leader -uve-topic-27-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,642] INFO [Broker id=3] Leader -uve-topic-28-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,645] INFO [Broker id=3] Leader -uve-topic-15-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,651] INFO [Broker id=3] Leader -uve-topic-7-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,657] INFO [Broker id=3] Leader -uve-topic-0-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,661] INFO [Broker id=3] Leader -uve-topic-1-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,665] INFO [Broker id=3] Leader -uve-topic-2-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,668] INFO [Broker id=3] Leader -uve-topic-9-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,670] INFO [Broker id=3] Leader -uve-topic-8-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,673] INFO [Broker id=3] Leader structured_syslog_topic-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,676] INFO [Broker id=3] Leader -uve-topic-1-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,679] INFO [Broker id=3] Leader -uve-topic-0-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,683] INFO [Broker id=3] Leader structured_syslog_topic-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,686] INFO [Broker id=3] Leader -uve-topic-4-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,690] INFO [Broker id=3] Leader -uve-topic-13-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,693] INFO [Broker id=3] Leader -uve-topic-26-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,695] INFO [Broker id=3] Leader -uve-topic-6-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,698] INFO [Broker id=3] Leader -uve-topic-8-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,700] INFO [Broker id=3] Leader -uve-topic-7-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,705] INFO [Broker id=3] Leader -uve-topic-20-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,709] INFO [Broker id=3] Leader -uve-topic-11-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,712] INFO [Broker id=3] Leader -uve-topic-24-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,715] INFO [Broker id=3] Leader -uve-topic-29-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,718] INFO [Broker id=3] Leader -uve-topic-16-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,721] INFO [Broker id=3] Leader -uve-topic-3-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,728] INFO [Broker id=3] Leader -uve-topic-11-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,733] INFO [Broker id=3] Leader -uve-topic-4-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,736] INFO [Broker id=3] Leader -uve-topic-5-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,739] INFO [Broker id=3] Leader -uve-topic-6-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,743] INFO [Broker id=3] Leader -uve-topic-2-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,746] INFO [Broker id=3] Leader -uve-topic-1-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,749] INFO [Broker id=3] Leader -uve-topic-18-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,752] INFO [Broker id=3] Leader structured_syslog_topic-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,755] INFO [Broker id=3] Leader -uve-topic-3-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,757] INFO [Broker id=3] Leader -uve-topic-2-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,763] INFO [Broker id=3] Leader -uve-topic-14-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,771] INFO [Broker id=3] Leader -uve-topic-27-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,778] INFO [Broker id=3] Leader -uve-topic-28-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,781] INFO [Broker id=3] Leader -uve-topic-15-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,783] INFO [Broker id=3] Leader -uve-topic-8-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,785] INFO [Broker id=3] Leader -uve-topic-1-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,788] INFO [Broker id=3] Leader -uve-topic-0-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,790] INFO [Broker id=3] Leader -uve-topic-20-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,793] INFO [Broker id=3] Leader structured_syslog_topic-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,795] INFO [Broker id=3] Leader -uve-topic-9-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,798] INFO [Broker id=3] Leader -uve-topic-22-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,800] INFO [Broker id=3] Leader -uve-topic-13-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,802] INFO [Broker id=3] Leader -uve-topic-12-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,805] INFO [Broker id=3] Leader -uve-topic-25-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,807] INFO [Broker id=3] Leader -uve-topic-26-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,810] INFO [Broker id=3] Leader -uve-topic-5-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,813] INFO [Broker id=3] Leader -uve-topic-12-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,815] INFO [Broker id=3] Leader -uve-topic-25-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,818] INFO [Broker id=3] Leader -uve-topic-13-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,821] INFO [Broker id=3] Leader -uve-topic-26-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,823] INFO [Broker id=3] Leader -uve-topic-7-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,827] INFO [Broker id=3] Leader -uve-topic-6-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,830] INFO [Broker id=3] Leader -uve-topic-28-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,832] INFO [Broker id=3] Leader -uve-topic-15-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,835] INFO [Broker id=3] Leader -uve-topic-7-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,837] INFO [Broker id=3] Leader -uve-topic-19-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,840] INFO [Broker id=3] Leader -uve-topic-10-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,842] INFO [Broker id=3] Leader -uve-topic-11-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,845] INFO [Broker id=3] Leader -uve-topic-24-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,848] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,850] INFO [Broker id=3] Leader -uve-topic-19-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,853] INFO [Broker id=3] Leader structured_syslog_topic-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,855] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,858] INFO [Broker id=3] Leader -uve-topic-14-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,860] INFO [Broker id=3] Leader -uve-topic-27-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,864] INFO [Broker id=3] Leader -uve-topic-10-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,866] INFO [Broker id=3] Leader -uve-topic-23-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,869] INFO [Broker id=3] Leader -uve-topic-17-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,872] INFO [Broker id=3] Leader -uve-topic-9-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,875] INFO [Broker id=3] Leader -uve-topic-14-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,877] INFO [Broker id=3] Leader -uve-topic-27-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,880] INFO [Broker id=3] Leader -uve-topic-6-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,882] INFO [Broker id=3] Leader -uve-topic-29-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,885] INFO [Broker id=3] Leader -uve-topic-16-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,887] INFO [Broker id=3] Leader -uve-topic-21-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,890] INFO [Broker id=3] Leader -uve-topic-0-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,892] INFO [Broker id=3] Leader -uve-topic-4-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,894] INFO [Broker id=3] Leader -uve-topic-8-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,897] INFO [Broker id=3] Leader -uve-topic-28-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,900] INFO [Broker id=3] Leader -uve-topic-14-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,902] INFO [Broker id=3] Leader -uve-topic-27-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,905] INFO [Broker id=3] Leader -uve-topic-29-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,908] INFO [Broker id=3] Leader -uve-topic-16-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,912] INFO [Broker id=3] Leader -uve-topic-10-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,915] INFO [Broker id=3] Leader -uve-topic-23-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,917] INFO [Broker id=3] Leader -uve-topic-12-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,920] INFO [Broker id=3] Leader -uve-topic-25-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,930] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,933] INFO [Broker id=3] Leader -uve-topic-27-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,938] INFO [Broker id=3] Leader -uve-topic-13-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,940] INFO [Broker id=3] Leader -uve-topic-26-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,944] INFO [Broker id=3] Leader -uve-topic-18-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,946] INFO [Broker id=3] Leader -uve-topic-9-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,948] INFO [Broker id=3] Leader -uve-topic-0-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,951] INFO [Broker id=3] Leader -uve-topic-1-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,955] INFO [Broker id=3] Leader -uve-topic-2-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,958] INFO [Broker id=3] Leader structured_syslog_topic-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,961] INFO [Broker id=3] Leader -uve-topic-6-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,964] INFO [Broker id=3] Leader -uve-topic-5-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,966] INFO [Broker id=3] Leader -uve-topic-14-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,969] INFO [Broker id=3] Leader -uve-topic-27-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,971] INFO [Broker id=3] Leader -uve-topic-5-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,974] INFO [Broker id=3] Leader -uve-topic-13-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,977] INFO [Broker id=3] Leader -uve-topic-6-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,979] INFO [Broker id=3] Leader -uve-topic-7-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,982] INFO [Broker id=3] Leader -uve-topic-8-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,985] INFO [Broker id=3] Leader -uve-topic-20-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,988] INFO [Broker id=3] Leader -uve-topic-11-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,990] INFO [Broker id=3] Leader -uve-topic-24-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:44,993] INFO [Broker id=3] Leader -uve-topic-4-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,000] INFO [Broker id=3] Leader -uve-topic-3-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,003] INFO [Broker id=3] Leader structured_syslog_topic-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,005] INFO [Broker id=3] Leader -uve-topic-5-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,008] INFO [Broker id=3] Leader -uve-topic-7-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,011] INFO [Broker id=3] Leader -uve-topic-13-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,014] INFO [Broker id=3] Leader -uve-topic-26-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,017] INFO [Broker id=3] Leader -uve-topic-6-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,021] INFO [Broker id=3] Leader -uve-topic-3-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,024] INFO [Broker id=3] Leader -uve-topic-2-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,029] INFO [Broker id=3] Leader -uve-topic-22-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,032] INFO [Broker id=3] Leader -uve-topic-19-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,034] INFO [Broker id=3] Leader structured_syslog_topic-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,038] INFO [Broker id=3] Leader -uve-topic-14-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,040] INFO [Broker id=3] Leader -uve-topic-9-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,043] INFO [Broker id=3] Leader -uve-topic-8-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,045] INFO [Broker id=3] Leader -uve-topic-21-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,047] INFO [Broker id=3] Leader -uve-topic-28-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,050] INFO [Broker id=3] Leader -uve-topic-15-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,053] INFO [Broker id=3] Leader -uve-topic-1-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,055] INFO [Broker id=3] Leader -uve-topic-0-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,058] INFO [Broker id=3] Leader -uve-topic-17-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,061] INFO [Broker id=3] Leader structured_syslog_topic-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,064] INFO [Broker id=3] Leader -uve-topic-13-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,067] INFO [Broker id=3] Leader -uve-topic-26-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,070] INFO [Broker id=3] Leader -uve-topic-4-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,073] INFO [Broker id=3] Leader structured_syslog_topic-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,075] INFO [Broker id=3] Leader -uve-topic-28-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,078] INFO [Broker id=3] Leader -uve-topic-15-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,081] INFO [Broker id=3] Leader -uve-topic-0-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,084] INFO [Broker id=3] Leader -uve-topic-7-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,087] INFO [Broker id=3] Leader -uve-topic-20-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,090] INFO [Broker id=3] Leader -uve-topic-28-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,093] INFO [Broker id=3] Leader -uve-topic-15-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,098] INFO [Broker id=3] Leader -uve-topic-12-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,100] INFO [Broker id=3] Leader -uve-topic-25-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,103] INFO [Broker id=3] Leader -uve-topic-3-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,106] INFO [Broker id=3] Leader -uve-topic-19-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,110] INFO [Broker id=3] Leader -uve-topic-4-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,113] INFO [Broker id=3] Leader -uve-topic-11-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,115] INFO [Broker id=3] Leader -uve-topic-24-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,118] INFO [Broker id=3] Leader structured_syslog_topic-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,121] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,124] INFO [Broker id=3] Leader -uve-topic-6-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,127] INFO [Broker id=3] Leader -uve-topic-13-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,129] INFO [Broker id=3] Leader -uve-topic-26-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,132] INFO [Broker id=3] Leader -uve-topic-14-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,135] INFO [Broker id=3] Leader -uve-topic-27-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,138] INFO [Broker id=3] Leader -uve-topic-18-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,147] INFO [Broker id=3] Leader -uve-topic-22-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,151] INFO [Broker id=3] Leader -uve-topic-10-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,159] INFO [Broker id=3] Leader -uve-topic-23-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,162] INFO [Broker id=3] Leader -uve-topic-6-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,164] INFO [Broker id=3] Leader -uve-topic-20-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,167] INFO [Broker id=3] Leader -uve-topic-21-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,171] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,174] INFO [Broker id=3] Leader -uve-topic-16-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,177] INFO [Broker id=3] Leader -uve-topic-29-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,179] INFO [Broker id=3] Leader -uve-topic-21-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,183] INFO [Broker id=3] Leader -uve-topic-4-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,186] INFO [Broker id=3] Leader -uve-topic-27-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,189] INFO [Broker id=3] Leader -uve-topic-14-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,191] INFO [Broker id=3] Leader -uve-topic-16-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,194] INFO [Broker id=3] Leader -uve-topic-29-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,197] INFO [Broker id=3] Leader -uve-topic-2-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,201] INFO [Broker id=3] Leader -uve-topic-2-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,203] INFO [Broker id=3] Leader -uve-topic-1-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,206] INFO [Broker id=3] Leader -uve-topic-3-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,209] INFO [Broker id=3] Leader -uve-topic-26-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,211] INFO [Broker id=3] Leader -uve-topic-13-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,213] INFO [Broker id=3] Leader -uve-topic-5-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,215] INFO [Broker id=3] Leader -uve-topic-9-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,218] INFO [Broker id=3] Leader -uve-topic-17-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,221] INFO [Broker id=3] Leader -uve-topic-1-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,223] INFO [Broker id=3] Leader -uve-topic-8-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,225] INFO [Broker id=3] Leader structured_syslog_topic-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,228] INFO [Broker id=3] Leader -uve-topic-5-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,231] INFO [Broker id=3] Leader -uve-topic-22-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,234] INFO [Broker id=3] Leader -uve-topic-26-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,237] INFO [Broker id=3] Leader -uve-topic-13-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,239] INFO [Broker id=3] Leader -uve-topic-5-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,241] INFO [Broker id=3] Leader -uve-topic-16-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,245] INFO [Broker id=3] Leader -uve-topic-29-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,261] INFO [Broker id=3] Leader -uve-topic-15-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,265] INFO [Broker id=3] Leader -uve-topic-28-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,267] INFO [Broker id=3] Leader -uve-topic-8-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,273] INFO [Broker id=3] Leader -uve-topic-5-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,283] INFO [Broker id=3] Leader -uve-topic-4-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,286] INFO [Broker id=3] Leader -uve-topic-24-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,288] INFO [Broker id=3] Leader -uve-topic-11-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,292] INFO [Broker id=3] Leader -uve-topic-4-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,295] INFO [Broker id=3] Leader structured_syslog_topic-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,298] INFO [Broker id=3] Leader -uve-topic-5-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,301] INFO [Broker id=3] Leader -uve-topic-7-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,303] INFO [Broker id=3] Leader -uve-topic-18-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,306] INFO [Broker id=3] Leader -uve-topic-1-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,309] INFO [Broker id=3] Leader -uve-topic-3-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,312] INFO [Broker id=3] Leader -uve-topic-19-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,314] INFO [Broker id=3] Leader structured_syslog_topic-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,317] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,320] INFO [Broker id=3] Leader -uve-topic-4-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,323] INFO [Broker id=3] Leader -uve-topic-25-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,326] INFO [Broker id=3] Leader -uve-topic-26-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,366] INFO [Broker id=3] Leader -uve-topic-12-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,370] INFO [Broker id=3] Leader -uve-topic-13-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,410] INFO [Broker id=3] Leader -uve-topic-4-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,415] INFO [Broker id=3] Leader -uve-topic-0-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,417] INFO [Broker id=3] Leader -uve-topic-17-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,420] INFO [Broker id=3] Leader -uve-topic-16-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,423] INFO [Broker id=3] Leader -uve-topic-29-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,427] INFO [Broker id=3] Leader -uve-topic-2-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,429] INFO [Broker id=3] Leader -uve-topic-22-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,432] INFO [Broker id=3] Leader -uve-topic-9-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,434] INFO [Broker id=3] Leader -uve-topic-21-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,437] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,439] INFO [Broker id=3] Leader -uve-topic-17-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,442] INFO [Broker id=3] Leader -uve-topic-26-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,445] INFO [Broker id=3] Leader -uve-topic-13-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,447] INFO [Broker id=3] Leader -uve-topic-15-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,450] INFO [Broker id=3] Leader -uve-topic-28-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,453] INFO [Broker id=3] Leader -uve-topic-20-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,455] INFO [Broker id=3] Leader -uve-topic-21-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,460] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,463] INFO [Broker id=3] Leader -uve-topic-27-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,465] INFO [Broker id=3] Leader -uve-topic-14-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,468] INFO [Broker id=3] Leader -uve-topic-25-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,470] INFO [Broker id=3] Leader -uve-topic-19-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,474] INFO [Broker id=3] Leader -uve-topic-20-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,477] INFO [Broker id=3] Leader -uve-topic-10-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,479] INFO [Broker id=3] Leader -uve-topic-24-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,482] INFO [Broker id=3] Leader -uve-topic-23-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,485] INFO [Broker id=3] Leader -uve-topic-25-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,487] INFO [Broker id=3] Leader -uve-topic-12-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,490] INFO [Broker id=3] Leader -uve-topic-27-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,515] INFO [Broker id=3] Leader -uve-topic-26-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,528] INFO [Broker id=3] Leader -uve-topic-13-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,531] INFO [Broker id=3] Leader -uve-topic-14-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,535] INFO [Broker id=3] Leader -uve-topic-6-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,538] INFO [Broker id=3] Leader -uve-topic-10-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,540] INFO [Broker id=3] Leader -uve-topic-22-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,546] INFO [Broker id=3] Leader -uve-topic-23-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,550] INFO [Broker id=3] Leader -uve-topic-18-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,552] INFO [Broker id=3] Leader -uve-topic-5-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,555] INFO [Broker id=3] Leader -uve-topic-25-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,557] INFO [Broker id=3] Leader -uve-topic-12-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,560] INFO [Broker id=3] Leader -uve-topic-18-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,563] INFO [Broker id=3] Leader -uve-topic-17-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,565] INFO [Broker id=3] Leader -uve-topic-20-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,568] INFO [Broker id=3] Leader -uve-topic-21-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,570] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,572] INFO [Broker id=3] Leader -uve-topic-22-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,575] INFO [Broker id=3] Leader -uve-topic-17-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,577] INFO [Broker id=3] Leader -uve-topic-16-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,579] INFO [Broker id=3] Leader -uve-topic-29-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,582] INFO [Broker id=3] Leader -uve-topic-21-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,584] INFO [Broker id=3] Leader structured_syslog_topic-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,586] INFO [Broker id=3] Leader -uve-topic-20-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,589] INFO [Broker id=3] Leader -uve-topic-27-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,596] INFO [Broker id=3] Leader -uve-topic-14-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,599] INFO [Broker id=3] Leader -uve-topic-16-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,602] INFO [Broker id=3] Leader -uve-topic-15-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,604] INFO [Broker id=3] Leader -uve-topic-29-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,607] INFO [Broker id=3] Leader -uve-topic-28-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,609] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,612] INFO [Broker id=3] Leader -uve-topic-25-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,614] INFO [Broker id=3] Leader -uve-topic-12-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,616] INFO [Broker id=3] Leader -uve-topic-24-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,619] INFO [Broker id=3] Leader -uve-topic-11-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,621] INFO [Broker id=3] Leader -uve-topic-26-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,624] INFO [Broker id=3] Leader -uve-topic-13-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,626] INFO [Broker id=3] Leader -uve-topic-12-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,629] INFO [Broker id=3] Leader -uve-topic-13-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,631] INFO [Broker id=3] Leader -uve-topic-5-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,634] INFO [Broker id=3] Leader -uve-topic-6-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,637] INFO [Broker id=3] Leader -uve-topic-9-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,639] INFO [Broker id=3] Leader -uve-topic-1-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,642] INFO [Broker id=3] Leader -uve-topic-8-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,645] INFO [Broker id=3] Leader -uve-topic-15-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,649] INFO [Broker id=3] Leader -uve-topic-28-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,651] INFO [Broker id=3] Leader -uve-topic-0-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,654] INFO [Broker id=3] Leader -uve-topic-7-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,656] INFO [Broker id=3] Leader -uve-topic-4-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,659] INFO [Broker id=3] Leader -uve-topic-3-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,661] INFO [Broker id=3] Leader -uve-topic-25-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,663] INFO [Broker id=3] Leader -uve-topic-12-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,665] INFO [Broker id=3] Leader -uve-topic-19-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,668] INFO [Broker id=3] Leader structured_syslog_topic-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,670] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,673] INFO [Broker id=3] Leader -uve-topic-7-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,675] INFO [Broker id=3] Leader -uve-topic-6-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,677] INFO [Broker id=3] Leader -uve-topic-10-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,690] INFO [Broker id=3] Leader -uve-topic-27-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,693] INFO [Broker id=3] Leader -uve-topic-23-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,695] INFO [Broker id=3] Leader -uve-topic-14-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,697] INFO [Broker id=3] Leader -uve-topic-2-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,701] INFO [Broker id=3] Leader -uve-topic-18-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,703] INFO [Broker id=3] Leader -uve-topic-19-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,705] INFO [Broker id=3] Leader -uve-topic-22-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,708] INFO [Broker id=3] Leader -uve-topic-24-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,711] INFO [Broker id=3] Leader -uve-topic-11-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,714] INFO [Broker id=3] Leader -uve-topic-10-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,717] INFO [Broker id=3] Leader -uve-topic-23-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,719] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,724] INFO [Broker id=3] Leader -uve-topic-4-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,728] INFO [Broker id=3] Leader -uve-topic-25-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,730] INFO [Broker id=3] Leader -uve-topic-12-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,733] INFO [Broker id=3] Leader -uve-topic-5-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,736] INFO [Broker id=3] Leader -uve-topic-4-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,740] INFO [Broker id=3] Leader -uve-topic-17-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,744] INFO [Broker id=3] Leader -uve-topic-0-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,747] INFO [Broker id=3] Leader -uve-topic-1-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,752] INFO [Broker id=3] Leader -uve-topic-16-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,754] INFO [Broker id=3] Leader -uve-topic-2-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,759] INFO [Broker id=3] Leader -uve-topic-9-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,762] INFO [Broker id=3] Leader -uve-topic-25-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,764] INFO [Broker id=3] Leader -uve-topic-12-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,767] INFO [Broker id=3] Leader -uve-topic-4-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,769] INFO [Broker id=3] Leader -uve-topic-3-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,771] INFO [Broker id=3] Leader -uve-topic-3-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,773] INFO [Broker id=3] Leader -uve-topic-0-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,776] INFO [Broker id=3] Leader -uve-topic-15-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,778] INFO [Broker id=3] Leader -uve-topic-6-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,781] INFO [Broker id=3] Leader -uve-topic-7-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,783] INFO [Broker id=3] Leader -uve-topic-8-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,785] INFO [Broker id=3] Leader -uve-topic-21-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,789] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,791] INFO [Broker id=3] Leader -uve-topic-25-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,793] INFO [Broker id=3] Leader -uve-topic-12-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,796] INFO [Broker id=3] Leader -uve-topic-19-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,798] INFO [Broker id=3] Leader -uve-topic-24-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,802] INFO [Broker id=3] Leader -uve-topic-11-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,804] INFO [Broker id=3] Leader -uve-topic-4-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,828] INFO [Broker id=3] Leader -uve-topic-24-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,831] INFO [Broker id=3] Leader -uve-topic-11-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,834] INFO [Broker id=3] Leader -uve-topic-5-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,836] INFO [Broker id=3] Leader -uve-topic-6-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,840] INFO [Broker id=3] Leader -uve-topic-27-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,842] INFO [Broker id=3] Leader -uve-topic-14-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,845] INFO [Broker id=3] Leader -uve-topic-18-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,848] INFO [Broker id=3] Leader -uve-topic-19-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,851] INFO [Broker id=3] Leader -uve-topic-10-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,854] INFO [Broker id=3] Leader -uve-topic-22-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,857] INFO [Broker id=3] Leader -uve-topic-23-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,859] INFO [Broker id=3] Leader -uve-topic-18-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,862] INFO [Broker id=3] Leader -uve-topic-24-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,864] INFO [Broker id=3] Leader -uve-topic-11-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,866] INFO [Broker id=3] Leader -uve-topic-26-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,869] INFO [Broker id=3] Leader -uve-topic-13-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,871] INFO [Broker id=3] Leader -uve-topic-25-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,874] INFO [Broker id=3] Leader -uve-topic-20-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,876] INFO [Broker id=3] Leader -uve-topic-12-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,878] INFO [Broker id=3] Leader -uve-topic-22-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,881] INFO [Broker id=3] Leader -uve-topic-16-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,883] INFO [Broker id=3] Leader -uve-topic-29-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,885] INFO [Broker id=3] Leader -uve-topic-21-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,887] INFO [Broker id=3] Leader -uve-topic-8-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,890] INFO [Broker id=3] Leader -uve-topic-17-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,897] INFO [Broker id=3] Leader -uve-topic-15-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,899] INFO [Broker id=3] Leader -uve-topic-28-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,902] INFO [Broker id=3] Leader -uve-topic-7-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,904] INFO [Broker id=3] Leader -uve-topic-10-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,907] INFO [Broker id=3] Leader -uve-topic-23-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,910] INFO [Broker id=3] Leader -uve-topic-1-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,912] INFO [Broker id=3] Leader -uve-topic-3-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,916] INFO [Broker id=3] Leader structured_syslog_topic-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,918] INFO [Broker id=3] Leader -uve-topic-5-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,922] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,924] INFO [Broker id=3] Leader -uve-topic-4-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,926] INFO [Broker id=3] Leader -uve-topic-9-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,930] INFO [Broker id=3] Leader -uve-topic-9-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,933] INFO [Broker id=3] Leader -uve-topic-19-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,937] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,940] INFO [Broker id=3] Leader -uve-topic-17-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,942] INFO [Broker id=3] Leader -uve-topic-8-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,945] INFO [Broker id=3] Leader -uve-topic-1-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,947] INFO [Broker id=3] Leader -uve-topic-0-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,950] INFO [Broker id=3] Leader -uve-topic-24-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,955] INFO [Broker id=3] Leader -uve-topic-5-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,958] INFO [Broker id=3] Leader -uve-topic-7-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,960] INFO [Broker id=3] Leader -uve-topic-6-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,963] INFO [Broker id=3] Leader -uve-topic-23-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,965] INFO [Broker id=3] Leader -uve-topic-10-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,967] INFO [Broker id=3] Leader -uve-topic-3-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,971] INFO [Broker id=3] Leader -uve-topic-2-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,973] INFO [Broker id=3] Leader -uve-topic-18-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,976] INFO [Broker id=3] Leader -uve-topic-19-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,980] INFO [Broker id=3] Leader -uve-topic-4-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,982] INFO [Broker id=3] Leader -uve-topic-5-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,984] INFO [Broker id=3] Leader -uve-topic-6-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,988] INFO [Broker id=3] Leader -uve-topic-25-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,990] INFO [Broker id=3] Leader -uve-topic-12-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,993] INFO [Broker id=3] Leader -uve-topic-0-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,995] INFO [Broker id=3] Leader -uve-topic-4-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,997] INFO [Broker id=3] Leader -uve-topic-2-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:45,999] INFO [Broker id=3] Leader -uve-topic-18-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,002] INFO [Broker id=3] Leader -uve-topic-1-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,005] INFO [Broker id=3] Leader -uve-topic-9-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,014] INFO [Broker id=3] Leader -uve-topic-21-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,017] INFO [Broker id=3] Leader -uve-topic-3-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,019] INFO [Broker id=3] Leader -uve-topic-23-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,021] INFO [Broker id=3] Leader -uve-topic-24-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,024] INFO [Broker id=3] Leader -uve-topic-11-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,026] INFO [Broker id=3] Leader -uve-topic-15-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,029] INFO [Broker id=3] Leader -uve-topic-3-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,033] INFO [Broker id=3] Leader -uve-topic-28-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,036] INFO [Broker id=3] Leader -uve-topic-8-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,045] INFO [Broker id=3] Leader -uve-topic-20-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,048] INFO [Broker id=3] Leader -uve-topic-7-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,051] INFO [Broker id=3] Leader -uve-topic-27-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,053] INFO [Broker id=3] Leader -uve-topic-14-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,056] INFO [Broker id=3] Leader -uve-topic-16-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,058] INFO [Broker id=3] Leader -uve-topic-29-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,060] INFO [Broker id=3] Leader -uve-topic-24-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,063] INFO [Broker id=3] Leader -uve-topic-11-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,068] INFO [Broker id=3] Leader -uve-topic-19-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,070] INFO [Broker id=3] Leader -uve-topic-24-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,080] INFO [Broker id=3] Leader -uve-topic-11-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,083] INFO [Broker id=3] Leader -uve-topic-3-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,086] INFO [Broker id=3] Leader structured_syslog_topic-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,088] INFO [Broker id=3] Leader -uve-topic-26-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,090] INFO [Broker id=3] Leader -uve-topic-13-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,092] INFO [Broker id=3] Leader -uve-topic-22-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,095] INFO [Broker id=3] Leader -uve-topic-10-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,099] INFO [Broker id=3] Leader structured_syslog_topic-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,102] INFO [Broker id=3] Leader -uve-topic-5-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,106] INFO [Broker id=3] Leader -uve-topic-25-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,109] INFO [Broker id=3] Leader -uve-topic-12-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,112] INFO [Broker id=3] Leader -uve-topic-24-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,114] INFO [Broker id=3] Leader -uve-topic-11-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,118] INFO [Broker id=3] Leader -uve-topic-26-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,122] INFO [Broker id=3] Leader -uve-topic-13-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,128] INFO [Broker id=3] Leader -uve-topic-17-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,132] INFO [Broker id=3] Leader -uve-topic-20-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,136] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,139] INFO [Broker id=3] Leader -uve-topic-22-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,141] INFO [Broker id=3] Leader -uve-topic-9-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,143] INFO [Broker id=3] Leader -uve-topic-19-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,145] INFO [Broker id=3] Leader -uve-topic-18-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,148] INFO [Broker id=3] Leader -uve-topic-24-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,150] INFO [Broker id=3] Leader -uve-topic-23-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,152] INFO [Broker id=3] Leader -uve-topic-11-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,155] INFO [Broker id=3] Leader -uve-topic-10-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,158] INFO [Broker id=3] Leader -uve-topic-3-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,160] INFO [Broker id=3] Leader -uve-topic-19-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,163] INFO [Broker id=3] Leader -uve-topic-23-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,168] INFO [Broker id=3] Leader -uve-topic-10-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,171] INFO [Broker id=3] Leader -uve-topic-15-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,173] INFO [Broker id=3] Leader -uve-topic-28-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,176] INFO [Broker id=3] Leader -uve-topic-21-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,184] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,187] INFO [Broker id=3] Leader -uve-topic-6-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,190] INFO [Broker id=3] Leader -uve-topic-19-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,194] INFO [Broker id=3] Leader -uve-topic-3-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,197] INFO [Broker id=3] Leader -uve-topic-26-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,199] INFO [Broker id=3] Leader -uve-topic-1-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,213] INFO [Broker id=3] Leader -uve-topic-9-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,217] INFO [Broker id=3] Leader -uve-topic-0-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,220] INFO [Broker id=3] Leader -uve-topic-1-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,224] INFO [Broker id=3] Leader -uve-topic-2-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,227] INFO [Broker id=3] Leader -uve-topic-25-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,229] INFO [Broker id=3] Leader -uve-topic-12-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,249] INFO [Broker id=3] Leader -uve-topic-4-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,253] INFO [Broker id=3] Leader -uve-topic-8-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,257] INFO [Broker id=3] Leader -uve-topic-0-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,259] INFO [Broker id=3] Leader -uve-topic-16-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,262] INFO [Broker id=3] Leader -uve-topic-29-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,264] INFO [Broker id=3] Leader -uve-topic-7-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,267] INFO [Broker id=3] Leader -uve-topic-8-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,270] INFO [Broker id=3] Leader -uve-topic-2-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,273] INFO [Broker id=3] Leader -uve-topic-27-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,275] INFO [Broker id=3] Leader -uve-topic-6-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,278] INFO [Broker id=3] Leader -uve-topic-7-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,280] INFO [Broker id=3] Leader -uve-topic-27-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,283] INFO [Broker id=3] Leader -uve-topic-14-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,285] INFO [Broker id=3] Leader -uve-topic-2-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,288] INFO [Broker id=3] Leader -uve-topic-24-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,290] INFO [Broker id=3] Leader -uve-topic-11-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,294] INFO [Broker id=3] Leader -uve-topic-18-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,297] INFO [Broker id=3] Leader -uve-topic-3-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,299] INFO [Broker id=3] Leader -uve-topic-23-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,302] INFO [Broker id=3] Leader -uve-topic-10-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,304] INFO [Broker id=3] Leader -uve-topic-4-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,307] INFO [Broker id=3] Leader -uve-topic-1-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,310] INFO [Broker id=3] Leader -uve-topic-6-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,313] INFO [Broker id=3] Leader -uve-topic-0-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,317] INFO [Broker id=3] Leader -uve-topic-9-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,320] INFO [Broker id=3] Leader -uve-topic-16-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,322] INFO [Broker id=3] Leader -uve-topic-29-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,325] INFO [Broker id=3] Leader -uve-topic-2-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,328] INFO [Broker id=3] Leader -uve-topic-1-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,331] INFO [Broker id=3] Leader -uve-topic-18-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,334] INFO [Broker id=3] Leader -uve-topic-3-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,338] INFO [Broker id=3] Leader -uve-topic-19-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,341] INFO [Broker id=3] Leader -uve-topic-25-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,344] INFO [Broker id=3] Leader -uve-topic-12-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,347] INFO [Broker id=3] Leader -uve-topic-24-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,350] INFO [Broker id=3] Leader -uve-topic-11-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,353] INFO [Broker id=3] Leader -uve-topic-15-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,355] INFO [Broker id=3] Leader -uve-topic-29-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,368] INFO [Broker id=3] Leader -uve-topic-28-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,373] INFO [Broker id=3] Leader -uve-topic-8-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,376] INFO [Broker id=3] Leader -uve-topic-20-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,379] INFO [Broker id=3] Leader -uve-topic-21-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,382] INFO [Broker id=3] Leader -uve-topic-18-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,395] INFO [Broker id=3] Leader structured_syslog_topic-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,397] INFO [Broker id=3] Leader -uve-topic-5-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,400] INFO [Broker id=3] Leader -uve-topic-27-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,403] INFO [Broker id=3] Leader -uve-topic-14-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,406] INFO [Broker id=3] Leader -uve-topic-7-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,411] INFO [Broker id=3] Leader -uve-topic-20-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,414] INFO [Broker id=3] Leader -uve-topic-27-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,417] INFO [Broker id=3] Leader -uve-topic-26-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,420] INFO [Broker id=3] Leader -uve-topic-13-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,424] INFO [Broker id=3] Leader -uve-topic-14-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,426] INFO [Broker id=3] Leader -uve-topic-23-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,429] INFO [Broker id=3] Leader -uve-topic-10-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,432] INFO [Broker id=3] Leader -uve-topic-19-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,435] INFO [Broker id=3] Leader -uve-topic-22-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,437] INFO [Broker id=3] Leader structured_syslog_topic-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,440] INFO [Broker id=3] Leader -uve-topic-24-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,444] INFO [Broker id=3] Leader -uve-topic-11-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,448] INFO [Broker id=3] Leader -uve-topic-26-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,451] INFO [Broker id=3] Leader -uve-topic-25-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,468] INFO [Broker id=3] Leader -uve-topic-12-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,472] INFO [Broker id=3] Leader -uve-topic-13-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,475] INFO [Broker id=3] Leader -uve-topic-21-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,478] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,481] INFO [Broker id=3] Leader -uve-topic-17-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,484] INFO [Broker id=3] Leader -uve-topic-9-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,486] INFO [Broker id=3] Leader -uve-topic-23-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,500] INFO [Broker id=3] Leader -uve-topic-0-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,516] INFO [Broker id=3] Leader -uve-topic-10-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,524] INFO [Broker id=3] Leader -uve-topic-18-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,528] INFO [Broker id=3] Leader -uve-topic-19-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,531] INFO [Broker id=3] Leader -uve-topic-23-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,538] INFO [Broker id=3] Leader -uve-topic-10-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,541] INFO [Broker id=3] Leader -uve-topic-2-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,544] INFO [Broker id=3] Leader -uve-topic-28-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,547] INFO [Broker id=3] Leader -uve-topic-15-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,556] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,559] INFO [Broker id=3] Leader -uve-topic-2-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,561] INFO [Broker id=3] Leader -uve-topic-13-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,564] INFO [Broker id=3] Leader -uve-topic-26-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,567] INFO [Broker id=3] Leader -uve-topic-12-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,571] INFO [Broker id=3] Leader -uve-topic-25-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,574] INFO [Broker id=3] Leader -uve-topic-14-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,576] INFO [Broker id=3] Leader -uve-topic-27-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,579] INFO [Broker id=3] Leader -uve-topic-10-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,581] INFO [Broker id=3] Leader -uve-topic-23-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,585] INFO [Broker id=3] Leader -uve-topic-12-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,588] INFO [Broker id=3] Leader -uve-topic-25-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,591] INFO [Broker id=3] Leader -uve-topic-11-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,594] INFO [Broker id=3] Leader -uve-topic-24-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,596] INFO [Broker id=3] Leader -uve-topic-4-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,600] INFO [Broker id=3] Leader -uve-topic-8-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,602] INFO [Broker id=3] Leader -uve-topic-0-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,605] INFO [Broker id=3] Leader -uve-topic-18-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,608] INFO [Broker id=3] Leader -uve-topic-2-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,610] INFO [Broker id=3] Leader -uve-topic-1-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,613] INFO [Broker id=3] Leader structured_syslog_topic-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,616] INFO [Broker id=3] Leader -uve-topic-7-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,619] INFO [Broker id=3] Leader -uve-topic-14-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,621] INFO [Broker id=3] Leader -uve-topic-27-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,623] INFO [Broker id=3] Leader -uve-topic-6-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,625] INFO [Broker id=3] Leader -uve-topic-2-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,628] INFO [Broker id=3] Leader -uve-topic-18-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,630] INFO [Broker id=3] Leader -uve-topic-5-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,632] INFO [Broker id=3] Leader -uve-topic-9-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,635] INFO [Broker id=3] Leader -uve-topic-22-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,637] INFO [Broker id=3] Leader -uve-topic-13-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,640] INFO [Broker id=3] Leader -uve-topic-26-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,643] INFO [Broker id=3] Leader -uve-topic-1-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,646] INFO [Broker id=3] Leader -uve-topic-17-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,648] INFO [Broker id=3] Leader -uve-topic-18-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,651] INFO [Broker id=3] Leader -uve-topic-21-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,654] INFO [Broker id=3] Leader -uve-topic-20-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,657] INFO [Broker id=3] Leader -uve-topic-22-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,661] INFO [Broker id=3] Leader -uve-topic-3-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,663] INFO [Broker id=3] Leader -uve-topic-19-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,666] INFO [Broker id=3] Leader -uve-topic-10-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,669] INFO [Broker id=3] Leader -uve-topic-11-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,673] INFO [Broker id=3] Leader -uve-topic-23-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,675] INFO [Broker id=3] Leader -uve-topic-24-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,679] INFO [Broker id=3] Leader -uve-topic-28-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,682] INFO [Broker id=3] Leader -uve-topic-3-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,685] INFO [Broker id=3] Leader -uve-topic-15-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,687] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,690] INFO [Broker id=3] Leader -uve-topic-19-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,694] INFO [Broker id=3] Leader -uve-topic-17-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,696] INFO [Broker id=3] Leader -uve-topic-20-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,699] INFO [Broker id=3] Leader -uve-topic-29-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,701] INFO [Broker id=3] Leader -uve-topic-16-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,704] INFO [Broker id=3] Leader -uve-topic-21-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,707] INFO [Broker id=3] Leader -uve-topic-28-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,710] INFO [Broker id=3] Leader -uve-topic-29-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,712] INFO [Broker id=3] Leader -uve-topic-15-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,715] INFO [Broker id=3] Leader -uve-topic-16-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,718] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,721] INFO [Broker id=3] Leader -uve-topic-9-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,724] INFO [Broker id=3] Leader -uve-topic-1-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,727] INFO [Broker id=3] Leader -uve-topic-23-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,730] INFO [Broker id=3] Leader -uve-topic-10-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,733] INFO [Broker id=3] Leader structured_syslog_topic-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,736] INFO [Broker id=3] Leader -uve-topic-2-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,738] INFO [Broker id=3] Leader -uve-topic-22-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,740] INFO [Broker id=3] Leader -uve-topic-18-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,742] INFO [Broker id=3] Leader -uve-topic-6-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,744] INFO [Broker id=3] Leader -uve-topic-5-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,747] INFO [Broker id=3] Leader -uve-topic-14-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,762] INFO [Broker id=3] Leader -uve-topic-27-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,765] INFO [Broker id=3] Leader -uve-topic-7-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,768] INFO [Broker id=3] Leader -uve-topic-20-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,770] INFO [Broker id=3] Leader -uve-topic-0-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,773] INFO [Broker id=3] Leader -uve-topic-9-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,776] INFO [Broker id=3] Leader -uve-topic-1-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,779] INFO [Broker id=3] Leader -uve-topic-17-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,783] INFO [Broker id=3] Leader structured_syslog_topic-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,786] INFO [Broker id=3] Leader -uve-topic-5-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,789] INFO [Broker id=3] Leader -uve-topic-4-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,792] INFO [Broker id=3] Leader -uve-topic-11-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,794] INFO [Broker id=3] Leader -uve-topic-24-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,797] INFO [Broker id=3] Leader -uve-topic-13-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,800] INFO [Broker id=3] Leader -uve-topic-12-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,803] INFO [Broker id=3] Leader -uve-topic-26-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,805] INFO [Broker id=3] Leader -uve-topic-29-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,808] INFO [Broker id=3] Leader -uve-topic-16-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,811] INFO [Broker id=3] Leader -uve-topic-17-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,814] INFO [Broker id=3] Leader -uve-topic-22-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,817] INFO [Broker id=3] Leader -uve-topic-18-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,820] INFO [Broker id=3] Leader -uve-topic-21-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,823] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,826] INFO [Broker id=3] Leader -uve-topic-17-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,829] INFO [Broker id=3] Leader -uve-topic-23-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,833] INFO [Broker id=3] Leader -uve-topic-10-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,836] INFO [Broker id=3] Leader -uve-topic-12-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,839] INFO [Broker id=3] Leader -uve-topic-25-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,841] INFO [Broker id=3] Leader -uve-topic-11-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,844] INFO [Broker id=3] Leader -uve-topic-19-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,847] INFO [Broker id=3] Leader -uve-topic-21-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,850] INFO [Broker id=3] Leader -uve-topic-20-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,852] INFO [Broker id=3] Leader -uve-topic-28-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,861] INFO [Broker id=3] Leader -uve-topic-15-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,864] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,867] INFO [Broker id=3] Leader -uve-topic-22-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,869] INFO [Broker id=3] Leader -uve-topic-18-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,872] INFO [Broker id=3] Leader -uve-topic-14-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,875] INFO [Broker id=3] Leader -uve-topic-13-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,878] INFO [Broker id=3] Leader -uve-topic-26-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,882] INFO [Broker id=3] Leader -uve-topic-27-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,886] INFO [Broker id=3] Leader -uve-topic-6-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,888] INFO [Broker id=3] Leader -uve-topic-1-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,891] INFO [Broker id=3] Leader -uve-topic-0-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,893] INFO [Broker id=3] Leader -uve-topic-22-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,897] INFO [Broker id=3] Leader -uve-topic-4-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,900] INFO [Broker id=3] Leader -uve-topic-3-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,902] INFO [Broker id=3] Leader -uve-topic-9-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,905] INFO [Broker id=3] Leader -uve-topic-28-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,908] INFO [Broker id=3] Leader -uve-topic-29-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,910] INFO [Broker id=3] Leader -uve-topic-15-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,913] INFO [Broker id=3] Leader -uve-topic-16-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,916] INFO [Broker id=3] Leader -uve-topic-8-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,918] INFO [Broker id=3] Leader -uve-topic-2-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,921] INFO [Broker id=3] Leader -uve-topic-3-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,924] INFO [Broker id=3] Leader -uve-topic-9-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,927] INFO [Broker id=3] Leader -uve-topic-2-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,929] INFO [Broker id=3] Leader -uve-topic-1-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,933] INFO [Broker id=3] Leader structured_syslog_topic-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,936] INFO [Broker id=3] Leader -uve-topic-22-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,939] INFO [Broker id=3] Leader -uve-topic-1-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,942] INFO [Broker id=3] Leader -uve-topic-0-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,948] INFO [Broker id=3] Leader -uve-topic-9-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,952] INFO [Broker id=3] Leader -uve-topic-4-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,955] INFO [Broker id=3] Leader -uve-topic-6-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,959] INFO [Broker id=3] Leader -uve-topic-5-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,962] INFO [Broker id=3] Leader -uve-topic-9-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,965] INFO [Broker id=3] Leader -uve-topic-22-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,967] INFO [Broker id=3] Leader -uve-topic-1-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,969] INFO [Broker id=3] Leader -uve-topic-17-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,973] INFO [Broker id=3] Leader -uve-topic-3-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,975] INFO [Broker id=3] Leader -uve-topic-19-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,979] INFO [Broker id=3] Leader -uve-topic-4-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,981] INFO [Broker id=3] Leader -uve-topic-5-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,986] INFO [Broker id=3] Leader -uve-topic-20-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,989] INFO [Broker id=3] Leader -uve-topic-28-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,992] INFO [Broker id=3] Leader -uve-topic-3-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:46,994] INFO [Broker id=3] Leader -uve-topic-15-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,002] INFO [Broker id=3] Leader HEALTH_CHECK_TOPIC-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,004] INFO [Broker id=3] Leader -uve-topic-8-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,009] INFO [Broker id=3] Leader -uve-topic-0-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,012] INFO [Broker id=3] Leader -uve-topic-17-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,015] INFO [Broker id=3] Leader -uve-topic-20-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,017] INFO [Broker id=3] Leader -uve-topic-29-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,020] INFO [Broker id=3] Leader -uve-topic-16-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,032] INFO [Broker id=3] Leader -uve-topic-21-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,035] INFO [Broker id=3] Leader -uve-topic-2-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,038] INFO [Broker id=3] Leader -uve-topic-9-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,040] INFO [Broker id=3] Leader -uve-topic-1-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,044] INFO [Broker id=3] Leader -uve-topic-23-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,046] INFO [Broker id=3] Leader -uve-topic-10-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,049] INFO [Broker id=3] Leader -uve-topic-17-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,053] INFO [Broker id=3] Leader structured_syslog_topic-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,057] INFO [Broker id=3] Leader -uve-topic-2-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,059] INFO [Broker id=3] Leader -uve-topic-14-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,062] INFO [Broker id=3] Leader -uve-topic-27-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,066] INFO [Broker id=3] Leader -uve-topic-7-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,068] INFO [Broker id=3] Leader -uve-topic-6-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,071] INFO [Broker id=3] Leader -uve-topic-13-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,073] INFO [Broker id=3] Leader -uve-topic-26-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,076] INFO [Broker id=3] Leader -uve-topic-14-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,078] INFO [Broker id=3] Leader -uve-topic-8-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,081] INFO [Broker id=3] Leader -uve-topic-0-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,083] INFO [Broker id=3] Leader -uve-topic-21-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,086] INFO [Broker id=3] Leader -uve-topic-12-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,088] INFO [Broker id=3] Leader -uve-topic-25-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,090] INFO [Broker id=3] Leader -uve-topic-21-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,092] INFO [Broker id=3] Leader -uve-topic-0-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,095] INFO [Broker id=3] Leader -uve-topic-22-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,097] INFO [Broker id=3] Leader -uve-topic-9-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,099] INFO [Broker id=3] Leader -uve-topic-8-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,101] INFO [Broker id=3] Leader -uve-topic-29-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,103] INFO [Broker id=3] Leader -uve-topic-11-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,106] INFO [Broker id=3] Leader -uve-topic-24-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,108] INFO [Broker id=3] Leader -uve-topic-18-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,111] INFO [Broker id=3] Leader -uve-topic-29-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,115] INFO [Broker id=3] Leader -uve-topic-15-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,119] INFO [Broker id=3] Leader -uve-topic-16-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,122] INFO [Broker id=3] Leader -uve-topic-7-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [3] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-10 02:00:47,143] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 4 (state.change.logger)
[2025-02-10 02:00:59,642] INFO [Broker id=3] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 5 (state.change.logger)
[2025-02-10 02:05:46,341] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 6 from controller 2 for 320 partitions (state.change.logger)
[2025-02-10 02:05:46,352] INFO [Broker id=3] Follower -uve-topic-18-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,352] INFO [Broker id=3] Follower -uve-topic-29-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,352] INFO [Broker id=3] Follower -uve-topic-2-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,352] INFO [Broker id=3] 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,352] INFO [Broker id=3] 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,352] INFO [Broker id=3] 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,352] INFO [Broker id=3] 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,352] INFO [Broker id=3] 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,352] INFO [Broker id=3] 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,352] INFO [Broker id=3] 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,352] INFO [Broker id=3] Follower -uve-topic-6-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,352] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] Follower -uve-topic-23-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] Follower -uve-topic-29-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] Follower -uve-topic-2-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,353] INFO [Broker id=3] Follower -uve-topic-18-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] Follower -uve-topic-23-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] Follower -uve-topic-29-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] Follower -uve-topic-6-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,353] INFO [Broker id=3] 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,353] INFO [Broker id=3] 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,354] INFO [Broker id=3] 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,354] INFO [Broker id=3] Follower -uve-topic-29-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,354] INFO [Broker id=3] 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,354] INFO [Broker id=3] 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,354] INFO [Broker id=3] 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,355] INFO [Broker id=3] 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,356] INFO [Broker id=3] 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,356] INFO [Broker id=3] Follower -uve-topic-23-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,356] INFO [Broker id=3] 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,356] INFO [Broker id=3] 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,356] INFO [Broker id=3] Follower -uve-topic-29-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,356] INFO [Broker id=3] 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,357] INFO [Broker id=3] Follower -uve-topic-6-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,357] INFO [Broker id=3] Follower -uve-topic-29-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,357] INFO [Broker id=3] Follower -uve-topic-2-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] Follower -uve-topic-18-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] Follower -uve-topic-8-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,357] INFO [Broker id=3] 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,358] INFO [Broker id=3] 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,358] INFO [Broker id=3] 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,358] INFO [Broker id=3] 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,358] INFO [Broker id=3] 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,358] INFO [Broker id=3] Follower -uve-topic-18-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,358] INFO [Broker id=3] Follower -uve-topic-23-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,359] INFO [Broker id=3] 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,359] INFO [Broker id=3] 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,359] INFO [Broker id=3] 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,359] INFO [Broker id=3] 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,362] INFO [Broker id=3] 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,362] INFO [Broker id=3] 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,362] INFO [Broker id=3] Follower -uve-topic-2-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,362] INFO [Broker id=3] 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,362] INFO [Broker id=3] 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,362] INFO [Broker id=3] 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,362] INFO [Broker id=3] 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,362] INFO [Broker id=3] 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,362] INFO [Broker id=3] Follower -uve-topic-6-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,362] INFO [Broker id=3] Follower -uve-topic-8-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,362] INFO [Broker id=3] Follower -uve-topic-2-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,363] INFO [Broker id=3] 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,363] INFO [Broker id=3] 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,364] INFO [Broker id=3] Follower -uve-topic-8-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] Follower -uve-topic-6-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] Follower -uve-topic-6-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] 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,364] INFO [Broker id=3] Follower -uve-topic-6-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,364] INFO [Broker id=3] Follower -uve-topic-8-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,364] INFO [Broker id=3] Follower -uve-topic-2-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,365] INFO [Broker id=3] Follower structured_syslog_topic-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] Follower -uve-topic-20-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] Follower structured_syslog_topic-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] Follower -uve-topic-6-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] Follower -uve-topic-2-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] Follower -uve-topic-8-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,365] INFO [Broker id=3] 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,365] INFO [Broker id=3] 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,366] INFO [Broker id=3] Follower -uve-topic-8-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,366] INFO [Broker id=3] Follower structured_syslog_topic-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,366] INFO [Broker id=3] 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,366] INFO [Broker id=3] 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,366] INFO [Broker id=3] 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,366] INFO [Broker id=3] 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,366] INFO [Broker id=3] 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,366] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] Follower -uve-topic-20-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] Follower -uve-topic-20-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] Follower -uve-topic-8-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] Follower structured_syslog_topic-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,367] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] Follower -uve-topic-8-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] Follower -uve-topic-20-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,368] INFO [Broker id=3] 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,379] INFO [Broker id=3] Follower structured_syslog_topic-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,379] INFO [Broker id=3] 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,379] INFO [Broker id=3] 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,379] INFO [Broker id=3] 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,379] INFO [Broker id=3] Follower -uve-topic-8-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,379] INFO [Broker id=3] 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,379] INFO [Broker id=3] 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,379] INFO [Broker id=3] 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,379] INFO [Broker id=3] 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,380] INFO [Broker id=3] 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,380] INFO [Broker id=3] 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,383] INFO [Broker id=3] Follower -uve-topic-23-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] Follower -uve-topic-20-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] Follower structured_syslog_topic-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] Follower structured_syslog_topic-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] Follower -uve-topic-20-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] 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,383] INFO [Broker id=3] Follower -uve-topic-18-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,383] INFO [Broker id=3] Follower -uve-topic-23-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,384] INFO [Broker id=3] 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,384] INFO [Broker id=3] 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,384] INFO [Broker id=3] 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,384] INFO [Broker id=3] 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,384] INFO [Broker id=3] 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,384] INFO [Broker id=3] 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,384] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] Follower -uve-topic-8-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] Follower -uve-topic-29-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,385] INFO [Broker id=3] Follower -uve-topic-20-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,385] INFO [Broker id=3] Follower structured_syslog_topic-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] Follower -uve-topic-18-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] Follower -uve-topic-23-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,385] INFO [Broker id=3] 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,386] INFO [Broker id=3] Follower -uve-topic-18-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] Follower -uve-topic-2-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] Follower structured_syslog_topic-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] Follower -uve-topic-18-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] Follower -uve-topic-20-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] Follower -uve-topic-29-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] Follower -uve-topic-23-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] Follower -uve-topic-6-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] Follower -uve-topic-23-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,386] INFO [Broker id=3] 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,387] INFO [Broker id=3] Follower -uve-topic-20-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] Follower -uve-topic-18-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] Follower -uve-topic-29-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] Follower -uve-topic-2-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] Follower structured_syslog_topic-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] Follower -uve-topic-6-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] Follower -uve-topic-2-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] Follower -uve-topic-23-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] 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,387] INFO [Broker id=3] Follower -uve-topic-18-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] Follower -uve-topic-29-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-10 02:05:46,387] INFO [Broker id=3] 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,389] INFO [Broker id=3] 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,492] INFO [Broker id=3] Add 320 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 7 (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Handling LeaderAndIsr request correlationId 8 from controller 2 for 320 partitions (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-14-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-16-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-17-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-0-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-8-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-20-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-2-0 starts at leader epoch 7 from offset 84 with high watermark 84. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-6-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,549] INFO [Broker id=3] Follower -uve-topic-15-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-22-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-9-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-21-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-8-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-12-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-21-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-9-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-14-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-6-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-8-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-12-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-16-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-25-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-15-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-8-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-22-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-11-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-20-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-21-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-21-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-0-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-11-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-20-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,550] INFO [Broker id=3] Follower -uve-topic-9-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,551] INFO [Broker id=3] Follower structured_syslog_topic-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,551] INFO [Broker id=3] Follower -uve-topic-13-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,551] INFO [Broker id=3] Follower -uve-topic-7-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,551] INFO [Broker id=3] Follower -uve-topic-8-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,551] INFO [Broker id=3] Follower -uve-topic-12-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,551] INFO [Broker id=3] Follower -uve-topic-15-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-14-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-16-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-15-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-21-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-22-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-25-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-20-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-25-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-15-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,577] INFO [Broker id=3] Follower -uve-topic-22-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-9-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-13-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-12-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-7-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-14-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-8-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower structured_syslog_topic-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-1-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-20-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-11-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-16-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-3-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-5-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-15-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower structured_syslog_topic-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-1-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-20-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-22-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-9-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-13-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-12-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-25-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-7-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-11-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower structured_syslog_topic-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-14-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-16-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-8-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-4-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-28-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-16-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-25-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-27-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-26-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-9-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-5-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-20-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-11-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-4-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower structured_syslog_topic-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-5-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-13-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-7-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-3-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-22-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-14-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-8-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-1-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower structured_syslog_topic-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,582] INFO [Broker id=3] Follower -uve-topic-13-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower structured_syslog_topic-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-28-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-7-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-25-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-3-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-11-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-26-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-20-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-16-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-4-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-27-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-29-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-5-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-13-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-1-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-5-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower structured_syslog_topic-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-22-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-13-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-29-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-5-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-11-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-4-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-5-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower structured_syslog_topic-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-7-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-18-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-1-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-3-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-4-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-26-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-25-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-17-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-16-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-13-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-28-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-20-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-19-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-24-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-25-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-27-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-13-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-10-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-22-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-23-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-18-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-20-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-17-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-16-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-22-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower structured_syslog_topic-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-27-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-29-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-11-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-26-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-5-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-6-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-13-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,583] INFO [Broker id=3] Follower -uve-topic-1-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-28-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-4-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-7-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-25-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-3-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-10-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-23-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-19-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-24-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-4-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-17-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-16-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-25-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-3-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-0-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-19-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-4-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-11-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-24-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-5-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-6-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-27-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-18-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-10-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-22-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-23-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-24-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-26-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-29-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-28-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-7-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-1-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-3-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-4-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-19-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-17-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-23-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-10-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-19-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-6-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-5-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-0-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-4-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-1-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-2-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-18-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-24-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-3-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-28-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-27-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-7-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-24-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,584] INFO [Broker id=3] Follower -uve-topic-29-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-11-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-3-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-26-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-12-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-24-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-26-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-17-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-23-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-10-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-19-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-28-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-19-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-1-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-0-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-29-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-2-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-6-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-27-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-7-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-2-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-24-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-18-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-3-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-23-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-10-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-6-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-0-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-29-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-1-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-2-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-18-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-12-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-19-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-24-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-28-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-21-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-27-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-23-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-26-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,593] INFO [Broker id=3] Follower -uve-topic-14-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-10-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-19-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-17-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-18-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-2-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-23-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-10-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-15-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-27-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-23-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-10-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-12-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-24-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-0-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-14-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-6-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-2-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-18-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-26-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-17-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-21-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-23-0 starts at leader epoch 7 from offset 40 with high watermark 40. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-10-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-19-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-15-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-29-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-28-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-9-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-2-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-18-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-27-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-9-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-29-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower HEALTH_CHECK_TOPIC-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-18-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-17-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-12-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-21-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-15-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-26-0 starts at leader epoch 7 from offset 163 with high watermark 163. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-14-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-6-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-0-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-28-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-2-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-0-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-17-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-15-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-8-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-0-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-29-0 starts at leader epoch 7 from offset 69 with high watermark 69. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-9-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-2-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-14-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-6-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-8-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-21-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-12-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-21-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,594] INFO [Broker id=3] Follower -uve-topic-9-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-10 02:05:46,711] INFO [Broker id=3] Stopped fetchers as part of become-follower request from controller 2 epoch 5 with correlation id 8 for 320 partitions (state.change.logger)
[2025-02-10 02:05:46,751] INFO [Broker id=3] Add 320 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 5 with correlation id 9 (state.change.logger)