[2025-02-13 02:08:27,547] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 0 (state.change.logger)
[2025-02-13 02:08:27,590] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 1 from controller 1 for 960 partitions (state.change.logger)
[2025-02-13 02:08:29,022] INFO [Broker id=2] Follower -uve-topic-22-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,025] INFO [Broker id=2] Follower -uve-topic-23-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,026] INFO [Broker id=2] Follower -uve-topic-17-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,026] INFO [Broker id=2] Follower -uve-topic-16-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,027] INFO [Broker id=2] Follower -uve-topic-29-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,027] INFO [Broker id=2] Follower -uve-topic-2-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,028] INFO [Broker id=2] Follower -uve-topic-18-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,030] INFO [Broker id=2] Follower -uve-topic-27-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,030] INFO [Broker id=2] Follower -uve-topic-14-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,030] INFO [Broker id=2] Follower -uve-topic-5-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,032] INFO [Broker id=2] Follower -uve-topic-16-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,032] INFO [Broker id=2] Follower -uve-topic-29-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,032] INFO [Broker id=2] Follower -uve-topic-17-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,033] INFO [Broker id=2] Follower -uve-topic-21-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,034] INFO [Broker id=2] Follower -uve-topic-11-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,035] INFO [Broker id=2] Follower -uve-topic-24-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,035] INFO [Broker id=2] Follower -uve-topic-13-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,035] INFO [Broker id=2] Follower -uve-topic-26-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,037] INFO [Broker id=2] Follower -uve-topic-8-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,037] INFO [Broker id=2] Follower -uve-topic-0-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,038] INFO [Broker id=2] Follower -uve-topic-17-0 starts at leader epoch 3 from offset 161 with high watermark 161. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,039] INFO [Broker id=2] Follower -uve-topic-9-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,040] INFO [Broker id=2] Follower -uve-topic-0-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,040] INFO [Broker id=2] Follower -uve-topic-20-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,042] INFO [Broker id=2] Follower -uve-topic-1-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,043] INFO [Broker id=2] Follower -uve-topic-3-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,044] INFO [Broker id=2] Follower -uve-topic-2-0 starts at leader epoch 3 from offset 538 with high watermark 538. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,045] INFO [Broker id=2] Follower -uve-topic-7-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,045] INFO [Broker id=2] Follower -uve-topic-6-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,045] INFO [Broker id=2] Follower -uve-topic-15-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,046] INFO [Broker id=2] Follower -uve-topic-28-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,047] INFO [Broker id=2] Follower -uve-topic-6-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,047] INFO [Broker id=2] Follower -uve-topic-7-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,047] INFO [Broker id=2] Follower -uve-topic-22-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,048] INFO [Broker id=2] Follower -uve-topic-0-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,049] INFO [Broker id=2] Follower -uve-topic-9-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,049] INFO [Broker id=2] Follower -uve-topic-21-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,050] INFO [Broker id=2] Follower structured_syslog_topic-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,050] INFO [Broker id=2] Follower -uve-topic-5-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,051] INFO [Broker id=2] Follower -uve-topic-4-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,052] INFO [Broker id=2] Follower -uve-topic-17-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,052] INFO [Broker id=2] Follower -uve-topic-8-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,052] INFO [Broker id=2] Follower -uve-topic-3-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,053] INFO [Broker id=2] Follower -uve-topic-4-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,053] INFO [Broker id=2] Follower -uve-topic-10-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,054] INFO [Broker id=2] Follower -uve-topic-23-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,055] INFO [Broker id=2] Follower -uve-topic-25-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,056] INFO [Broker id=2] Follower -uve-topic-20-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,058] INFO [Broker id=2] Follower -uve-topic-12-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,058] INFO [Broker id=2] Follower -uve-topic-19-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,060] INFO [Broker id=2] Follower -uve-topic-29-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,061] INFO [Broker id=2] Follower -uve-topic-16-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,068] INFO [Broker id=2] Follower -uve-topic-8-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,068] INFO [Broker id=2] Follower -uve-topic-21-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,068] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-14 starts at leader epoch 3 from offset 5 with high watermark 5. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,069] INFO [Broker id=2] Follower -uve-topic-2-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,069] INFO [Broker id=2] Follower -uve-topic-9-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,069] INFO [Broker id=2] Follower -uve-topic-18-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,069] INFO [Broker id=2] Follower -uve-topic-10-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,070] INFO [Broker id=2] Follower -uve-topic-23-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,070] INFO [Broker id=2] Follower -uve-topic-14-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,071] INFO [Broker id=2] Follower -uve-topic-27-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,071] INFO [Broker id=2] Follower -uve-topic-7-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,072] INFO [Broker id=2] Follower -uve-topic-6-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,074] INFO [Broker id=2] Follower -uve-topic-8-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,074] INFO [Broker id=2] Follower -uve-topic-21-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,074] INFO [Broker id=2] Follower -uve-topic-20-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,075] INFO [Broker id=2] Follower -uve-topic-0-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,075] INFO [Broker id=2] Follower -uve-topic-17-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,075] INFO [Broker id=2] Follower -uve-topic-29-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,075] INFO [Broker id=2] Follower -uve-topic-16-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,075] INFO [Broker id=2] Follower -uve-topic-4-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,075] INFO [Broker id=2] Follower -uve-topic-13-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,076] INFO [Broker id=2] Follower -uve-topic-26-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,076] INFO [Broker id=2] Follower -uve-topic-6-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,077] INFO [Broker id=2] Follower -uve-topic-5-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,078] INFO [Broker id=2] Follower -uve-topic-12-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,078] INFO [Broker id=2] Follower -uve-topic-26-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,079] INFO [Broker id=2] Follower -uve-topic-25-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,079] INFO [Broker id=2] Follower -uve-topic-29-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,080] INFO [Broker id=2] Follower -uve-topic-16-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,080] INFO [Broker id=2] Follower -uve-topic-10-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,081] INFO [Broker id=2] Follower -uve-topic-23-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,089] INFO [Broker id=2] Follower -uve-topic-19-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,089] INFO [Broker id=2] Follower -uve-topic-25-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,094] INFO [Broker id=2] Follower -uve-topic-11-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,095] INFO [Broker id=2] Follower -uve-topic-24-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,095] INFO [Broker id=2] Follower -uve-topic-19-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,095] INFO [Broker id=2] Follower -uve-topic-28-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,095] INFO [Broker id=2] Follower -uve-topic-15-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,095] INFO [Broker id=2] Follower -uve-topic-20-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,096] INFO [Broker id=2] Follower -uve-topic-29-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,096] INFO [Broker id=2] Follower -uve-topic-16-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,096] INFO [Broker id=2] Follower -uve-topic-7-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,096] INFO [Broker id=2] Follower -uve-topic-8-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,097] INFO [Broker id=2] Follower -uve-topic-22-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,100] INFO [Broker id=2] Follower -uve-topic-18-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,100] INFO [Broker id=2] Follower -uve-topic-24-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,100] INFO [Broker id=2] Follower -uve-topic-11-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,100] INFO [Broker id=2] Follower -uve-topic-17-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,101] INFO [Broker id=2] Follower -uve-topic-22-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,101] INFO [Broker id=2] Follower -uve-topic-1-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,101] INFO [Broker id=2] Follower structured_syslog_topic-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,101] INFO [Broker id=2] Follower -uve-topic-5-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,101] INFO [Broker id=2] Follower -uve-topic-15-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,102] INFO [Broker id=2] Follower -uve-topic-28-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,102] INFO [Broker id=2] Follower -uve-topic-20-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,103] INFO [Broker id=2] Follower -uve-topic-21-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,103] INFO [Broker id=2] Follower -uve-topic-7-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,113] INFO [Broker id=2] Follower -uve-topic-3-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,114] INFO [Broker id=2] Follower -uve-topic-8-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,115] INFO [Broker id=2] Follower -uve-topic-21-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,115] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-11 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,116] INFO [Broker id=2] Follower -uve-topic-0-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,116] INFO [Broker id=2] Follower -uve-topic-24-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,118] INFO [Broker id=2] Follower -uve-topic-23-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,118] INFO [Broker id=2] Follower -uve-topic-11-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,118] INFO [Broker id=2] Follower -uve-topic-10-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,118] INFO [Broker id=2] Follower -uve-topic-19-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,119] INFO [Broker id=2] Follower -uve-topic-20-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,121] INFO [Broker id=2] Follower -uve-topic-3-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,122] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-8 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,123] INFO [Broker id=2] Follower -uve-topic-7-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,123] INFO [Broker id=2] Follower -uve-topic-17-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,124] INFO [Broker id=2] Follower -uve-topic-16-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,125] INFO [Broker id=2] Follower -uve-topic-29-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,125] INFO [Broker id=2] Follower -uve-topic-0-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,126] INFO [Broker id=2] Follower structured_syslog_topic-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,126] INFO [Broker id=2] Follower -uve-topic-9-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,127] INFO [Broker id=2] Follower -uve-topic-6-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,128] INFO [Broker id=2] Follower -uve-topic-26-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,128] INFO [Broker id=2] Follower -uve-topic-13-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,129] INFO [Broker id=2] Follower -uve-topic-5-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,129] INFO [Broker id=2] Follower -uve-topic-7-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,129] INFO [Broker id=2] Follower -uve-topic-8-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,129] INFO [Broker id=2] Follower -uve-topic-19-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,129] INFO [Broker id=2] Follower -uve-topic-4-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,129] INFO [Broker id=2] Follower -uve-topic-25-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,130] INFO [Broker id=2] Follower -uve-topic-20-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,130] INFO [Broker id=2] Follower -uve-topic-12-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,130] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-27 starts at leader epoch 2 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,131] INFO [Broker id=2] Follower -uve-topic-16-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,131] INFO [Broker id=2] Follower -uve-topic-29-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,131] INFO [Broker id=2] Follower -uve-topic-8-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,131] INFO [Broker id=2] Follower -uve-topic-18-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,131] INFO [Broker id=2] Follower -uve-topic-1-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,131] INFO [Broker id=2] Follower -uve-topic-22-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,132] INFO [Broker id=2] Follower -uve-topic-23-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,132] INFO [Broker id=2] Follower -uve-topic-10-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,132] INFO [Broker id=2] Follower -uve-topic-2-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,132] INFO [Broker id=2] Follower -uve-topic-18-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,132] INFO [Broker id=2] Follower -uve-topic-27-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,133] INFO [Broker id=2] Follower -uve-topic-14-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,133] INFO [Broker id=2] Follower -uve-topic-15-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,133] INFO [Broker id=2] Follower -uve-topic-28-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,133] INFO [Broker id=2] Follower -uve-topic-28-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,134] INFO [Broker id=2] Follower -uve-topic-27-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,134] INFO [Broker id=2] Follower -uve-topic-14-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,134] INFO [Broker id=2] Follower -uve-topic-8-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,134] INFO [Broker id=2] Follower -uve-topic-22-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,134] INFO [Broker id=2] Follower -uve-topic-16-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,134] INFO [Broker id=2] Follower -uve-topic-15-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,135] INFO [Broker id=2] Follower -uve-topic-29-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,135] INFO [Broker id=2] Follower -uve-topic-28-0 starts at leader epoch 3 from offset 1720 with high watermark 1720. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,135] INFO [Broker id=2] Follower -uve-topic-21-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,135] INFO [Broker id=2] Follower -uve-topic-17-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,135] INFO [Broker id=2] Follower -uve-topic-20-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,136] INFO [Broker id=2] Follower -uve-topic-21-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,137] INFO [Broker id=2] Follower structured_syslog_topic-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,137] INFO [Broker id=2] Follower -uve-topic-25-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,138] INFO [Broker id=2] Follower -uve-topic-12-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,138] INFO [Broker id=2] Follower -uve-topic-24-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,139] INFO [Broker id=2] Follower -uve-topic-11-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,139] INFO [Broker id=2] Follower -uve-topic-26-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,140] INFO [Broker id=2] Follower -uve-topic-13-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,140] INFO [Broker id=2] Follower -uve-topic-15-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,140] INFO [Broker id=2] Follower -uve-topic-28-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,141] INFO [Broker id=2] Follower -uve-topic-20-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,141] INFO [Broker id=2] Follower -uve-topic-7-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,141] INFO [Broker id=2] Follower -uve-topic-3-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,143] INFO [Broker id=2] Follower -uve-topic-19-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,144] INFO [Broker id=2] Follower -uve-topic-23-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,146] INFO [Broker id=2] Follower -uve-topic-10-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,147] INFO [Broker id=2] Follower -uve-topic-25-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,147] INFO [Broker id=2] Follower -uve-topic-12-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,148] INFO [Broker id=2] Follower -uve-topic-24-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,149] INFO [Broker id=2] Follower -uve-topic-11-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,149] INFO [Broker id=2] Follower -uve-topic-15-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,150] INFO [Broker id=2] Follower -uve-topic-28-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,151] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-5 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,152] INFO [Broker id=2] Follower -uve-topic-20-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,155] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-24 starts at leader epoch 2 from offset 7 with high watermark 7. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,159] INFO [Broker id=2] Follower -uve-topic-6-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,160] INFO [Broker id=2] Follower -uve-topic-9-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,171] INFO [Broker id=2] Follower -uve-topic-19-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,174] INFO [Broker id=2] Follower -uve-topic-18-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,174] INFO [Broker id=2] Follower -uve-topic-22-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,178] INFO [Broker id=2] Follower -uve-topic-10-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,178] INFO [Broker id=2] Follower -uve-topic-23-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,179] INFO [Broker id=2] Follower -uve-topic-18-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,179] INFO [Broker id=2] Follower -uve-topic-17-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,179] INFO [Broker id=2] Follower -uve-topic-22-0 starts at leader epoch 3 from offset 2708 with high watermark 2708. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,179] INFO [Broker id=2] Follower -uve-topic-14-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,181] INFO [Broker id=2] Follower -uve-topic-27-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,182] INFO [Broker id=2] Follower -uve-topic-5-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,182] INFO [Broker id=2] Follower -uve-topic-21-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,185] INFO [Broker id=2] Follower -uve-topic-28-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,185] INFO [Broker id=2] Follower -uve-topic-15-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,185] INFO [Broker id=2] Follower -uve-topic-16-0 starts at leader epoch 3 from offset 161 with high watermark 161. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,185] INFO [Broker id=2] Follower -uve-topic-17-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,186] INFO [Broker id=2] Follower -uve-topic-13-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,186] INFO [Broker id=2] Follower -uve-topic-12-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,186] INFO [Broker id=2] Follower -uve-topic-25-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,186] INFO [Broker id=2] Follower -uve-topic-26-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,186] INFO [Broker id=2] Follower -uve-topic-14-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,188] INFO [Broker id=2] Follower -uve-topic-27-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,188] INFO [Broker id=2] Follower -uve-topic-7-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,188] INFO [Broker id=2] Follower -uve-topic-2-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,189] INFO [Broker id=2] Follower -uve-topic-14-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,189] INFO [Broker id=2] Follower -uve-topic-27-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,189] INFO [Broker id=2] Follower -uve-topic-28-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,189] INFO [Broker id=2] Follower -uve-topic-15-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,190] INFO [Broker id=2] Follower -uve-topic-7-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,190] INFO [Broker id=2] Follower -uve-topic-0-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,191] INFO [Broker id=2] Follower -uve-topic-1-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,191] INFO [Broker id=2] Follower -uve-topic-2-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,191] INFO [Broker id=2] Follower -uve-topic-9-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,191] INFO [Broker id=2] Follower -uve-topic-8-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,192] INFO [Broker id=2] Follower structured_syslog_topic-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,193] INFO [Broker id=2] Follower -uve-topic-1-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,193] INFO [Broker id=2] Follower -uve-topic-0-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,194] INFO [Broker id=2] Follower structured_syslog_topic-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,205] INFO [Broker id=2] Follower -uve-topic-4-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,215] INFO [Broker id=2] Follower -uve-topic-13-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,216] INFO [Broker id=2] Follower -uve-topic-26-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-6-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-8-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-7-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-20-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-11-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-24-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-29-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-16-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-3-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-11-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,217] INFO [Broker id=2] Follower -uve-topic-4-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,223] INFO [Broker id=2] Follower -uve-topic-5-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,224] INFO [Broker id=2] Follower -uve-topic-6-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,224] INFO [Broker id=2] Follower -uve-topic-2-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,224] INFO [Broker id=2] Follower -uve-topic-1-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,226] INFO [Broker id=2] Follower -uve-topic-18-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,228] INFO [Broker id=2] Follower structured_syslog_topic-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,228] INFO [Broker id=2] Follower -uve-topic-3-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,228] INFO [Broker id=2] Follower -uve-topic-2-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,230] INFO [Broker id=2] Follower -uve-topic-14-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,231] INFO [Broker id=2] Follower -uve-topic-27-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,231] INFO [Broker id=2] Follower -uve-topic-28-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,231] INFO [Broker id=2] Follower -uve-topic-15-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,231] INFO [Broker id=2] Follower -uve-topic-8-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,231] INFO [Broker id=2] Follower -uve-topic-1-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,231] INFO [Broker id=2] Follower -uve-topic-0-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,231] INFO [Broker id=2] Follower -uve-topic-20-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,237] INFO [Broker id=2] Follower structured_syslog_topic-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,238] INFO [Broker id=2] Follower -uve-topic-9-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,238] INFO [Broker id=2] Follower -uve-topic-22-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,239] INFO [Broker id=2] Follower -uve-topic-13-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,239] INFO [Broker id=2] Follower -uve-topic-12-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,240] INFO [Broker id=2] Follower -uve-topic-25-0 starts at leader epoch 3 from offset 1687 with high watermark 1687. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,241] INFO [Broker id=2] Follower -uve-topic-26-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-5-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-12-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-25-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-13-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-26-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-7-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-6-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-28-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-15-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-7-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-19-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-10-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,242] INFO [Broker id=2] Follower -uve-topic-11-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,243] INFO [Broker id=2] Follower -uve-topic-24-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,243] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-21 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,243] INFO [Broker id=2] Follower -uve-topic-19-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,243] INFO [Broker id=2] Follower structured_syslog_topic-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,244] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-2 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,244] INFO [Broker id=2] Follower -uve-topic-14-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,245] INFO [Broker id=2] Follower -uve-topic-27-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,245] INFO [Broker id=2] Follower -uve-topic-10-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,245] INFO [Broker id=2] Follower -uve-topic-23-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,245] INFO [Broker id=2] Follower -uve-topic-17-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,245] INFO [Broker id=2] Follower -uve-topic-9-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,245] INFO [Broker id=2] Follower -uve-topic-14-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,246] INFO [Broker id=2] Follower -uve-topic-27-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,246] INFO [Broker id=2] Follower -uve-topic-6-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,247] INFO [Broker id=2] Follower -uve-topic-29-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,247] INFO [Broker id=2] Follower -uve-topic-16-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,248] INFO [Broker id=2] Follower -uve-topic-21-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,248] INFO [Broker id=2] Follower -uve-topic-0-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,248] INFO [Broker id=2] Follower -uve-topic-4-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,248] INFO [Broker id=2] Follower -uve-topic-8-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,248] INFO [Broker id=2] Follower -uve-topic-28-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,249] INFO [Broker id=2] Follower -uve-topic-14-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,249] INFO [Broker id=2] Follower -uve-topic-27-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,249] INFO [Broker id=2] Follower -uve-topic-29-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,249] INFO [Broker id=2] Follower -uve-topic-16-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,250] INFO [Broker id=2] Follower -uve-topic-10-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,250] INFO [Broker id=2] Follower -uve-topic-23-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,251] INFO [Broker id=2] Follower -uve-topic-12-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,252] INFO [Broker id=2] Follower -uve-topic-25-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,252] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-18 starts at leader epoch 2 from offset 1 with high watermark 1. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,252] INFO [Broker id=2] Follower -uve-topic-27-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,252] INFO [Broker id=2] Follower -uve-topic-13-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,252] INFO [Broker id=2] Follower -uve-topic-26-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,252] INFO [Broker id=2] Follower -uve-topic-18-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,253] INFO [Broker id=2] Follower -uve-topic-9-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,254] INFO [Broker id=2] Follower -uve-topic-0-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,255] INFO [Broker id=2] Follower -uve-topic-1-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,255] INFO [Broker id=2] Follower -uve-topic-2-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,255] INFO [Broker id=2] Follower structured_syslog_topic-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,255] INFO [Broker id=2] Follower -uve-topic-6-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,256] INFO [Broker id=2] Follower -uve-topic-5-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,256] INFO [Broker id=2] Follower -uve-topic-14-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,256] INFO [Broker id=2] Follower -uve-topic-27-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,256] INFO [Broker id=2] Follower -uve-topic-5-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,256] INFO [Broker id=2] Follower -uve-topic-13-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,256] INFO [Broker id=2] Follower -uve-topic-6-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,257] INFO [Broker id=2] Follower -uve-topic-7-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,257] INFO [Broker id=2] Follower -uve-topic-8-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,257] INFO [Broker id=2] Follower -uve-topic-20-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,257] INFO [Broker id=2] Follower -uve-topic-11-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,257] INFO [Broker id=2] Follower -uve-topic-24-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,260] INFO [Broker id=2] Follower -uve-topic-4-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,260] INFO [Broker id=2] Follower -uve-topic-3-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,260] INFO [Broker id=2] Follower structured_syslog_topic-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,261] INFO [Broker id=2] Follower -uve-topic-5-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,261] INFO [Broker id=2] Follower -uve-topic-7-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,261] INFO [Broker id=2] Follower -uve-topic-13-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,261] INFO [Broker id=2] Follower -uve-topic-26-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,262] INFO [Broker id=2] Follower -uve-topic-6-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,262] INFO [Broker id=2] Follower -uve-topic-3-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,263] INFO [Broker id=2] Follower -uve-topic-2-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,263] INFO [Broker id=2] Follower -uve-topic-22-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,264] INFO [Broker id=2] Follower -uve-topic-19-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,264] INFO [Broker id=2] Follower structured_syslog_topic-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,266] INFO [Broker id=2] Follower -uve-topic-14-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,267] INFO [Broker id=2] Follower -uve-topic-9-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,267] INFO [Broker id=2] Follower -uve-topic-8-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,267] INFO [Broker id=2] Follower -uve-topic-21-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,267] INFO [Broker id=2] Follower -uve-topic-28-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,267] INFO [Broker id=2] Follower -uve-topic-15-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,268] INFO [Broker id=2] Follower -uve-topic-1-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,269] INFO [Broker id=2] Follower -uve-topic-0-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,270] INFO [Broker id=2] Follower -uve-topic-17-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,270] INFO [Broker id=2] Follower structured_syslog_topic-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,271] INFO [Broker id=2] Follower -uve-topic-13-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,271] INFO [Broker id=2] Follower -uve-topic-26-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,271] INFO [Broker id=2] Follower -uve-topic-4-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,273] INFO [Broker id=2] Follower structured_syslog_topic-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,273] INFO [Broker id=2] Follower -uve-topic-28-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,273] INFO [Broker id=2] Follower -uve-topic-15-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,274] INFO [Broker id=2] Follower -uve-topic-0-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,275] INFO [Broker id=2] Follower -uve-topic-7-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,275] INFO [Broker id=2] Follower -uve-topic-20-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,276] INFO [Broker id=2] Follower -uve-topic-28-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,276] INFO [Broker id=2] Follower -uve-topic-15-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,276] INFO [Broker id=2] Follower -uve-topic-12-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,276] INFO [Broker id=2] Follower -uve-topic-25-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,277] INFO [Broker id=2] Follower -uve-topic-3-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,279] INFO [Broker id=2] Follower -uve-topic-19-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,280] INFO [Broker id=2] Follower -uve-topic-4-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,280] INFO [Broker id=2] Follower -uve-topic-11-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,281] INFO [Broker id=2] Follower -uve-topic-24-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,285] INFO [Broker id=2] Follower structured_syslog_topic-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,285] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-15 starts at leader epoch 2 from offset 6 with high watermark 6. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,290] INFO [Broker id=2] Follower -uve-topic-6-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,290] INFO [Broker id=2] Follower -uve-topic-13-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,290] INFO [Broker id=2] Follower -uve-topic-26-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,290] INFO [Broker id=2] Follower -uve-topic-14-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,291] INFO [Broker id=2] Follower -uve-topic-27-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,292] INFO [Broker id=2] Follower -uve-topic-18-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,293] INFO [Broker id=2] Follower -uve-topic-22-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,298] INFO [Broker id=2] Follower -uve-topic-10-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,304] INFO [Broker id=2] Follower -uve-topic-23-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,305] INFO [Broker id=2] Follower -uve-topic-6-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,306] INFO [Broker id=2] Follower -uve-topic-20-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,308] INFO [Broker id=2] Follower -uve-topic-21-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,309] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-25 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,310] INFO [Broker id=2] Follower -uve-topic-16-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,312] INFO [Broker id=2] Follower -uve-topic-29-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,313] INFO [Broker id=2] Follower -uve-topic-21-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,313] INFO [Broker id=2] Follower -uve-topic-4-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,313] INFO [Broker id=2] Follower -uve-topic-27-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,313] INFO [Broker id=2] Follower -uve-topic-14-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,313] INFO [Broker id=2] Follower -uve-topic-16-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,313] INFO [Broker id=2] Follower -uve-topic-29-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,314] INFO [Broker id=2] Follower -uve-topic-2-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,314] INFO [Broker id=2] Follower -uve-topic-2-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,314] INFO [Broker id=2] Follower -uve-topic-1-0 starts at leader epoch 0 from offset 542 with high watermark 541. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,314] INFO [Broker id=2] Follower -uve-topic-3-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,318] INFO [Broker id=2] Follower -uve-topic-26-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,319] INFO [Broker id=2] Follower -uve-topic-13-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,319] INFO [Broker id=2] Follower -uve-topic-5-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,319] INFO [Broker id=2] Follower -uve-topic-9-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,320] INFO [Broker id=2] Follower -uve-topic-17-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,321] INFO [Broker id=2] Follower -uve-topic-1-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,321] INFO [Broker id=2] Follower -uve-topic-8-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,321] INFO [Broker id=2] Follower structured_syslog_topic-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,323] INFO [Broker id=2] Follower -uve-topic-5-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,324] INFO [Broker id=2] Follower -uve-topic-22-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,324] INFO [Broker id=2] Follower -uve-topic-26-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,325] INFO [Broker id=2] Follower -uve-topic-13-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,325] INFO [Broker id=2] Follower -uve-topic-5-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,326] INFO [Broker id=2] Follower -uve-topic-16-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,326] INFO [Broker id=2] Follower -uve-topic-29-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,326] INFO [Broker id=2] Follower -uve-topic-15-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,327] INFO [Broker id=2] Follower -uve-topic-28-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,328] INFO [Broker id=2] Follower -uve-topic-8-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,328] INFO [Broker id=2] Follower -uve-topic-5-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,328] INFO [Broker id=2] Follower -uve-topic-4-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,328] INFO [Broker id=2] Follower -uve-topic-24-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,329] INFO [Broker id=2] Follower -uve-topic-11-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,329] INFO [Broker id=2] Follower -uve-topic-4-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,329] INFO [Broker id=2] Follower structured_syslog_topic-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,329] INFO [Broker id=2] Follower -uve-topic-5-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,330] INFO [Broker id=2] Follower -uve-topic-7-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,330] INFO [Broker id=2] Follower -uve-topic-18-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,332] INFO [Broker id=2] Follower -uve-topic-1-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,332] INFO [Broker id=2] Follower -uve-topic-3-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,332] INFO [Broker id=2] Follower -uve-topic-19-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,332] INFO [Broker id=2] Follower structured_syslog_topic-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,333] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-12 starts at leader epoch 2 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,334] INFO [Broker id=2] Follower -uve-topic-4-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,334] INFO [Broker id=2] Follower -uve-topic-25-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,335] INFO [Broker id=2] Follower -uve-topic-26-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,336] INFO [Broker id=2] Follower -uve-topic-12-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,338] INFO [Broker id=2] Follower -uve-topic-13-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,338] INFO [Broker id=2] Follower -uve-topic-4-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,339] INFO [Broker id=2] Follower -uve-topic-0-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,339] INFO [Broker id=2] Follower -uve-topic-17-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,339] INFO [Broker id=2] Follower -uve-topic-16-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,339] INFO [Broker id=2] Follower -uve-topic-29-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,340] INFO [Broker id=2] Follower -uve-topic-2-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,340] INFO [Broker id=2] Follower -uve-topic-22-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,340] INFO [Broker id=2] Follower -uve-topic-9-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,340] INFO [Broker id=2] Follower -uve-topic-21-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,340] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-3 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,340] INFO [Broker id=2] Follower -uve-topic-17-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,342] INFO [Broker id=2] Follower -uve-topic-26-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,343] INFO [Broker id=2] Follower -uve-topic-13-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,343] INFO [Broker id=2] Follower -uve-topic-15-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,343] INFO [Broker id=2] Follower -uve-topic-28-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,343] INFO [Broker id=2] Follower -uve-topic-20-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,344] INFO [Broker id=2] Follower -uve-topic-21-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,344] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-22 starts at leader epoch 3 from offset 6 with high watermark 6. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,344] INFO [Broker id=2] Follower -uve-topic-27-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,344] INFO [Broker id=2] Follower -uve-topic-14-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,344] INFO [Broker id=2] Follower -uve-topic-25-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,345] INFO [Broker id=2] Follower -uve-topic-19-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,345] INFO [Broker id=2] Follower -uve-topic-20-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,345] INFO [Broker id=2] Follower -uve-topic-10-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,346] INFO [Broker id=2] Follower -uve-topic-24-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,346] INFO [Broker id=2] Follower -uve-topic-23-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,346] INFO [Broker id=2] Follower -uve-topic-25-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,347] INFO [Broker id=2] Follower -uve-topic-12-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,347] INFO [Broker id=2] Follower -uve-topic-27-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,348] INFO [Broker id=2] Follower -uve-topic-26-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,348] INFO [Broker id=2] Follower -uve-topic-13-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,348] INFO [Broker id=2] Follower -uve-topic-14-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,348] INFO [Broker id=2] Follower -uve-topic-6-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,348] INFO [Broker id=2] Follower -uve-topic-10-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,349] INFO [Broker id=2] Follower -uve-topic-22-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,350] INFO [Broker id=2] Follower -uve-topic-23-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,350] INFO [Broker id=2] Follower -uve-topic-18-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,350] INFO [Broker id=2] Follower -uve-topic-5-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,351] INFO [Broker id=2] Follower -uve-topic-25-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,351] INFO [Broker id=2] Follower -uve-topic-12-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,351] INFO [Broker id=2] Follower -uve-topic-18-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,351] INFO [Broker id=2] Follower -uve-topic-17-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,351] INFO [Broker id=2] Follower -uve-topic-20-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,351] INFO [Broker id=2] Follower -uve-topic-21-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,352] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-19 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,352] INFO [Broker id=2] Follower -uve-topic-22-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,352] INFO [Broker id=2] Follower -uve-topic-17-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,352] INFO [Broker id=2] Follower -uve-topic-16-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,353] INFO [Broker id=2] Follower -uve-topic-29-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,353] INFO [Broker id=2] Follower -uve-topic-21-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,353] INFO [Broker id=2] Follower structured_syslog_topic-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,354] INFO [Broker id=2] Follower -uve-topic-20-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,355] INFO [Broker id=2] Follower -uve-topic-27-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,355] INFO [Broker id=2] Follower -uve-topic-14-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,355] INFO [Broker id=2] Follower -uve-topic-16-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,355] INFO [Broker id=2] Follower -uve-topic-15-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,355] INFO [Broker id=2] Follower -uve-topic-29-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,356] INFO [Broker id=2] Follower -uve-topic-28-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,356] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-0 starts at leader epoch 2 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,357] INFO [Broker id=2] Follower -uve-topic-25-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,358] INFO [Broker id=2] Follower -uve-topic-12-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,358] INFO [Broker id=2] Follower -uve-topic-24-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,358] INFO [Broker id=2] Follower -uve-topic-11-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,358] INFO [Broker id=2] Follower -uve-topic-26-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,358] INFO [Broker id=2] Follower -uve-topic-13-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,359] INFO [Broker id=2] Follower -uve-topic-12-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,359] INFO [Broker id=2] Follower -uve-topic-13-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,359] INFO [Broker id=2] Follower -uve-topic-5-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,359] INFO [Broker id=2] Follower -uve-topic-6-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,359] INFO [Broker id=2] Follower -uve-topic-9-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,360] INFO [Broker id=2] Follower -uve-topic-1-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,360] INFO [Broker id=2] Follower -uve-topic-8-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,379] INFO [Broker id=2] Follower -uve-topic-15-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,379] INFO [Broker id=2] Follower -uve-topic-28-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,379] INFO [Broker id=2] Follower -uve-topic-0-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,379] INFO [Broker id=2] Follower -uve-topic-7-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,380] INFO [Broker id=2] Follower -uve-topic-4-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,380] INFO [Broker id=2] Follower -uve-topic-3-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,380] INFO [Broker id=2] Follower -uve-topic-25-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,381] INFO [Broker id=2] Follower -uve-topic-12-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,381] INFO [Broker id=2] Follower -uve-topic-19-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,381] INFO [Broker id=2] Follower structured_syslog_topic-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,381] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-9 starts at leader epoch 2 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,382] INFO [Broker id=2] Follower -uve-topic-7-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,382] INFO [Broker id=2] Follower -uve-topic-6-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,382] INFO [Broker id=2] Follower -uve-topic-10-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,382] INFO [Broker id=2] Follower -uve-topic-27-0 starts at leader epoch 3 from offset 1626 with high watermark 1626. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,383] INFO [Broker id=2] Follower -uve-topic-23-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,383] INFO [Broker id=2] Follower -uve-topic-14-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,383] INFO [Broker id=2] Follower -uve-topic-2-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,383] INFO [Broker id=2] Follower -uve-topic-18-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,383] INFO [Broker id=2] Follower -uve-topic-19-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,384] INFO [Broker id=2] Follower -uve-topic-22-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,385] INFO [Broker id=2] Follower -uve-topic-24-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,385] INFO [Broker id=2] Follower -uve-topic-11-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,385] INFO [Broker id=2] Follower -uve-topic-10-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,386] INFO [Broker id=2] Follower -uve-topic-23-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,386] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-28 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,387] INFO [Broker id=2] Follower -uve-topic-4-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,387] INFO [Broker id=2] Follower -uve-topic-25-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,388] INFO [Broker id=2] Follower -uve-topic-12-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,388] INFO [Broker id=2] Follower -uve-topic-5-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,389] INFO [Broker id=2] Follower -uve-topic-4-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,389] INFO [Broker id=2] Follower -uve-topic-17-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,389] INFO [Broker id=2] Follower -uve-topic-0-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,389] INFO [Broker id=2] Follower -uve-topic-1-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,390] INFO [Broker id=2] Follower -uve-topic-16-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,390] INFO [Broker id=2] Follower -uve-topic-2-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,391] INFO [Broker id=2] Follower -uve-topic-9-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,391] INFO [Broker id=2] Follower -uve-topic-25-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,392] INFO [Broker id=2] Follower -uve-topic-12-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,392] INFO [Broker id=2] Follower -uve-topic-4-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,392] INFO [Broker id=2] Follower -uve-topic-3-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,393] INFO [Broker id=2] Follower -uve-topic-3-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,393] INFO [Broker id=2] Follower -uve-topic-0-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,394] INFO [Broker id=2] Follower -uve-topic-15-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,394] INFO [Broker id=2] Follower -uve-topic-6-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,394] INFO [Broker id=2] Follower -uve-topic-7-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,394] INFO [Broker id=2] Follower -uve-topic-8-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,395] INFO [Broker id=2] Follower -uve-topic-21-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,396] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-16 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,396] INFO [Broker id=2] Follower -uve-topic-25-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,396] INFO [Broker id=2] Follower -uve-topic-12-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,397] INFO [Broker id=2] Follower -uve-topic-19-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,397] INFO [Broker id=2] Follower -uve-topic-24-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,397] INFO [Broker id=2] Follower -uve-topic-11-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,398] INFO [Broker id=2] Follower -uve-topic-4-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,398] INFO [Broker id=2] Follower -uve-topic-24-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,398] INFO [Broker id=2] Follower -uve-topic-11-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,399] INFO [Broker id=2] Follower -uve-topic-5-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,399] INFO [Broker id=2] Follower -uve-topic-6-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,400] INFO [Broker id=2] Follower -uve-topic-27-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,400] INFO [Broker id=2] Follower -uve-topic-14-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,400] INFO [Broker id=2] Follower -uve-topic-18-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,400] INFO [Broker id=2] Follower -uve-topic-19-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,401] INFO [Broker id=2] Follower -uve-topic-10-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,401] INFO [Broker id=2] Follower -uve-topic-22-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,402] INFO [Broker id=2] Follower -uve-topic-23-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,418] INFO [Broker id=2] Follower -uve-topic-18-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,419] INFO [Broker id=2] Follower -uve-topic-24-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,419] INFO [Broker id=2] Follower -uve-topic-11-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,419] INFO [Broker id=2] Follower -uve-topic-26-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,420] INFO [Broker id=2] Follower -uve-topic-13-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,420] INFO [Broker id=2] Follower -uve-topic-25-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,420] INFO [Broker id=2] Follower -uve-topic-20-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,420] INFO [Broker id=2] Follower -uve-topic-12-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,420] INFO [Broker id=2] Follower -uve-topic-22-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,425] INFO [Broker id=2] Follower -uve-topic-16-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,427] INFO [Broker id=2] Follower -uve-topic-29-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,427] INFO [Broker id=2] Follower -uve-topic-21-0 starts at leader epoch 0 from offset 557 with high watermark 557. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,427] INFO [Broker id=2] Follower -uve-topic-8-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,428] INFO [Broker id=2] Follower -uve-topic-17-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,428] INFO [Broker id=2] Follower -uve-topic-15-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,429] INFO [Broker id=2] Follower -uve-topic-28-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,429] INFO [Broker id=2] Follower -uve-topic-7-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,431] INFO [Broker id=2] Follower -uve-topic-10-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,431] INFO [Broker id=2] Follower -uve-topic-23-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,432] INFO [Broker id=2] Follower -uve-topic-1-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,432] INFO [Broker id=2] Follower -uve-topic-3-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,432] INFO [Broker id=2] Follower structured_syslog_topic-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,432] INFO [Broker id=2] Follower -uve-topic-5-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,433] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-6 starts at leader epoch 2 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,433] INFO [Broker id=2] Follower -uve-topic-4-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,434] INFO [Broker id=2] Follower -uve-topic-9-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,434] INFO [Broker id=2] Follower -uve-topic-9-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,435] INFO [Broker id=2] Follower -uve-topic-19-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,436] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-13 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,436] INFO [Broker id=2] Follower -uve-topic-17-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,437] INFO [Broker id=2] Follower -uve-topic-8-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,437] INFO [Broker id=2] Follower -uve-topic-1-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,437] INFO [Broker id=2] Follower -uve-topic-0-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,437] INFO [Broker id=2] Follower -uve-topic-24-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,437] INFO [Broker id=2] Follower -uve-topic-5-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,437] INFO [Broker id=2] Follower -uve-topic-7-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,438] INFO [Broker id=2] Follower -uve-topic-6-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,438] INFO [Broker id=2] Follower -uve-topic-23-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,438] INFO [Broker id=2] Follower -uve-topic-10-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,438] INFO [Broker id=2] Follower -uve-topic-3-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,438] INFO [Broker id=2] Follower -uve-topic-2-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,439] INFO [Broker id=2] Follower -uve-topic-18-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,441] INFO [Broker id=2] Follower -uve-topic-19-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,441] INFO [Broker id=2] Follower -uve-topic-4-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,442] INFO [Broker id=2] Follower -uve-topic-5-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,442] INFO [Broker id=2] Follower -uve-topic-6-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,442] INFO [Broker id=2] Follower -uve-topic-25-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,442] INFO [Broker id=2] Follower -uve-topic-12-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,442] INFO [Broker id=2] Follower -uve-topic-0-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,442] INFO [Broker id=2] Follower -uve-topic-4-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,443] INFO [Broker id=2] Follower -uve-topic-2-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,443] INFO [Broker id=2] Follower -uve-topic-18-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,443] INFO [Broker id=2] Follower -uve-topic-1-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,443] INFO [Broker id=2] Follower -uve-topic-9-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,443] INFO [Broker id=2] Follower -uve-topic-21-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,444] INFO [Broker id=2] Follower -uve-topic-3-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,449] INFO [Broker id=2] Follower -uve-topic-23-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,449] INFO [Broker id=2] Follower -uve-topic-24-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,449] INFO [Broker id=2] Follower -uve-topic-11-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,449] INFO [Broker id=2] Follower -uve-topic-15-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,449] INFO [Broker id=2] Follower -uve-topic-3-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,449] INFO [Broker id=2] Follower -uve-topic-28-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-8-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-20-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-7-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-27-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-14-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-16-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-29-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,450] INFO [Broker id=2] Follower -uve-topic-24-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,453] INFO [Broker id=2] Follower -uve-topic-11-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,458] INFO [Broker id=2] Follower -uve-topic-19-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,458] INFO [Broker id=2] Follower -uve-topic-24-0 starts at leader epoch 3 from offset 791 with high watermark 790. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower -uve-topic-11-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower -uve-topic-3-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower structured_syslog_topic-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower -uve-topic-26-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower -uve-topic-13-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower -uve-topic-22-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower -uve-topic-10-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower structured_syslog_topic-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,459] INFO [Broker id=2] Follower -uve-topic-5-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-25-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-12-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-24-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-11-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-26-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-13-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-17-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower -uve-topic-20-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,460] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-29 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,465] INFO [Broker id=2] Follower -uve-topic-22-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,465] INFO [Broker id=2] Follower -uve-topic-9-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,465] INFO [Broker id=2] Follower -uve-topic-19-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-18-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-24-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-23-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-11-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-10-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-3-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-19-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-23-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,466] INFO [Broker id=2] Follower -uve-topic-10-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,467] INFO [Broker id=2] Follower -uve-topic-15-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,467] INFO [Broker id=2] Follower -uve-topic-28-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-21-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-6-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-19-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-3-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-26-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-1-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-9-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-0-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,468] INFO [Broker id=2] Follower -uve-topic-1-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,469] INFO [Broker id=2] Follower -uve-topic-2-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-25-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-12-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-4-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-8-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-0-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-16-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-29-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-7-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-8-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-2-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-27-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-6-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-7-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-27-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-14-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-2-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-24-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-11-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-18-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-3-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-23-15 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-10-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-4-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-1-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-6-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-0-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,470] INFO [Broker id=2] Follower -uve-topic-9-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-16-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-29-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-2-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-1-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-18-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-3-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-19-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-25-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-12-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-24-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-11-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-15-10 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-29-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-28-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-8-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-20-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-21-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-18-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower structured_syslog_topic-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-5-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-27-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-14-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-7-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,473] INFO [Broker id=2] Follower -uve-topic-20-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-27-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-26-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-13-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-14-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-23-12 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-10-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-19-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-22-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower structured_syslog_topic-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-24-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-11-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-26-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-25-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-12-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-13-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-21-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-7 starts at leader epoch 3 from offset 5 with high watermark 5. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-17-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-9-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-23-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-0-0 starts at leader epoch 3 from offset 3243 with high watermark 3243. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-10-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-18-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-19-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-23-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-10-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-2-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-28-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-15-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-26 starts at leader epoch 3 from offset 6 with high watermark 6. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-2-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-13-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-26-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,474] INFO [Broker id=2] Follower -uve-topic-12-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,475] INFO [Broker id=2] Follower -uve-topic-25-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,475] INFO [Broker id=2] Follower -uve-topic-14-6 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,475] INFO [Broker id=2] Follower -uve-topic-27-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,475] INFO [Broker id=2] Follower -uve-topic-10-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,475] INFO [Broker id=2] Follower -uve-topic-23-9 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,475] INFO [Broker id=2] Follower -uve-topic-12-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,475] INFO [Broker id=2] Follower -uve-topic-25-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,478] INFO [Broker id=2] Follower -uve-topic-11-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,478] INFO [Broker id=2] Follower -uve-topic-24-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,478] INFO [Broker id=2] Follower -uve-topic-4-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,478] INFO [Broker id=2] Follower -uve-topic-8-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,482] INFO [Broker id=2] Follower -uve-topic-0-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,483] INFO [Broker id=2] Follower -uve-topic-18-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,484] INFO [Broker id=2] Follower -uve-topic-2-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,484] INFO [Broker id=2] Follower -uve-topic-1-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,484] INFO [Broker id=2] Follower structured_syslog_topic-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,484] INFO [Broker id=2] Follower -uve-topic-7-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,484] INFO [Broker id=2] Follower -uve-topic-14-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-27-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-6-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-2-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-18-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-5-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-9-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-22-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-13-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-26-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-1-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-17-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-18-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-21-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-20-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-22-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-3-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-19-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-10-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-11-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-23-0 starts at leader epoch 0 from offset 1255 with high watermark 1255. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-24-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-28-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-3-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower -uve-topic-15-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,485] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-23 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,486] INFO [Broker id=2] Follower -uve-topic-19-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,486] INFO [Broker id=2] Follower -uve-topic-17-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,486] INFO [Broker id=2] Follower -uve-topic-20-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-29-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-16-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-21-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-28-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-29-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-15-7 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-16-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-4 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-9-26 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-1-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-23-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-10-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower structured_syslog_topic-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-2-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-22-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-18-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-6-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-5-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-14-3 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-27-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-7-11 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-20-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-0-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-9-23 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-1-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-17-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower structured_syslog_topic-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-5-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-4-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-11-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-24-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-13-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-12-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-26-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-29-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,487] INFO [Broker id=2] Follower -uve-topic-16-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,492] INFO [Broker id=2] Follower -uve-topic-17-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,493] INFO [Broker id=2] Follower -uve-topic-22-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,493] INFO [Broker id=2] Follower -uve-topic-18-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,493] INFO [Broker id=2] Follower -uve-topic-21-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,493] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-1 starts at leader epoch 3 from offset 5 with high watermark 5. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,493] INFO [Broker id=2] Follower -uve-topic-17-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,494] INFO [Broker id=2] Follower -uve-topic-23-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,494] INFO [Broker id=2] Follower -uve-topic-10-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,495] INFO [Broker id=2] Follower -uve-topic-12-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,507] INFO [Broker id=2] Follower -uve-topic-25-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,508] INFO [Broker id=2] Follower -uve-topic-11-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,508] INFO [Broker id=2] Follower -uve-topic-19-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,508] INFO [Broker id=2] Follower -uve-topic-21-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,508] INFO [Broker id=2] Follower -uve-topic-20-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,508] INFO [Broker id=2] Follower -uve-topic-28-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,508] INFO [Broker id=2] Follower -uve-topic-15-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,508] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-20 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,509] INFO [Broker id=2] Follower -uve-topic-22-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,509] INFO [Broker id=2] Follower -uve-topic-18-17 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,509] INFO [Broker id=2] Follower -uve-topic-14-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,509] INFO [Broker id=2] Follower -uve-topic-13-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-26-0 starts at leader epoch 3 from offset 1014 with high watermark 1014. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-27-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-6-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-1-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-0-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-22-5 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-4-27 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-3-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-9-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-28-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-29-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-15-4 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-16-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-8-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,510] INFO [Broker id=2] Follower -uve-topic-2-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,519] INFO [Broker id=2] Follower -uve-topic-3-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,522] INFO [Broker id=2] Follower -uve-topic-9-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,522] INFO [Broker id=2] Follower -uve-topic-2-25 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-1-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower structured_syslog_topic-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-22-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-1-21 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-0-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-9-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-4-24 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-6-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-5-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-9-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-22-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-1-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-17-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-3-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-19-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-4-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-5-25 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-20-0 starts at leader epoch 3 from offset 849 with high watermark 849. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-28-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-3-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-15-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-17 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,523] INFO [Broker id=2] Follower -uve-topic-8-28 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-0-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-17-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-20-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-29-0 starts at leader epoch 3 from offset 726 with high watermark 726. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-16-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-21-1 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-2-22 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-9-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-1-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-23-13 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-10-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-17-13 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower structured_syslog_topic-18 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-2-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-14-19 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-27-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-7-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-6-7 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-13-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-26-16 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-14-0 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-8-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,524] INFO [Broker id=2] Follower -uve-topic-0-20 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,543] INFO [Broker id=2] Follower -uve-topic-21-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,544] INFO [Broker id=2] Follower -uve-topic-12-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-25-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-21-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-0-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-22-2 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-9-29 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-8-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-29-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-11-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-24-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,548] INFO [Broker id=2] Follower -uve-topic-18-14 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,551] INFO [Broker id=2] Follower -uve-topic-29-19 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,551] INFO [Broker id=2] Follower -uve-topic-15-1 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,551] INFO [Broker id=2] Follower -uve-topic-16-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,551] INFO [Broker id=2] Follower -uve-topic-7-8 starts at leader epoch 2 from offset 0 with high watermark 0. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:08:29,580] INFO [Broker id=2] Stopped fetchers as part of become-follower request from controller 1 epoch 2 with correlation id 1 for 960 partitions (state.change.logger)
[2025-02-13 02:08:30,008] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 2 (state.change.logger)
[2025-02-13 02:08:36,131] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 4 (state.change.logger)
[2025-02-13 02:08:53,485] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 1 epoch 2 with correlation id 5 (state.change.logger)
[2025-02-13 02:11:04,261] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 6 from controller 1 for 960 partitions (state.change.logger)
[2025-02-13 02:11:04,329] INFO [Broker id=2] Stopped fetchers as part of LeaderAndIsr request correlationId 6 from controller 1 epoch 2 as part of the become-leader transition for 480 partitions (state.change.logger)
[2025-02-13 02:11:04,335] INFO [Broker id=2] Leader -uve-topic-22-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,348] INFO [Broker id=2] Leader -uve-topic-29-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,353] INFO [Broker id=2] Leader -uve-topic-16-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,356] INFO [Broker id=2] Leader -uve-topic-17-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,360] INFO [Broker id=2] Leader -uve-topic-2-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,363] INFO [Broker id=2] Leader -uve-topic-14-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,366] INFO [Broker id=2] Leader -uve-topic-27-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,369] INFO [Broker id=2] Leader -uve-topic-5-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,373] INFO [Broker id=2] Leader -uve-topic-29-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,376] INFO [Broker id=2] Leader -uve-topic-21-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,381] INFO [Broker id=2] Leader -uve-topic-13-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,385] INFO [Broker id=2] Leader -uve-topic-26-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,389] INFO [Broker id=2] Leader -uve-topic-8-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,392] INFO [Broker id=2] Leader -uve-topic-20-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,397] INFO [Broker id=2] Leader -uve-topic-7-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,401] INFO [Broker id=2] Leader -uve-topic-6-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,409] INFO [Broker id=2] Leader -uve-topic-15-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,414] INFO [Broker id=2] Leader -uve-topic-0-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,419] INFO [Broker id=2] Leader -uve-topic-9-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,423] INFO [Broker id=2] Leader structured_syslog_topic-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,426] INFO [Broker id=2] Leader -uve-topic-17-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,433] INFO [Broker id=2] Leader -uve-topic-3-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,438] INFO [Broker id=2] Leader -uve-topic-23-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,441] INFO [Broker id=2] Leader -uve-topic-19-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,444] INFO [Broker id=2] Leader -uve-topic-25-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,448] INFO [Broker id=2] Leader -uve-topic-12-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,453] INFO [Broker id=2] Leader -uve-topic-16-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,457] INFO [Broker id=2] Leader -uve-topic-18-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,460] INFO [Broker id=2] Leader -uve-topic-23-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,463] INFO [Broker id=2] Leader -uve-topic-14-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,467] INFO [Broker id=2] Leader -uve-topic-27-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,470] INFO [Broker id=2] Leader -uve-topic-7-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,474] INFO [Broker id=2] Leader -uve-topic-6-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,478] INFO [Broker id=2] Leader -uve-topic-8-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,482] INFO [Broker id=2] Leader -uve-topic-17-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,486] INFO [Broker id=2] Leader -uve-topic-16-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,490] INFO [Broker id=2] Leader -uve-topic-4-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,493] INFO [Broker id=2] Leader -uve-topic-13-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,497] INFO [Broker id=2] Leader -uve-topic-12-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,502] INFO [Broker id=2] Leader -uve-topic-26-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,505] INFO [Broker id=2] Leader -uve-topic-25-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,510] INFO [Broker id=2] Leader -uve-topic-5-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,513] INFO [Broker id=2] Leader -uve-topic-29-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,517] INFO [Broker id=2] Leader -uve-topic-19-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,524] INFO [Broker id=2] Leader -uve-topic-24-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,529] INFO [Broker id=2] Leader -uve-topic-15-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,532] INFO [Broker id=2] Leader -uve-topic-20-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,541] INFO [Broker id=2] Leader -uve-topic-29-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,546] INFO [Broker id=2] Leader -uve-topic-16-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,549] INFO [Broker id=2] Leader -uve-topic-7-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,554] INFO [Broker id=2] Leader -uve-topic-18-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,557] INFO [Broker id=2] Leader -uve-topic-24-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,562] INFO [Broker id=2] Leader -uve-topic-11-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,567] INFO [Broker id=2] Leader -uve-topic-17-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,570] INFO [Broker id=2] Leader -uve-topic-22-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,574] INFO [Broker id=2] Leader -uve-topic-1-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,578] INFO [Broker id=2] Leader -uve-topic-20-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,583] INFO [Broker id=2] Leader -uve-topic-7-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,588] INFO [Broker id=2] Leader -uve-topic-24-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,591] INFO [Broker id=2] Leader -uve-topic-23-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,595] INFO [Broker id=2] Leader -uve-topic-19-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,598] INFO [Broker id=2] Leader -uve-topic-20-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,601] INFO [Broker id=2] Leader -uve-topic-7-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,606] INFO [Broker id=2] Leader -uve-topic-17-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,617] INFO [Broker id=2] Leader -uve-topic-16-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,621] INFO [Broker id=2] Leader -uve-topic-29-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,624] INFO [Broker id=2] Leader -uve-topic-0-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,628] INFO [Broker id=2] Leader structured_syslog_topic-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,632] INFO [Broker id=2] Leader -uve-topic-9-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,636] INFO [Broker id=2] Leader -uve-topic-26-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,640] INFO [Broker id=2] Leader -uve-topic-25-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,644] INFO [Broker id=2] Leader -uve-topic-12-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,648] INFO [Broker id=2] Leader -uve-topic-16-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,652] INFO [Broker id=2] Leader -uve-topic-18-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,656] INFO [Broker id=2] Leader -uve-topic-22-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,660] INFO [Broker id=2] Leader -uve-topic-10-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,664] INFO [Broker id=2] Leader -uve-topic-2-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,667] INFO [Broker id=2] Leader -uve-topic-15-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,670] INFO [Broker id=2] Leader -uve-topic-27-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,673] INFO [Broker id=2] Leader -uve-topic-14-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,686] INFO [Broker id=2] Leader -uve-topic-8-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,691] INFO [Broker id=2] Leader -uve-topic-15-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,697] INFO [Broker id=2] Leader -uve-topic-29-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,701] INFO [Broker id=2] Leader -uve-topic-20-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,705] INFO [Broker id=2] Leader -uve-topic-21-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,710] INFO [Broker id=2] Leader structured_syslog_topic-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,714] INFO [Broker id=2] Leader -uve-topic-26-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,717] INFO [Broker id=2] Leader -uve-topic-13-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,722] INFO [Broker id=2] Leader -uve-topic-28-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,729] INFO [Broker id=2] Leader -uve-topic-20-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,734] INFO [Broker id=2] Leader -uve-topic-7-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,738] INFO [Broker id=2] Leader -uve-topic-19-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,744] INFO [Broker id=2] Leader -uve-topic-24-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,748] INFO [Broker id=2] Leader -uve-topic-15-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,752] INFO [Broker id=2] Leader -uve-topic-20-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,758] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-24 starts at leader epoch 3 from offset 7 with high watermark 7 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,762] INFO [Broker id=2] Leader -uve-topic-18-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,768] INFO [Broker id=2] Leader -uve-topic-23-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,772] INFO [Broker id=2] Leader -uve-topic-18-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,776] INFO [Broker id=2] Leader -uve-topic-17-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,780] INFO [Broker id=2] Leader -uve-topic-22-0 starts at leader epoch 4 from offset 2905 with high watermark 2905 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,784] INFO [Broker id=2] Leader -uve-topic-16-0 starts at leader epoch 4 from offset 175 with high watermark 175 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,788] INFO [Broker id=2] Leader -uve-topic-17-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,794] INFO [Broker id=2] Leader -uve-topic-12-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,799] INFO [Broker id=2] Leader -uve-topic-25-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,802] INFO [Broker id=2] Leader -uve-topic-26-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,815] INFO [Broker id=2] Leader -uve-topic-14-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,822] INFO [Broker id=2] Leader -uve-topic-27-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,826] INFO [Broker id=2] Leader -uve-topic-28-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,831] INFO [Broker id=2] Leader -uve-topic-7-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,836] INFO [Broker id=2] Leader -uve-topic-0-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,840] INFO [Broker id=2] Leader -uve-topic-1-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,847] INFO [Broker id=2] Leader -uve-topic-2-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,851] INFO [Broker id=2] Leader -uve-topic-9-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,861] INFO [Broker id=2] Leader -uve-topic-8-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,873] INFO [Broker id=2] Leader -uve-topic-1-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,878] INFO [Broker id=2] Leader structured_syslog_topic-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,883] INFO [Broker id=2] Leader -uve-topic-4-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,888] INFO [Broker id=2] Leader -uve-topic-13-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,892] INFO [Broker id=2] Leader -uve-topic-7-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,899] INFO [Broker id=2] Leader -uve-topic-20-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,903] INFO [Broker id=2] Leader -uve-topic-8-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,908] INFO [Broker id=2] Leader -uve-topic-11-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,911] INFO [Broker id=2] Leader -uve-topic-24-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,918] INFO [Broker id=2] Leader -uve-topic-29-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,923] INFO [Broker id=2] Leader -uve-topic-5-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,927] INFO [Broker id=2] Leader -uve-topic-6-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,934] INFO [Broker id=2] Leader -uve-topic-18-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,938] INFO [Broker id=2] Leader -uve-topic-2-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,942] INFO [Broker id=2] Leader structured_syslog_topic-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,954] INFO [Broker id=2] Leader -uve-topic-2-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,967] INFO [Broker id=2] Leader -uve-topic-15-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,978] INFO [Broker id=2] Leader -uve-topic-8-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,982] INFO [Broker id=2] Leader -uve-topic-1-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,986] INFO [Broker id=2] Leader -uve-topic-0-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:04,992] INFO [Broker id=2] Leader structured_syslog_topic-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:04,996] INFO [Broker id=2] Leader -uve-topic-20-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,000] INFO [Broker id=2] Leader -uve-topic-9-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,007] INFO [Broker id=2] Leader -uve-topic-12-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,013] INFO [Broker id=2] Leader -uve-topic-25-0 starts at leader epoch 4 from offset 1758 with high watermark 1758 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,017] INFO [Broker id=2] Leader -uve-topic-26-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,021] INFO [Broker id=2] Leader -uve-topic-13-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,026] INFO [Broker id=2] Leader -uve-topic-26-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,031] INFO [Broker id=2] Leader -uve-topic-28-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,035] INFO [Broker id=2] Leader -uve-topic-7-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,039] INFO [Broker id=2] Leader -uve-topic-24-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,042] INFO [Broker id=2] Leader -uve-topic-19-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,046] INFO [Broker id=2] Leader structured_syslog_topic-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,049] INFO [Broker id=2] Leader -uve-topic-17-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,053] INFO [Broker id=2] Leader -uve-topic-10-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,060] INFO [Broker id=2] Leader -uve-topic-9-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,064] INFO [Broker id=2] Leader -uve-topic-14-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,068] INFO [Broker id=2] Leader -uve-topic-27-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,071] INFO [Broker id=2] Leader -uve-topic-29-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,075] INFO [Broker id=2] Leader -uve-topic-21-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,087] INFO [Broker id=2] Leader -uve-topic-0-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,255] INFO [Broker id=2] Leader -uve-topic-4-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,261] INFO [Broker id=2] Leader -uve-topic-28-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,314] INFO [Broker id=2] Leader -uve-topic-29-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,321] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 3 from offset 1 with high watermark 1 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,326] INFO [Broker id=2] Leader -uve-topic-13-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,330] INFO [Broker id=2] Leader -uve-topic-18-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,334] INFO [Broker id=2] Leader -uve-topic-0-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,337] INFO [Broker id=2] Leader -uve-topic-1-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,342] INFO [Broker id=2] Leader -uve-topic-2-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,346] INFO [Broker id=2] Leader -uve-topic-6-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,350] INFO [Broker id=2] Leader -uve-topic-13-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,353] INFO [Broker id=2] Leader -uve-topic-7-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,357] INFO [Broker id=2] Leader -uve-topic-8-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,360] INFO [Broker id=2] Leader -uve-topic-20-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,363] INFO [Broker id=2] Leader -uve-topic-11-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,368] INFO [Broker id=2] Leader -uve-topic-24-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,372] INFO [Broker id=2] Leader -uve-topic-4-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,375] INFO [Broker id=2] Leader structured_syslog_topic-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,378] INFO [Broker id=2] Leader -uve-topic-5-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,381] INFO [Broker id=2] Leader -uve-topic-26-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,385] INFO [Broker id=2] Leader -uve-topic-3-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,388] INFO [Broker id=2] Leader -uve-topic-14-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,391] INFO [Broker id=2] Leader -uve-topic-9-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,394] INFO [Broker id=2] Leader -uve-topic-8-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,397] INFO [Broker id=2] Leader -uve-topic-1-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,400] INFO [Broker id=2] Leader -uve-topic-17-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,403] INFO [Broker id=2] Leader structured_syslog_topic-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,406] INFO [Broker id=2] Leader -uve-topic-4-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,409] INFO [Broker id=2] Leader -uve-topic-26-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,413] INFO [Broker id=2] Leader structured_syslog_topic-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,416] INFO [Broker id=2] Leader -uve-topic-28-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,420] INFO [Broker id=2] Leader -uve-topic-0-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,423] INFO [Broker id=2] Leader -uve-topic-28-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,426] INFO [Broker id=2] Leader -uve-topic-24-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,429] INFO [Broker id=2] Leader -uve-topic-6-15 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,433] INFO [Broker id=2] Leader -uve-topic-18-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,436] INFO [Broker id=2] Leader -uve-topic-10-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,439] INFO [Broker id=2] Leader -uve-topic-20-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,442] INFO [Broker id=2] Leader -uve-topic-21-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,449] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,453] INFO [Broker id=2] Leader -uve-topic-29-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,458] INFO [Broker id=2] Leader -uve-topic-21-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,462] INFO [Broker id=2] Leader -uve-topic-4-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,466] INFO [Broker id=2] Leader -uve-topic-27-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,469] INFO [Broker id=2] Leader -uve-topic-2-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,473] INFO [Broker id=2] Leader -uve-topic-2-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,476] INFO [Broker id=2] Leader -uve-topic-26-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,479] INFO [Broker id=2] Leader -uve-topic-9-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,482] INFO [Broker id=2] Leader -uve-topic-17-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,485] INFO [Broker id=2] Leader -uve-topic-1-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,488] INFO [Broker id=2] Leader -uve-topic-8-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,492] INFO [Broker id=2] Leader structured_syslog_topic-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,495] INFO [Broker id=2] Leader -uve-topic-5-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,498] INFO [Broker id=2] Leader -uve-topic-26-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,501] INFO [Broker id=2] Leader -uve-topic-16-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,505] INFO [Broker id=2] Leader -uve-topic-8-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,508] INFO [Broker id=2] Leader -uve-topic-4-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,511] INFO [Broker id=2] Leader -uve-topic-24-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,514] INFO [Broker id=2] Leader -uve-topic-11-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,517] INFO [Broker id=2] Leader -uve-topic-4-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,521] INFO [Broker id=2] Leader structured_syslog_topic-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,524] INFO [Broker id=2] Leader -uve-topic-5-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,527] INFO [Broker id=2] Leader -uve-topic-1-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,530] INFO [Broker id=2] Leader -uve-topic-3-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,536] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-12 starts at leader epoch 3 from offset 4 with high watermark 4 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,539] INFO [Broker id=2] Leader -uve-topic-4-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,542] INFO [Broker id=2] Leader -uve-topic-13-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,545] INFO [Broker id=2] Leader -uve-topic-0-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,549] INFO [Broker id=2] Leader -uve-topic-29-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,552] INFO [Broker id=2] Leader -uve-topic-2-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,555] INFO [Broker id=2] Leader -uve-topic-22-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,558] INFO [Broker id=2] Leader -uve-topic-9-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,561] INFO [Broker id=2] Leader -uve-topic-17-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,565] INFO [Broker id=2] Leader -uve-topic-26-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,569] INFO [Broker id=2] Leader -uve-topic-15-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,572] INFO [Broker id=2] Leader -uve-topic-28-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,576] INFO [Broker id=2] Leader -uve-topic-20-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,580] INFO [Broker id=2] Leader -uve-topic-21-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,583] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 4 from offset 6 with high watermark 6 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,586] INFO [Broker id=2] Leader -uve-topic-25-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,590] INFO [Broker id=2] Leader -uve-topic-26-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,593] INFO [Broker id=2] Leader -uve-topic-14-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,597] INFO [Broker id=2] Leader -uve-topic-10-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,600] INFO [Broker id=2] Leader -uve-topic-18-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,603] INFO [Broker id=2] Leader -uve-topic-17-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,607] INFO [Broker id=2] Leader -uve-topic-20-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,610] INFO [Broker id=2] Leader -uve-topic-21-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,614] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 4 from offset 4 with high watermark 4 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,618] INFO [Broker id=2] Leader -uve-topic-29-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,622] INFO [Broker id=2] Leader -uve-topic-21-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,625] INFO [Broker id=2] Leader structured_syslog_topic-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,628] INFO [Broker id=2] Leader -uve-topic-27-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,632] INFO [Broker id=2] Leader -uve-topic-28-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,635] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-0 starts at leader epoch 3 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,641] INFO [Broker id=2] Leader -uve-topic-24-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,644] INFO [Broker id=2] Leader -uve-topic-6-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,648] INFO [Broker id=2] Leader -uve-topic-9-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,651] INFO [Broker id=2] Leader -uve-topic-1-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,654] INFO [Broker id=2] Leader -uve-topic-8-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,658] INFO [Broker id=2] Leader -uve-topic-28-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,663] INFO [Broker id=2] Leader -uve-topic-0-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,667] INFO [Broker id=2] Leader -uve-topic-4-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,672] INFO [Broker id=2] Leader -uve-topic-6-9 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,675] INFO [Broker id=2] Leader -uve-topic-10-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,678] INFO [Broker id=2] Leader -uve-topic-23-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,681] INFO [Broker id=2] Leader -uve-topic-2-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,685] INFO [Broker id=2] Leader -uve-topic-18-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,689] INFO [Broker id=2] Leader -uve-topic-19-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,692] INFO [Broker id=2] Leader -uve-topic-11-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,697] INFO [Broker id=2] Leader -uve-topic-10-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,701] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-28 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,705] INFO [Broker id=2] Leader -uve-topic-25-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,709] INFO [Broker id=2] Leader -uve-topic-12-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,713] INFO [Broker id=2] Leader -uve-topic-5-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,716] INFO [Broker id=2] Leader -uve-topic-4-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,720] INFO [Broker id=2] Leader -uve-topic-0-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,722] INFO [Broker id=2] Leader -uve-topic-2-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,726] INFO [Broker id=2] Leader -uve-topic-9-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,729] INFO [Broker id=2] Leader -uve-topic-3-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,732] INFO [Broker id=2] Leader -uve-topic-7-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,738] INFO [Broker id=2] Leader -uve-topic-8-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,741] INFO [Broker id=2] Leader -uve-topic-21-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,745] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,748] INFO [Broker id=2] Leader -uve-topic-25-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,752] INFO [Broker id=2] Leader -uve-topic-12-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,755] INFO [Broker id=2] Leader -uve-topic-24-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,759] INFO [Broker id=2] Leader -uve-topic-11-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,763] INFO [Broker id=2] Leader -uve-topic-4-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,766] INFO [Broker id=2] Leader -uve-topic-11-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,771] INFO [Broker id=2] Leader -uve-topic-5-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,776] INFO [Broker id=2] Leader -uve-topic-6-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,780] INFO [Broker id=2] Leader -uve-topic-14-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,784] INFO [Broker id=2] Leader -uve-topic-10-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,788] INFO [Broker id=2] Leader -uve-topic-18-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,792] INFO [Broker id=2] Leader -uve-topic-11-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,796] INFO [Broker id=2] Leader -uve-topic-13-17 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,800] INFO [Broker id=2] Leader -uve-topic-22-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,804] INFO [Broker id=2] Leader -uve-topic-16-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,807] INFO [Broker id=2] Leader -uve-topic-17-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,811] INFO [Broker id=2] Leader -uve-topic-15-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,816] INFO [Broker id=2] Leader -uve-topic-28-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,819] INFO [Broker id=2] Leader -uve-topic-1-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,822] INFO [Broker id=2] Leader -uve-topic-3-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,826] INFO [Broker id=2] Leader -uve-topic-5-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,828] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-6 starts at leader epoch 3 from offset 3 with high watermark 3 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,831] INFO [Broker id=2] Leader -uve-topic-4-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,836] INFO [Broker id=2] Leader -uve-topic-9-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,840] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 4 from offset 4 with high watermark 4 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,844] INFO [Broker id=2] Leader -uve-topic-8-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,847] INFO [Broker id=2] Leader -uve-topic-0-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,851] INFO [Broker id=2] Leader -uve-topic-5-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,855] INFO [Broker id=2] Leader -uve-topic-6-3 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,858] INFO [Broker id=2] Leader -uve-topic-23-18 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,862] INFO [Broker id=2] Leader -uve-topic-10-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,865] INFO [Broker id=2] Leader -uve-topic-3-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,868] INFO [Broker id=2] Leader -uve-topic-2-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,871] INFO [Broker id=2] Leader -uve-topic-18-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,876] INFO [Broker id=2] Leader -uve-topic-19-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,879] INFO [Broker id=2] Leader -uve-topic-6-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,882] INFO [Broker id=2] Leader -uve-topic-25-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,887] INFO [Broker id=2] Leader -uve-topic-12-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,893] INFO [Broker id=2] Leader -uve-topic-4-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,896] INFO [Broker id=2] Leader -uve-topic-1-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,900] INFO [Broker id=2] Leader -uve-topic-21-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,903] INFO [Broker id=2] Leader -uve-topic-3-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,906] INFO [Broker id=2] Leader -uve-topic-23-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,909] INFO [Broker id=2] Leader -uve-topic-11-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,912] INFO [Broker id=2] Leader -uve-topic-3-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,915] INFO [Broker id=2] Leader -uve-topic-28-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,919] INFO [Broker id=2] Leader -uve-topic-27-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,922] INFO [Broker id=2] Leader -uve-topic-11-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,926] INFO [Broker id=2] Leader -uve-topic-24-0 starts at leader epoch 4 from offset 836 with high watermark 836 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,929] INFO [Broker id=2] Leader -uve-topic-10-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,932] INFO [Broker id=2] Leader -uve-topic-5-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,937] INFO [Broker id=2] Leader -uve-topic-25-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,940] INFO [Broker id=2] Leader -uve-topic-12-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,944] INFO [Broker id=2] Leader -uve-topic-11-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,947] INFO [Broker id=2] Leader -uve-topic-13-11 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,950] INFO [Broker id=2] Leader -uve-topic-22-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,953] INFO [Broker id=2] Leader -uve-topic-9-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,957] INFO [Broker id=2] Leader -uve-topic-19-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,961] INFO [Broker id=2] Leader -uve-topic-18-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,965] INFO [Broker id=2] Leader -uve-topic-24-26 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,969] INFO [Broker id=2] Leader -uve-topic-23-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,972] INFO [Broker id=2] Leader -uve-topic-10-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,977] INFO [Broker id=2] Leader -uve-topic-3-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,980] INFO [Broker id=2] Leader -uve-topic-19-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,985] INFO [Broker id=2] Leader -uve-topic-23-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,988] INFO [Broker id=2] Leader -uve-topic-15-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:05,992] INFO [Broker id=2] Leader -uve-topic-28-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:05,997] INFO [Broker id=2] Leader -uve-topic-21-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,001] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,005] INFO [Broker id=2] Leader -uve-topic-3-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,010] INFO [Broker id=2] Leader -uve-topic-1-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,015] INFO [Broker id=2] Leader -uve-topic-0-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,018] INFO [Broker id=2] Leader -uve-topic-2-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,021] INFO [Broker id=2] Leader -uve-topic-16-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,024] INFO [Broker id=2] Leader -uve-topic-7-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,027] INFO [Broker id=2] Leader -uve-topic-8-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,031] INFO [Broker id=2] Leader -uve-topic-27-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,034] INFO [Broker id=2] Leader -uve-topic-6-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,038] INFO [Broker id=2] Leader -uve-topic-14-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,042] INFO [Broker id=2] Leader -uve-topic-11-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,045] INFO [Broker id=2] Leader -uve-topic-3-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,048] INFO [Broker id=2] Leader -uve-topic-10-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,052] INFO [Broker id=2] Leader -uve-topic-6-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,058] INFO [Broker id=2] Leader -uve-topic-9-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,064] INFO [Broker id=2] Leader -uve-topic-1-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,067] INFO [Broker id=2] Leader -uve-topic-3-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,073] INFO [Broker id=2] Leader -uve-topic-25-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,076] INFO [Broker id=2] Leader -uve-topic-12-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,080] INFO [Broker id=2] Leader -uve-topic-11-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,084] INFO [Broker id=2] Leader -uve-topic-28-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,087] INFO [Broker id=2] Leader -uve-topic-5-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,093] INFO [Broker id=2] Leader -uve-topic-27-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,096] INFO [Broker id=2] Leader -uve-topic-27-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,100] INFO [Broker id=2] Leader -uve-topic-14-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,103] INFO [Broker id=2] Leader -uve-topic-23-12 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,107] INFO [Broker id=2] Leader -uve-topic-10-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,111] INFO [Broker id=2] Leader -uve-topic-19-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,115] INFO [Broker id=2] Leader structured_syslog_topic-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,119] INFO [Broker id=2] Leader -uve-topic-26-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,123] INFO [Broker id=2] Leader -uve-topic-25-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,133] INFO [Broker id=2] Leader -uve-topic-12-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,136] INFO [Broker id=2] Leader -uve-topic-13-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,141] INFO [Broker id=2] Leader -uve-topic-21-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,144] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 4 from offset 5 with high watermark 5 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,150] INFO [Broker id=2] Leader -uve-topic-23-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,170] INFO [Broker id=2] Leader -uve-topic-0-0 starts at leader epoch 4 from offset 3638 with high watermark 3638 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,176] INFO [Broker id=2] Leader -uve-topic-19-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,180] INFO [Broker id=2] Leader -uve-topic-10-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,183] INFO [Broker id=2] Leader -uve-topic-15-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,186] INFO [Broker id=2] Leader -uve-topic-2-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,190] INFO [Broker id=2] Leader -uve-topic-13-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,193] INFO [Broker id=2] Leader -uve-topic-14-6 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,196] INFO [Broker id=2] Leader -uve-topic-10-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,200] INFO [Broker id=2] Leader -uve-topic-12-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,204] INFO [Broker id=2] Leader -uve-topic-25-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,208] INFO [Broker id=2] Leader -uve-topic-11-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,212] INFO [Broker id=2] Leader -uve-topic-18-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,215] INFO [Broker id=2] Leader -uve-topic-7-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,221] INFO [Broker id=2] Leader -uve-topic-14-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,227] INFO [Broker id=2] Leader -uve-topic-27-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,231] INFO [Broker id=2] Leader -uve-topic-6-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,235] INFO [Broker id=2] Leader -uve-topic-5-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,238] INFO [Broker id=2] Leader -uve-topic-22-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,242] INFO [Broker id=2] Leader -uve-topic-13-5 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,246] INFO [Broker id=2] Leader -uve-topic-22-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,249] INFO [Broker id=2] Leader -uve-topic-19-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,257] INFO [Broker id=2] Leader -uve-topic-10-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,261] INFO [Broker id=2] Leader -uve-topic-23-0 starts at leader epoch 1 from offset 1312 with high watermark 1312 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 0. (state.change.logger)
[2025-02-13 02:11:06,264] INFO [Broker id=2] Leader -uve-topic-24-20 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,267] INFO [Broker id=2] Leader -uve-topic-19-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,269] INFO [Broker id=2] Leader -uve-topic-3-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,273] INFO [Broker id=2] Leader -uve-topic-15-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,276] INFO [Broker id=2] Leader -uve-topic-20-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,279] INFO [Broker id=2] Leader -uve-topic-16-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,281] INFO [Broker id=2] Leader -uve-topic-21-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,284] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-4 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,287] INFO [Broker id=2] Leader -uve-topic-28-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,290] INFO [Broker id=2] Leader -uve-topic-29-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,297] INFO [Broker id=2] Leader -uve-topic-15-7 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,303] INFO [Broker id=2] Leader -uve-topic-16-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,306] INFO [Broker id=2] Leader -uve-topic-1-27 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,310] INFO [Broker id=2] Leader -uve-topic-23-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,315] INFO [Broker id=2] Leader -uve-topic-22-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,318] INFO [Broker id=2] Leader -uve-topic-27-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,322] INFO [Broker id=2] Leader -uve-topic-5-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,325] INFO [Broker id=2] Leader -uve-topic-0-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,328] INFO [Broker id=2] Leader -uve-topic-9-23 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,331] INFO [Broker id=2] Leader structured_syslog_topic-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,333] INFO [Broker id=2] Leader -uve-topic-13-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,337] INFO [Broker id=2] Leader -uve-topic-12-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,340] INFO [Broker id=2] Leader -uve-topic-26-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,344] INFO [Broker id=2] Leader -uve-topic-17-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,348] INFO [Broker id=2] Leader -uve-topic-21-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,351] INFO [Broker id=2] Leader -uve-topic-22-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,356] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 4 from offset 5 with high watermark 5 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,359] INFO [Broker id=2] Leader -uve-topic-23-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,362] INFO [Broker id=2] Leader -uve-topic-12-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,365] INFO [Broker id=2] Leader -uve-topic-25-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,368] INFO [Broker id=2] Leader -uve-topic-11-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,371] INFO [Broker id=2] Leader -uve-topic-19-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,375] INFO [Broker id=2] Leader -uve-topic-15-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,378] INFO [Broker id=2] Leader -uve-topic-22-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,382] INFO [Broker id=2] Leader -uve-topic-14-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,386] INFO [Broker id=2] Leader -uve-topic-27-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,390] INFO [Broker id=2] Leader -uve-topic-6-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,396] INFO [Broker id=2] Leader -uve-topic-3-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,399] INFO [Broker id=2] Leader -uve-topic-28-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,402] INFO [Broker id=2] Leader -uve-topic-16-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,405] INFO [Broker id=2] Leader -uve-topic-2-25 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,408] INFO [Broker id=2] Leader -uve-topic-22-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,410] INFO [Broker id=2] Leader -uve-topic-1-21 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,413] INFO [Broker id=2] Leader -uve-topic-4-24 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,416] INFO [Broker id=2] Leader -uve-topic-5-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,420] INFO [Broker id=2] Leader -uve-topic-22-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,424] INFO [Broker id=2] Leader -uve-topic-19-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,426] INFO [Broker id=2] Leader -uve-topic-3-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,430] INFO [Broker id=2] Leader -uve-topic-15-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,433] INFO [Broker id=2] Leader -uve-topic-20-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,436] INFO [Broker id=2] Leader -uve-topic-16-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,438] INFO [Broker id=2] Leader -uve-topic-21-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,441] INFO [Broker id=2] Leader -uve-topic-17-13 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,444] INFO [Broker id=2] Leader -uve-topic-23-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,448] INFO [Broker id=2] Leader -uve-topic-14-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,451] INFO [Broker id=2] Leader -uve-topic-27-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,455] INFO [Broker id=2] Leader -uve-topic-6-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,458] INFO [Broker id=2] Leader -uve-topic-7-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,460] INFO [Broker id=2] Leader -uve-topic-13-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,464] INFO [Broker id=2] Leader -uve-topic-14-0 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,467] INFO [Broker id=2] Leader -uve-topic-8-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,470] INFO [Broker id=2] Leader -uve-topic-12-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,473] INFO [Broker id=2] Leader -uve-topic-25-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,476] INFO [Broker id=2] Leader -uve-topic-0-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,479] INFO [Broker id=2] Leader -uve-topic-22-2 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,481] INFO [Broker id=2] Leader -uve-topic-9-29 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,484] INFO [Broker id=2] Leader -uve-topic-29-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,487] INFO [Broker id=2] Leader -uve-topic-24-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,489] INFO [Broker id=2] Leader -uve-topic-18-14 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,497] INFO [Broker id=2] Leader -uve-topic-7-8 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,500] INFO [Broker id=2] Leader -uve-topic-29-19 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,503] INFO [Broker id=2] Leader -uve-topic-15-1 starts at leader epoch 3 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,506] INFO [Broker id=2] Leader -uve-topic-16-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2,3] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-23-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-18-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-16-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-17-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-11-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-24-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-0-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-17-0 starts at leader epoch 4 from offset 175 with high watermark 175. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-9-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-0-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-1-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-2-0 starts at leader epoch 4 from offset 601 with high watermark 601. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-3-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-28-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-6-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-7-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-22-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-21-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-5-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-4-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-8-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-4-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-10-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-20-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-29-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-8-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-14 starts at leader epoch 4 from offset 5 with high watermark 5. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-21-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-9-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-2-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-10-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-21-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-20-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-0-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-29-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-26-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-6-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-16-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-10-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,510] INFO [Broker id=2] Follower -uve-topic-23-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-25-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-11-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-19-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-28-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-8-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-22-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-5-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower structured_syslog_topic-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-15-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-28-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-21-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-3-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-8-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-21-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-11 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-0-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-11-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-10-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-3-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-8 starts at leader epoch 4 from offset 4 with high watermark 4. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-6-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-13-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-5-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-7-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-8-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-19-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-4-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-20-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-27 starts at leader epoch 3 from offset 2 with high watermark 2. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-29-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-8-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-1-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-23-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-18-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-27-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-14-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-28-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-28-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-22-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-16-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-28-0 starts at leader epoch 4 from offset 1912 with high watermark 1912. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-21-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-17-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-25-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-12-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-24-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-11-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-15-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-3-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-23-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-10-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-25-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-12-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-11-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,511] INFO [Broker id=2] Follower -uve-topic-28-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-5 starts at leader epoch 4 from offset 4 with high watermark 4. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-6-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-9-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-19-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-22-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-10-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-14-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-27-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-5-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-28-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-15-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-21-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-13-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-14-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-27-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-7-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-2-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-15-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower structured_syslog_topic-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-0-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-26-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-6-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-16-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-11-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-3-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-4-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-1-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-3-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-14-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-27-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-28-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-22-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-13-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-12-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-25-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-5-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-7-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-6-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-15-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-19-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-10-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-11-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-21 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-14-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-27-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-2 starts at leader epoch 4 from offset 2 with high watermark 2. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-23-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-6-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-16-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-8-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-14-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,512] INFO [Broker id=2] Follower -uve-topic-27-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-16-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-10-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-23-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-12-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-25-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-27-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-26-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-9-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower structured_syslog_topic-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-5-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-14-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-27-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-5-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-6-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-3-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-7-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-13-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-6-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-2-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-22-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-19-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower structured_syslog_topic-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-21-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-28-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-15-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-0-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-13-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-15-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-7-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-20-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-15-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-19-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-12-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-25-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-3-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-4-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-11-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower structured_syslog_topic-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-15 starts at leader epoch 3 from offset 6 with high watermark 6. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-13-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-26-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-14-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-27-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-22-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-23-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-6-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-16-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-14-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-16-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-29-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-1-0 starts at leader epoch 1 from offset 607 with high watermark 607. Previous leader epoch was 0. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-3-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-13-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-5-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-22-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-13-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-5-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-29-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-15-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-28-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-5-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-7-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,513] INFO [Broker id=2] Follower -uve-topic-18-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-19-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower structured_syslog_topic-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-25-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-26-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-12-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-4-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-17-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-16-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-21-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-3 starts at leader epoch 3 from offset 3 with high watermark 3. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-13-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-27-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-14-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-19-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-20-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-10-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-24-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-23-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-25-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-12-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-27-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-13-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-6-12 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-22-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-23-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-5-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-25-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-12-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-18-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-22-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-17-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-16-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-20-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-14-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-16-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-15-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-29-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-25-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-12-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-11-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-26-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-13-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-12-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-13-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-5-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-15-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-7-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-3-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-25-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-12-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-19-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower structured_syslog_topic-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-9 starts at leader epoch 3 from offset 4 with high watermark 4. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-7-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-27-0 starts at leader epoch 4 from offset 1793 with high watermark 1793. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-14-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-22-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-24-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-23-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-4-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-17-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-1-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-16-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-25-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-12-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-4-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-3-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-0-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-15-0 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-6-6 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-19-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-24-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-27-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-18-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-19-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,514] INFO [Broker id=2] Follower -uve-topic-22-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-23-21 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-24-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-26-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-25-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-20-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-12-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-29-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-21-0 starts at leader epoch 1 from offset 596 with high watermark 596. Previous leader epoch was 0. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-8-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-7-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-10-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-23-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower structured_syslog_topic-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-9-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-19-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-17-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-1-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-24-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-7-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-4-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-5-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-0-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-2-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-18-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-9-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-24-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-15-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-8-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-20-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-7-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-14-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-16-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-29-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-24-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-19-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-11-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-3-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower structured_syslog_topic-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-26-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-13-14 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-22-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower structured_syslog_topic-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-24-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-26-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-17-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-20-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-29 starts at leader epoch 4 from offset 2 with high watermark 2. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-11-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-10-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-6-0 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-19-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-26-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-9-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-1-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-25-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-12-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-4-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-8-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-0-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-29-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-2-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-7-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-27-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-2-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-24-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-18-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-23-15 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-4-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-1-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-0-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-16-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-29-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-2-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-18-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-19-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-24-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-15-10 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-29-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-8-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-20-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-21-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,515] INFO [Broker id=2] Follower -uve-topic-18-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower structured_syslog_topic-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-14-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-7-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-20-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-26-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-13-8 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-22-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-24-23 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-11-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-17-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-9-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-10-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-18-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-23-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-2-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-28-27 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-26 starts at leader epoch 4 from offset 6 with high watermark 6. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-26-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-12-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-25-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-27-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-23-9 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-24-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-4-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-8-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-0-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-2-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-1-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower structured_syslog_topic-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-18-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-2-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-9-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-26-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-1-17 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-17-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-18-29 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-21-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-20-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-3-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-11-22 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-23 starts at leader epoch 4 from offset 3 with high watermark 3. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-28-24 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-17-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-29-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-9-26 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-10-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-18-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower structured_syslog_topic-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-2-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-14-3 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-6-29 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-7-11 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-20-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-1-24 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-17-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-4-8 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-5-28 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-11-19 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-24-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-29-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-16-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-18-7 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-17-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-10-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-21-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-20-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-28-21 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-20 starts at leader epoch 4 from offset 2 with high watermark 2. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-18-17 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-13-2 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-26-0 starts at leader epoch 4 from offset 1047 with high watermark 1047. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-1-14 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-0-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-22-5 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-4-27 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-9-13 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-29-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-15-4 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-8-12 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-9-4 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-2-6 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,516] INFO [Broker id=2] Follower -uve-topic-3-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-1-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower structured_syslog_topic-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-0-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-9-1 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-6-26 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-9-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-1-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-17-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-3-23 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,517] INFO [Broker id=2] Follower -uve-topic-4-5 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-5-25 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-20-0 starts at leader epoch 4 from offset 897 with high watermark 897. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-28-18 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-17 starts at leader epoch 4 from offset 4 with high watermark 4. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-29-0 starts at leader epoch 4 from offset 849 with high watermark 849. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-8-28 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-0-10 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-17-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-2-22 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-9-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-1-2 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-10-15 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-2-3 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower structured_syslog_topic-18 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-26-16 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-0-20 starts at leader epoch 3 from offset 0 with high watermark 0. Previous leader epoch was 2. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-21-11 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-21-20 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-8-9 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,518] INFO [Broker id=2] Follower -uve-topic-11-16 starts at leader epoch 4 from offset 0 with high watermark 0. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,527] INFO [Broker id=2] Stopped fetchers as part of become-follower request from controller 1 epoch 2 with correlation id 6 for 480 partitions (state.change.logger)
[2025-02-13 02:11:06,541] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 1 from controller 3 for 960 partitions (state.change.logger)
[2025-02-13 02:11:06,559] INFO [Broker id=2] Stopped fetchers as part of LeaderAndIsr request correlationId 1 from controller 3 epoch 3 as part of the become-leader transition for 960 partitions (state.change.logger)
[2025-02-13 02:11:06,559] INFO [Broker id=2] Leader -uve-topic-22-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,564] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,564] INFO [Broker id=2] Leader -uve-topic-23-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,567] INFO [Broker id=2] Leader -uve-topic-17-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,571] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,571] INFO [Broker id=2] Leader -uve-topic-16-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,574] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,574] INFO [Broker id=2] Leader -uve-topic-29-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,577] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,577] INFO [Broker id=2] Leader -uve-topic-2-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,580] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,580] INFO [Broker id=2] Leader -uve-topic-18-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,583] INFO [Broker id=2] Leader -uve-topic-27-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,586] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,586] INFO [Broker id=2] Leader -uve-topic-14-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,589] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,589] INFO [Broker id=2] Leader -uve-topic-5-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,592] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,592] INFO [Broker id=2] Leader -uve-topic-16-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,595] INFO [Broker id=2] Leader -uve-topic-29-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,598] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,598] INFO [Broker id=2] Leader -uve-topic-17-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,601] INFO [Broker id=2] Leader -uve-topic-21-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,604] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,604] INFO [Broker id=2] Leader -uve-topic-11-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,608] INFO [Broker id=2] Leader -uve-topic-24-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,611] INFO [Broker id=2] Leader -uve-topic-13-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,615] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,615] INFO [Broker id=2] Leader -uve-topic-26-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,618] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,618] INFO [Broker id=2] Leader -uve-topic-8-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,622] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,622] INFO [Broker id=2] Leader -uve-topic-0-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,625] INFO [Broker id=2] Leader -uve-topic-17-0 starts at leader epoch 5 from offset 175 with high watermark 175 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,630] INFO [Broker id=2] Leader -uve-topic-9-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,633] INFO [Broker id=2] Leader -uve-topic-0-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,636] INFO [Broker id=2] Leader -uve-topic-20-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,639] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,639] INFO [Broker id=2] Leader -uve-topic-1-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,642] INFO [Broker id=2] Leader -uve-topic-3-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,646] INFO [Broker id=2] Leader -uve-topic-2-0 starts at leader epoch 5 from offset 601 with high watermark 601 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,650] INFO [Broker id=2] Leader -uve-topic-7-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,654] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,654] INFO [Broker id=2] Leader -uve-topic-6-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,658] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,658] INFO [Broker id=2] Leader -uve-topic-15-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,663] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,663] INFO [Broker id=2] Leader -uve-topic-28-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,666] INFO [Broker id=2] Leader -uve-topic-6-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,669] INFO [Broker id=2] Leader -uve-topic-7-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,672] INFO [Broker id=2] Leader -uve-topic-22-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,676] INFO [Broker id=2] Leader -uve-topic-0-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,679] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,679] INFO [Broker id=2] Leader -uve-topic-9-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,681] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,681] INFO [Broker id=2] Leader -uve-topic-21-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,684] INFO [Broker id=2] Leader structured_syslog_topic-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,687] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,687] INFO [Broker id=2] Leader -uve-topic-5-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,690] INFO [Broker id=2] Leader -uve-topic-4-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,693] INFO [Broker id=2] Leader -uve-topic-17-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,695] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,696] INFO [Broker id=2] Leader -uve-topic-8-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,698] INFO [Broker id=2] Leader -uve-topic-3-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,701] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,701] INFO [Broker id=2] Leader -uve-topic-4-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,704] INFO [Broker id=2] Leader -uve-topic-10-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,706] INFO [Broker id=2] Leader -uve-topic-23-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,709] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,709] INFO [Broker id=2] Leader -uve-topic-25-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,711] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,711] INFO [Broker id=2] Leader -uve-topic-20-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,714] INFO [Broker id=2] Leader -uve-topic-12-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,717] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,717] INFO [Broker id=2] Leader -uve-topic-19-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,719] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,719] INFO [Broker id=2] Leader -uve-topic-29-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,721] INFO [Broker id=2] Leader -uve-topic-16-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,724] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,724] INFO [Broker id=2] Leader -uve-topic-8-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,726] INFO [Broker id=2] Leader -uve-topic-21-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,729] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-14 starts at leader epoch 5 from offset 5 with high watermark 5 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,731] INFO [Broker id=2] Leader -uve-topic-2-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,734] INFO [Broker id=2] Leader -uve-topic-9-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,737] INFO [Broker id=2] Leader -uve-topic-18-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,740] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,740] INFO [Broker id=2] Leader -uve-topic-10-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,742] INFO [Broker id=2] Leader -uve-topic-23-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,745] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,745] INFO [Broker id=2] Leader -uve-topic-14-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,748] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,748] INFO [Broker id=2] Leader -uve-topic-27-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,750] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,750] INFO [Broker id=2] Leader -uve-topic-7-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,753] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,753] INFO [Broker id=2] Leader -uve-topic-6-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,756] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,756] INFO [Broker id=2] Leader -uve-topic-8-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,759] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,759] INFO [Broker id=2] Leader -uve-topic-21-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,763] INFO [Broker id=2] Leader -uve-topic-20-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,766] INFO [Broker id=2] Leader -uve-topic-0-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,768] INFO [Broker id=2] Leader -uve-topic-17-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,771] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,771] INFO [Broker id=2] Leader -uve-topic-29-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,774] INFO [Broker id=2] Leader -uve-topic-16-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,776] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,776] INFO [Broker id=2] Leader -uve-topic-4-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,779] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,779] INFO [Broker id=2] Leader -uve-topic-13-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,782] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,782] INFO [Broker id=2] Leader -uve-topic-26-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,785] INFO [Broker id=2] Leader -uve-topic-6-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,788] INFO [Broker id=2] Leader -uve-topic-5-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,790] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,790] INFO [Broker id=2] Leader -uve-topic-12-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,793] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,793] INFO [Broker id=2] Leader -uve-topic-26-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,795] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,795] INFO [Broker id=2] Leader -uve-topic-25-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,798] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,798] INFO [Broker id=2] Leader -uve-topic-29-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,800] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,800] INFO [Broker id=2] Leader -uve-topic-16-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,803] INFO [Broker id=2] Leader -uve-topic-10-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,806] INFO [Broker id=2] Leader -uve-topic-23-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,809] INFO [Broker id=2] Leader -uve-topic-19-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,812] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,812] INFO [Broker id=2] Leader -uve-topic-25-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,815] INFO [Broker id=2] Leader -uve-topic-11-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,818] INFO [Broker id=2] Leader -uve-topic-24-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,820] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,820] INFO [Broker id=2] Leader -uve-topic-19-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,823] INFO [Broker id=2] Leader -uve-topic-28-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,826] INFO [Broker id=2] Leader -uve-topic-15-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,828] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,828] INFO [Broker id=2] Leader -uve-topic-20-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,831] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,831] INFO [Broker id=2] Leader -uve-topic-29-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,833] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,833] INFO [Broker id=2] Leader -uve-topic-16-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,837] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,837] INFO [Broker id=2] Leader -uve-topic-7-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,839] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,839] INFO [Broker id=2] Leader -uve-topic-8-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,841] INFO [Broker id=2] Leader -uve-topic-22-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,844] INFO [Broker id=2] Leader -uve-topic-18-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,846] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,846] INFO [Broker id=2] Leader -uve-topic-24-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,849] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,849] INFO [Broker id=2] Leader -uve-topic-11-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,851] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,851] INFO [Broker id=2] Leader -uve-topic-17-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,854] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,854] INFO [Broker id=2] Leader -uve-topic-22-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,859] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,859] INFO [Broker id=2] Leader -uve-topic-1-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,861] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,861] INFO [Broker id=2] Leader structured_syslog_topic-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,864] INFO [Broker id=2] Leader -uve-topic-5-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,868] INFO [Broker id=2] Leader -uve-topic-15-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,870] INFO [Broker id=2] Leader -uve-topic-28-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,873] INFO [Broker id=2] Leader -uve-topic-20-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,877] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,877] INFO [Broker id=2] Leader -uve-topic-21-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,880] INFO [Broker id=2] Leader -uve-topic-7-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,884] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,884] INFO [Broker id=2] Leader -uve-topic-3-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,886] INFO [Broker id=2] Leader -uve-topic-8-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,890] INFO [Broker id=2] Leader -uve-topic-21-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,894] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-11 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,897] INFO [Broker id=2] Leader -uve-topic-0-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,900] INFO [Broker id=2] Leader -uve-topic-24-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,903] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,903] INFO [Broker id=2] Leader -uve-topic-23-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,906] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,906] INFO [Broker id=2] Leader -uve-topic-11-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,909] INFO [Broker id=2] Leader -uve-topic-10-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,912] INFO [Broker id=2] Leader -uve-topic-19-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,916] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,916] INFO [Broker id=2] Leader -uve-topic-20-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,919] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,919] INFO [Broker id=2] Leader -uve-topic-3-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,921] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-8 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,924] INFO [Broker id=2] Leader -uve-topic-7-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,927] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,927] INFO [Broker id=2] Leader -uve-topic-17-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,931] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,931] INFO [Broker id=2] Leader -uve-topic-16-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,934] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,934] INFO [Broker id=2] Leader -uve-topic-29-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,938] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,938] INFO [Broker id=2] Leader -uve-topic-0-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,941] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,941] INFO [Broker id=2] Leader structured_syslog_topic-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,944] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,945] INFO [Broker id=2] Leader -uve-topic-9-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,949] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,949] INFO [Broker id=2] Leader -uve-topic-6-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,952] INFO [Broker id=2] Leader -uve-topic-26-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,956] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,956] INFO [Broker id=2] Leader -uve-topic-13-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,959] INFO [Broker id=2] Leader -uve-topic-5-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,963] INFO [Broker id=2] Leader -uve-topic-7-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,966] INFO [Broker id=2] Leader -uve-topic-8-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,969] INFO [Broker id=2] Leader -uve-topic-19-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,972] INFO [Broker id=2] Leader -uve-topic-4-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,975] INFO [Broker id=2] Leader -uve-topic-25-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,978] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,978] INFO [Broker id=2] Leader -uve-topic-20-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,981] INFO [Broker id=2] Leader -uve-topic-12-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,984] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,984] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-27 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,987] INFO [Broker id=2] Leader -uve-topic-16-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,990] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,990] INFO [Broker id=2] Leader -uve-topic-29-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:06,993] INFO [Broker id=2] Leader -uve-topic-8-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,995] INFO [Broker id=2] Leader -uve-topic-18-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:06,998] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:06,998] INFO [Broker id=2] Leader -uve-topic-1-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,000] INFO [Broker id=2] Leader -uve-topic-22-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,003] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,003] INFO [Broker id=2] Leader -uve-topic-23-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,006] INFO [Broker id=2] Leader -uve-topic-10-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,009] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,009] INFO [Broker id=2] Leader -uve-topic-2-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,012] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,012] INFO [Broker id=2] Leader -uve-topic-18-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,015] INFO [Broker id=2] Leader -uve-topic-27-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,018] INFO [Broker id=2] Leader -uve-topic-14-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,020] INFO [Broker id=2] Leader -uve-topic-15-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,023] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,023] INFO [Broker id=2] Leader -uve-topic-28-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,026] INFO [Broker id=2] Leader -uve-topic-28-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,028] INFO [Broker id=2] Leader -uve-topic-27-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,031] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,031] INFO [Broker id=2] Leader -uve-topic-14-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,034] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,034] INFO [Broker id=2] Leader -uve-topic-8-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,037] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,037] INFO [Broker id=2] Leader -uve-topic-22-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,040] INFO [Broker id=2] Leader -uve-topic-16-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,042] INFO [Broker id=2] Leader -uve-topic-15-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,045] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,045] INFO [Broker id=2] Leader -uve-topic-29-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,048] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,048] INFO [Broker id=2] Leader -uve-topic-28-0 starts at leader epoch 5 from offset 1912 with high watermark 1912 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,051] INFO [Broker id=2] Leader -uve-topic-21-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,054] INFO [Broker id=2] Leader -uve-topic-17-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,057] INFO [Broker id=2] Leader -uve-topic-20-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,059] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,059] INFO [Broker id=2] Leader -uve-topic-21-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,063] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,063] INFO [Broker id=2] Leader structured_syslog_topic-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,068] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,068] INFO [Broker id=2] Leader -uve-topic-25-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,074] INFO [Broker id=2] Leader -uve-topic-12-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,077] INFO [Broker id=2] Leader -uve-topic-24-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,080] INFO [Broker id=2] Leader -uve-topic-11-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,083] INFO [Broker id=2] Leader -uve-topic-26-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,085] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,085] INFO [Broker id=2] Leader -uve-topic-13-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,089] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,089] INFO [Broker id=2] Leader -uve-topic-15-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,093] INFO [Broker id=2] Leader -uve-topic-28-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,096] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,096] INFO [Broker id=2] Leader -uve-topic-20-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,099] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,099] INFO [Broker id=2] Leader -uve-topic-7-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,102] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,102] INFO [Broker id=2] Leader -uve-topic-3-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,104] INFO [Broker id=2] Leader -uve-topic-19-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,107] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,107] INFO [Broker id=2] Leader -uve-topic-23-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,110] INFO [Broker id=2] Leader -uve-topic-10-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,113] INFO [Broker id=2] Leader -uve-topic-25-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,116] INFO [Broker id=2] Leader -uve-topic-12-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,119] INFO [Broker id=2] Leader -uve-topic-24-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,122] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,122] INFO [Broker id=2] Leader -uve-topic-11-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,125] INFO [Broker id=2] Leader -uve-topic-15-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,128] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,128] INFO [Broker id=2] Leader -uve-topic-28-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,132] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-5 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,136] INFO [Broker id=2] Leader -uve-topic-20-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,140] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,141] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-24 starts at leader epoch 4 from offset 7 with high watermark 7 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,145] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,145] INFO [Broker id=2] Leader -uve-topic-6-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,148] INFO [Broker id=2] Leader -uve-topic-9-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,150] INFO [Broker id=2] Leader -uve-topic-19-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,153] INFO [Broker id=2] Leader -uve-topic-18-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,158] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,158] INFO [Broker id=2] Leader -uve-topic-22-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,161] INFO [Broker id=2] Leader -uve-topic-10-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,164] INFO [Broker id=2] Leader -uve-topic-23-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,169] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,169] INFO [Broker id=2] Leader -uve-topic-18-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,172] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,172] INFO [Broker id=2] Leader -uve-topic-17-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,175] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,175] INFO [Broker id=2] Leader -uve-topic-22-0 starts at leader epoch 5 from offset 2905 with high watermark 2905 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,178] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,181] INFO [Broker id=2] Leader -uve-topic-14-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,185] INFO [Broker id=2] Leader -uve-topic-27-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,188] INFO [Broker id=2] Leader -uve-topic-5-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,191] INFO [Broker id=2] Leader -uve-topic-21-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,194] INFO [Broker id=2] Leader -uve-topic-28-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,197] INFO [Broker id=2] Leader -uve-topic-15-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,200] INFO [Broker id=2] Leader -uve-topic-16-0 starts at leader epoch 5 from offset 175 with high watermark 175 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,203] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,203] INFO [Broker id=2] Leader -uve-topic-17-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,206] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,206] INFO [Broker id=2] Leader -uve-topic-13-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,209] INFO [Broker id=2] Leader -uve-topic-12-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,212] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,212] INFO [Broker id=2] Leader -uve-topic-25-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,215] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,215] INFO [Broker id=2] Leader -uve-topic-26-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,217] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,217] INFO [Broker id=2] Leader -uve-topic-14-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,220] INFO [Broker id=2] Leader -uve-topic-27-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,224] INFO [Broker id=2] Leader -uve-topic-7-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,226] INFO [Broker id=2] Leader -uve-topic-2-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,229] INFO [Broker id=2] Leader -uve-topic-14-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,232] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,232] INFO [Broker id=2] Leader -uve-topic-27-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,234] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,234] INFO [Broker id=2] Leader -uve-topic-28-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,237] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,237] INFO [Broker id=2] Leader -uve-topic-15-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,241] INFO [Broker id=2] Leader -uve-topic-7-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,244] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,244] INFO [Broker id=2] Leader -uve-topic-0-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,247] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,247] INFO [Broker id=2] Leader -uve-topic-1-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,250] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,250] INFO [Broker id=2] Leader -uve-topic-2-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,253] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,253] INFO [Broker id=2] Leader -uve-topic-9-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,256] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,256] INFO [Broker id=2] Leader -uve-topic-8-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,259] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,259] INFO [Broker id=2] Leader structured_syslog_topic-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,261] INFO [Broker id=2] Leader -uve-topic-1-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,264] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,264] INFO [Broker id=2] Leader -uve-topic-0-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,268] INFO [Broker id=2] Leader structured_syslog_topic-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,271] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,271] INFO [Broker id=2] Leader -uve-topic-4-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,274] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,274] INFO [Broker id=2] Leader -uve-topic-13-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,277] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,277] INFO [Broker id=2] Leader -uve-topic-26-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,279] INFO [Broker id=2] Leader -uve-topic-6-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,282] INFO [Broker id=2] Leader -uve-topic-8-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,285] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,285] INFO [Broker id=2] Leader -uve-topic-7-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,288] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,288] INFO [Broker id=2] Leader -uve-topic-20-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,291] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,291] INFO [Broker id=2] Leader -uve-topic-11-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,294] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,294] INFO [Broker id=2] Leader -uve-topic-24-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,297] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,297] INFO [Broker id=2] Leader -uve-topic-29-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,299] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,299] INFO [Broker id=2] Leader -uve-topic-16-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,303] INFO [Broker id=2] Leader -uve-topic-3-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,306] INFO [Broker id=2] Leader -uve-topic-11-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,308] INFO [Broker id=2] Leader -uve-topic-4-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,312] INFO [Broker id=2] Leader -uve-topic-5-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,316] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,316] INFO [Broker id=2] Leader -uve-topic-6-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,319] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,319] INFO [Broker id=2] Leader -uve-topic-2-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,322] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,322] INFO [Broker id=2] Leader -uve-topic-1-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,325] INFO [Broker id=2] Leader -uve-topic-18-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,328] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,328] INFO [Broker id=2] Leader structured_syslog_topic-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,331] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,331] INFO [Broker id=2] Leader -uve-topic-3-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,333] INFO [Broker id=2] Leader -uve-topic-2-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,336] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,336] INFO [Broker id=2] Leader -uve-topic-14-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,339] INFO [Broker id=2] Leader -uve-topic-27-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,342] INFO [Broker id=2] Leader -uve-topic-28-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,345] INFO [Broker id=2] Leader -uve-topic-15-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,348] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,349] INFO [Broker id=2] Leader -uve-topic-8-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,352] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,352] INFO [Broker id=2] Leader -uve-topic-1-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,355] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,355] INFO [Broker id=2] Leader -uve-topic-0-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,358] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,358] INFO [Broker id=2] Leader -uve-topic-20-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,361] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,361] INFO [Broker id=2] Leader structured_syslog_topic-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,364] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,364] INFO [Broker id=2] Leader -uve-topic-9-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,367] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,367] INFO [Broker id=2] Leader -uve-topic-22-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,370] INFO [Broker id=2] Leader -uve-topic-13-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,374] INFO [Broker id=2] Leader -uve-topic-12-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,378] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,378] INFO [Broker id=2] Leader -uve-topic-25-0 starts at leader epoch 5 from offset 1758 with high watermark 1758 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,382] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,382] INFO [Broker id=2] Leader -uve-topic-26-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,386] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,386] INFO [Broker id=2] Leader -uve-topic-5-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,389] INFO [Broker id=2] Leader -uve-topic-12-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,393] INFO [Broker id=2] Leader -uve-topic-25-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,396] INFO [Broker id=2] Leader -uve-topic-13-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,399] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,400] INFO [Broker id=2] Leader -uve-topic-26-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,404] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,404] INFO [Broker id=2] Leader -uve-topic-7-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,407] INFO [Broker id=2] Leader -uve-topic-6-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,410] INFO [Broker id=2] Leader -uve-topic-28-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,413] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,413] INFO [Broker id=2] Leader -uve-topic-15-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,416] INFO [Broker id=2] Leader -uve-topic-7-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,420] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,420] INFO [Broker id=2] Leader -uve-topic-19-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,425] INFO [Broker id=2] Leader -uve-topic-10-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,428] INFO [Broker id=2] Leader -uve-topic-11-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,431] INFO [Broker id=2] Leader -uve-topic-24-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,434] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,434] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-21 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,438] INFO [Broker id=2] Leader -uve-topic-19-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,441] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,441] INFO [Broker id=2] Leader structured_syslog_topic-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,444] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,444] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-2 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,447] INFO [Broker id=2] Leader -uve-topic-14-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,450] INFO [Broker id=2] Leader -uve-topic-27-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,453] INFO [Broker id=2] Leader -uve-topic-10-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,456] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,456] INFO [Broker id=2] Leader -uve-topic-23-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,460] INFO [Broker id=2] Leader -uve-topic-17-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,464] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,464] INFO [Broker id=2] Leader -uve-topic-9-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,470] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,470] INFO [Broker id=2] Leader -uve-topic-14-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,474] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,474] INFO [Broker id=2] Leader -uve-topic-27-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,478] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,478] INFO [Broker id=2] Leader -uve-topic-6-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,482] INFO [Broker id=2] Leader -uve-topic-29-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,485] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,485] INFO [Broker id=2] Leader -uve-topic-16-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,489] INFO [Broker id=2] Leader -uve-topic-21-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,492] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,492] INFO [Broker id=2] Leader -uve-topic-0-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,495] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,495] INFO [Broker id=2] Leader -uve-topic-4-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,498] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,498] INFO [Broker id=2] Leader -uve-topic-8-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,502] INFO [Broker id=2] Leader -uve-topic-28-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,505] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,505] INFO [Broker id=2] Leader -uve-topic-14-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,508] INFO [Broker id=2] Leader -uve-topic-27-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,511] INFO [Broker id=2] Leader -uve-topic-29-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,514] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,514] INFO [Broker id=2] Leader -uve-topic-16-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,517] INFO [Broker id=2] Leader -uve-topic-10-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,520] INFO [Broker id=2] Leader -uve-topic-23-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,523] INFO [Broker id=2] Leader -uve-topic-12-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,526] INFO [Broker id=2] Leader -uve-topic-25-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,529] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 4 from offset 1 with high watermark 1 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,532] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,532] INFO [Broker id=2] Leader -uve-topic-27-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,535] INFO [Broker id=2] Leader -uve-topic-13-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,539] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,539] INFO [Broker id=2] Leader -uve-topic-26-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,542] INFO [Broker id=2] Leader -uve-topic-18-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,545] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,545] INFO [Broker id=2] Leader -uve-topic-9-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,547] INFO [Broker id=2] Leader -uve-topic-0-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,550] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,550] INFO [Broker id=2] Leader -uve-topic-1-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,553] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,553] INFO [Broker id=2] Leader -uve-topic-2-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,556] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,556] INFO [Broker id=2] Leader structured_syslog_topic-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,559] INFO [Broker id=2] Leader -uve-topic-6-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,561] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,561] INFO [Broker id=2] Leader -uve-topic-5-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,564] INFO [Broker id=2] Leader -uve-topic-14-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,567] INFO [Broker id=2] Leader -uve-topic-27-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,570] INFO [Broker id=2] Leader -uve-topic-5-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,573] INFO [Broker id=2] Leader -uve-topic-13-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,576] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,576] INFO [Broker id=2] Leader -uve-topic-6-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,579] INFO [Broker id=2] Leader -uve-topic-7-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,582] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,582] INFO [Broker id=2] Leader -uve-topic-8-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,585] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,585] INFO [Broker id=2] Leader -uve-topic-20-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,588] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,588] INFO [Broker id=2] Leader -uve-topic-11-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,590] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,591] INFO [Broker id=2] Leader -uve-topic-24-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,593] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,594] INFO [Broker id=2] Leader -uve-topic-4-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,596] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,596] INFO [Broker id=2] Leader -uve-topic-3-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,599] INFO [Broker id=2] Leader structured_syslog_topic-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,602] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,602] INFO [Broker id=2] Leader -uve-topic-5-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,605] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,605] INFO [Broker id=2] Leader -uve-topic-7-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,608] INFO [Broker id=2] Leader -uve-topic-13-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,612] INFO [Broker id=2] Leader -uve-topic-26-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,615] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,615] INFO [Broker id=2] Leader -uve-topic-6-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,618] INFO [Broker id=2] Leader -uve-topic-3-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,621] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,621] INFO [Broker id=2] Leader -uve-topic-2-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,624] INFO [Broker id=2] Leader -uve-topic-22-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,627] INFO [Broker id=2] Leader -uve-topic-19-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,630] INFO [Broker id=2] Leader structured_syslog_topic-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,632] INFO [Broker id=2] Leader -uve-topic-14-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,635] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,635] INFO [Broker id=2] Leader -uve-topic-9-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,639] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,639] INFO [Broker id=2] Leader -uve-topic-8-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,641] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,641] INFO [Broker id=2] Leader -uve-topic-21-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,644] INFO [Broker id=2] Leader -uve-topic-28-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,647] INFO [Broker id=2] Leader -uve-topic-15-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,651] INFO [Broker id=2] Leader -uve-topic-1-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,655] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,656] INFO [Broker id=2] Leader -uve-topic-0-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,659] INFO [Broker id=2] Leader -uve-topic-17-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,662] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,662] INFO [Broker id=2] Leader structured_syslog_topic-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,666] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,666] INFO [Broker id=2] Leader -uve-topic-13-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,669] INFO [Broker id=2] Leader -uve-topic-26-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,672] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,672] INFO [Broker id=2] Leader -uve-topic-4-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,675] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,675] INFO [Broker id=2] Leader structured_syslog_topic-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,678] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,678] INFO [Broker id=2] Leader -uve-topic-28-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,680] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,681] INFO [Broker id=2] Leader -uve-topic-15-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,683] INFO [Broker id=2] Leader -uve-topic-0-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,686] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,686] INFO [Broker id=2] Leader -uve-topic-7-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,689] INFO [Broker id=2] Leader -uve-topic-20-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,696] INFO [Broker id=2] Leader -uve-topic-28-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,698] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,698] INFO [Broker id=2] Leader -uve-topic-15-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,701] INFO [Broker id=2] Leader -uve-topic-12-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,704] INFO [Broker id=2] Leader -uve-topic-25-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,707] INFO [Broker id=2] Leader -uve-topic-3-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,710] INFO [Broker id=2] Leader -uve-topic-19-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,713] INFO [Broker id=2] Leader -uve-topic-4-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,716] INFO [Broker id=2] Leader -uve-topic-11-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,719] INFO [Broker id=2] Leader -uve-topic-24-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,721] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,721] INFO [Broker id=2] Leader structured_syslog_topic-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,724] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-15 starts at leader epoch 4 from offset 6 with high watermark 6 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,726] INFO [Broker id=2] Leader -uve-topic-6-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,729] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,729] INFO [Broker id=2] Leader -uve-topic-13-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,732] INFO [Broker id=2] Leader -uve-topic-26-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,735] INFO [Broker id=2] Leader -uve-topic-14-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,738] INFO [Broker id=2] Leader -uve-topic-27-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,740] INFO [Broker id=2] Leader -uve-topic-18-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,744] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,744] INFO [Broker id=2] Leader -uve-topic-22-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,748] INFO [Broker id=2] Leader -uve-topic-10-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,751] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,751] INFO [Broker id=2] Leader -uve-topic-23-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,754] INFO [Broker id=2] Leader -uve-topic-6-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,758] INFO [Broker id=2] Leader -uve-topic-20-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,761] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,761] INFO [Broker id=2] Leader -uve-topic-21-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,764] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,764] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,767] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,767] INFO [Broker id=2] Leader -uve-topic-16-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,770] INFO [Broker id=2] Leader -uve-topic-29-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,772] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,772] INFO [Broker id=2] Leader -uve-topic-21-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,776] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,776] INFO [Broker id=2] Leader -uve-topic-4-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,779] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,779] INFO [Broker id=2] Leader -uve-topic-27-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,782] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,782] INFO [Broker id=2] Leader -uve-topic-14-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,784] INFO [Broker id=2] Leader -uve-topic-16-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,787] INFO [Broker id=2] Leader -uve-topic-29-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,790] INFO [Broker id=2] Leader -uve-topic-2-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,792] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,792] INFO [Broker id=2] Leader -uve-topic-2-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,795] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,795] INFO [Broker id=2] Leader -uve-topic-1-0 starts at leader epoch 2 from offset 607 with high watermark 607 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 1. (state.change.logger)
[2025-02-13 02:11:07,797] INFO [Broker id=2] Leader -uve-topic-3-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,800] INFO [Broker id=2] Leader -uve-topic-26-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,803] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,803] INFO [Broker id=2] Leader -uve-topic-13-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,806] INFO [Broker id=2] Leader -uve-topic-5-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,808] INFO [Broker id=2] Leader -uve-topic-9-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,813] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,813] INFO [Broker id=2] Leader -uve-topic-17-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,815] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,815] INFO [Broker id=2] Leader -uve-topic-1-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,817] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,817] INFO [Broker id=2] Leader -uve-topic-8-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,820] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,820] INFO [Broker id=2] Leader structured_syslog_topic-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,825] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,825] INFO [Broker id=2] Leader -uve-topic-5-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,828] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,828] INFO [Broker id=2] Leader -uve-topic-22-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,831] INFO [Broker id=2] Leader -uve-topic-26-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,834] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,834] INFO [Broker id=2] Leader -uve-topic-13-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,837] INFO [Broker id=2] Leader -uve-topic-5-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,841] INFO [Broker id=2] Leader -uve-topic-16-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,845] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,845] INFO [Broker id=2] Leader -uve-topic-29-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,849] INFO [Broker id=2] Leader -uve-topic-15-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,852] INFO [Broker id=2] Leader -uve-topic-28-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,855] INFO [Broker id=2] Leader -uve-topic-8-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,858] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,858] INFO [Broker id=2] Leader -uve-topic-5-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,861] INFO [Broker id=2] Leader -uve-topic-4-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,863] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,864] INFO [Broker id=2] Leader -uve-topic-24-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,866] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,866] INFO [Broker id=2] Leader -uve-topic-11-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,869] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,869] INFO [Broker id=2] Leader -uve-topic-4-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,872] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,872] INFO [Broker id=2] Leader structured_syslog_topic-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,876] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,876] INFO [Broker id=2] Leader -uve-topic-5-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,881] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,881] INFO [Broker id=2] Leader -uve-topic-7-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,887] INFO [Broker id=2] Leader -uve-topic-18-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,891] INFO [Broker id=2] Leader -uve-topic-1-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,898] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,899] INFO [Broker id=2] Leader -uve-topic-3-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,902] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,902] INFO [Broker id=2] Leader -uve-topic-19-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,905] INFO [Broker id=2] Leader structured_syslog_topic-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,909] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-12 starts at leader epoch 4 from offset 4 with high watermark 4 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,915] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,915] INFO [Broker id=2] Leader -uve-topic-4-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,917] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,918] INFO [Broker id=2] Leader -uve-topic-25-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,921] INFO [Broker id=2] Leader -uve-topic-26-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,923] INFO [Broker id=2] Leader -uve-topic-12-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,926] INFO [Broker id=2] Leader -uve-topic-13-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,929] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,929] INFO [Broker id=2] Leader -uve-topic-4-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,932] INFO [Broker id=2] Leader -uve-topic-0-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,935] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,935] INFO [Broker id=2] Leader -uve-topic-17-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,938] INFO [Broker id=2] Leader -uve-topic-16-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,941] INFO [Broker id=2] Leader -uve-topic-29-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,945] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,945] INFO [Broker id=2] Leader -uve-topic-2-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,948] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,948] INFO [Broker id=2] Leader -uve-topic-22-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,951] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,951] INFO [Broker id=2] Leader -uve-topic-9-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,954] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,954] INFO [Broker id=2] Leader -uve-topic-21-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,957] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-3 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,960] INFO [Broker id=2] Leader -uve-topic-17-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,963] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,963] INFO [Broker id=2] Leader -uve-topic-26-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,967] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,967] INFO [Broker id=2] Leader -uve-topic-13-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,970] INFO [Broker id=2] Leader -uve-topic-15-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,973] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,973] INFO [Broker id=2] Leader -uve-topic-28-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,976] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,976] INFO [Broker id=2] Leader -uve-topic-20-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,979] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,979] INFO [Broker id=2] Leader -uve-topic-21-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,982] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,982] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 5 from offset 6 with high watermark 6 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,986] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,986] INFO [Broker id=2] Leader -uve-topic-27-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,989] INFO [Broker id=2] Leader -uve-topic-14-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:07,992] INFO [Broker id=2] Leader -uve-topic-25-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,995] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:07,995] INFO [Broker id=2] Leader -uve-topic-19-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:07,999] INFO [Broker id=2] Leader -uve-topic-20-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,002] INFO [Broker id=2] Leader -uve-topic-10-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,006] INFO [Broker id=2] Leader -uve-topic-24-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,009] INFO [Broker id=2] Leader -uve-topic-23-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,012] INFO [Broker id=2] Leader -uve-topic-25-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,015] INFO [Broker id=2] Leader -uve-topic-12-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,018] INFO [Broker id=2] Leader -uve-topic-27-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,021] INFO [Broker id=2] Leader -uve-topic-26-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,024] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,024] INFO [Broker id=2] Leader -uve-topic-13-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,027] INFO [Broker id=2] Leader -uve-topic-14-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,030] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,030] INFO [Broker id=2] Leader -uve-topic-6-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,033] INFO [Broker id=2] Leader -uve-topic-10-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,036] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,036] INFO [Broker id=2] Leader -uve-topic-22-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,039] INFO [Broker id=2] Leader -uve-topic-23-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,047] INFO [Broker id=2] Leader -uve-topic-18-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,050] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,050] INFO [Broker id=2] Leader -uve-topic-5-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,054] INFO [Broker id=2] Leader -uve-topic-25-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,057] INFO [Broker id=2] Leader -uve-topic-12-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,060] INFO [Broker id=2] Leader -uve-topic-18-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,063] INFO [Broker id=2] Leader -uve-topic-17-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,066] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,066] INFO [Broker id=2] Leader -uve-topic-20-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,068] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,068] INFO [Broker id=2] Leader -uve-topic-21-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,071] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,071] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,074] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,074] INFO [Broker id=2] Leader -uve-topic-22-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,078] INFO [Broker id=2] Leader -uve-topic-17-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,081] INFO [Broker id=2] Leader -uve-topic-16-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,083] INFO [Broker id=2] Leader -uve-topic-29-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,087] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,087] INFO [Broker id=2] Leader -uve-topic-21-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,090] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,090] INFO [Broker id=2] Leader structured_syslog_topic-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,093] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,093] INFO [Broker id=2] Leader -uve-topic-20-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,096] INFO [Broker id=2] Leader -uve-topic-27-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,099] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,099] INFO [Broker id=2] Leader -uve-topic-14-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,102] INFO [Broker id=2] Leader -uve-topic-16-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,105] INFO [Broker id=2] Leader -uve-topic-15-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,108] INFO [Broker id=2] Leader -uve-topic-29-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,110] INFO [Broker id=2] Leader -uve-topic-28-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,113] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,113] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-0 starts at leader epoch 4 from offset 2 with high watermark 2 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,116] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,116] INFO [Broker id=2] Leader -uve-topic-25-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,119] INFO [Broker id=2] Leader -uve-topic-12-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,123] INFO [Broker id=2] Leader -uve-topic-24-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,126] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,126] INFO [Broker id=2] Leader -uve-topic-11-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,129] INFO [Broker id=2] Leader -uve-topic-26-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,132] INFO [Broker id=2] Leader -uve-topic-13-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,136] INFO [Broker id=2] Leader -uve-topic-12-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,140] INFO [Broker id=2] Leader -uve-topic-13-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,144] INFO [Broker id=2] Leader -uve-topic-5-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,147] INFO [Broker id=2] Leader -uve-topic-6-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,150] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,150] INFO [Broker id=2] Leader -uve-topic-9-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,154] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,154] INFO [Broker id=2] Leader -uve-topic-1-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,157] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,157] INFO [Broker id=2] Leader -uve-topic-8-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,160] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,160] INFO [Broker id=2] Leader -uve-topic-15-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,163] INFO [Broker id=2] Leader -uve-topic-28-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,166] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,166] INFO [Broker id=2] Leader -uve-topic-0-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,169] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,169] INFO [Broker id=2] Leader -uve-topic-7-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,172] INFO [Broker id=2] Leader -uve-topic-4-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,175] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,175] INFO [Broker id=2] Leader -uve-topic-3-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,178] INFO [Broker id=2] Leader -uve-topic-25-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,184] INFO [Broker id=2] Leader -uve-topic-12-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,187] INFO [Broker id=2] Leader -uve-topic-19-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,190] INFO [Broker id=2] Leader structured_syslog_topic-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,192] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 4 from offset 4 with high watermark 4 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,195] INFO [Broker id=2] Leader -uve-topic-7-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,199] INFO [Broker id=2] Leader -uve-topic-6-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,202] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,202] INFO [Broker id=2] Leader -uve-topic-10-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,205] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,205] INFO [Broker id=2] Leader -uve-topic-27-0 starts at leader epoch 5 from offset 1793 with high watermark 1793 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,208] INFO [Broker id=2] Leader -uve-topic-23-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,213] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,213] INFO [Broker id=2] Leader -uve-topic-14-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,220] INFO [Broker id=2] Leader -uve-topic-2-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,223] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,223] INFO [Broker id=2] Leader -uve-topic-18-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,227] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,227] INFO [Broker id=2] Leader -uve-topic-19-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,230] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,230] INFO [Broker id=2] Leader -uve-topic-22-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,233] INFO [Broker id=2] Leader -uve-topic-24-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,236] INFO [Broker id=2] Leader -uve-topic-11-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,239] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,239] INFO [Broker id=2] Leader -uve-topic-10-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,242] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,242] INFO [Broker id=2] Leader -uve-topic-23-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,245] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-28 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,247] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,247] INFO [Broker id=2] Leader -uve-topic-4-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,251] INFO [Broker id=2] Leader -uve-topic-25-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,253] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,253] INFO [Broker id=2] Leader -uve-topic-12-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,256] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,256] INFO [Broker id=2] Leader -uve-topic-5-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,259] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,259] INFO [Broker id=2] Leader -uve-topic-4-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,261] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,261] INFO [Broker id=2] Leader -uve-topic-17-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,265] INFO [Broker id=2] Leader -uve-topic-0-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,267] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,268] INFO [Broker id=2] Leader -uve-topic-1-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,270] INFO [Broker id=2] Leader -uve-topic-16-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,273] INFO [Broker id=2] Leader -uve-topic-2-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,276] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,276] INFO [Broker id=2] Leader -uve-topic-9-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,279] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,279] INFO [Broker id=2] Leader -uve-topic-25-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,282] INFO [Broker id=2] Leader -uve-topic-12-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,285] INFO [Broker id=2] Leader -uve-topic-4-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,288] INFO [Broker id=2] Leader -uve-topic-3-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,291] INFO [Broker id=2] Leader -uve-topic-3-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,295] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,295] INFO [Broker id=2] Leader -uve-topic-0-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,298] INFO [Broker id=2] Leader -uve-topic-15-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,301] INFO [Broker id=2] Leader -uve-topic-6-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,305] INFO [Broker id=2] Leader -uve-topic-7-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,308] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,308] INFO [Broker id=2] Leader -uve-topic-8-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,311] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,311] INFO [Broker id=2] Leader -uve-topic-21-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,314] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,314] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,317] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,317] INFO [Broker id=2] Leader -uve-topic-25-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,320] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,320] INFO [Broker id=2] Leader -uve-topic-12-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,323] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,323] INFO [Broker id=2] Leader -uve-topic-19-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,326] INFO [Broker id=2] Leader -uve-topic-24-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,329] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,329] INFO [Broker id=2] Leader -uve-topic-11-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,332] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,332] INFO [Broker id=2] Leader -uve-topic-4-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,335] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,335] INFO [Broker id=2] Leader -uve-topic-24-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,338] INFO [Broker id=2] Leader -uve-topic-11-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,341] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,341] INFO [Broker id=2] Leader -uve-topic-5-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,343] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,344] INFO [Broker id=2] Leader -uve-topic-6-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,347] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,347] INFO [Broker id=2] Leader -uve-topic-27-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,350] INFO [Broker id=2] Leader -uve-topic-14-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,353] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,353] INFO [Broker id=2] Leader -uve-topic-18-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,356] INFO [Broker id=2] Leader -uve-topic-19-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,359] INFO [Broker id=2] Leader -uve-topic-10-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,363] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,363] INFO [Broker id=2] Leader -uve-topic-22-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,367] INFO [Broker id=2] Leader -uve-topic-23-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,370] INFO [Broker id=2] Leader -uve-topic-18-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,376] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,376] INFO [Broker id=2] Leader -uve-topic-24-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,381] INFO [Broker id=2] Leader -uve-topic-11-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,387] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,387] INFO [Broker id=2] Leader -uve-topic-26-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,391] INFO [Broker id=2] Leader -uve-topic-13-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,396] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,396] INFO [Broker id=2] Leader -uve-topic-25-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,402] INFO [Broker id=2] Leader -uve-topic-20-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,411] INFO [Broker id=2] Leader -uve-topic-12-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,414] INFO [Broker id=2] Leader -uve-topic-22-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,417] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,417] INFO [Broker id=2] Leader -uve-topic-16-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,420] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,420] INFO [Broker id=2] Leader -uve-topic-29-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,424] INFO [Broker id=2] Leader -uve-topic-21-0 starts at leader epoch 2 from offset 596 with high watermark 596 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 1. (state.change.logger)
[2025-02-13 02:11:08,427] INFO [Broker id=2] Leader -uve-topic-8-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,431] INFO [Broker id=2] Leader -uve-topic-17-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,434] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,435] INFO [Broker id=2] Leader -uve-topic-15-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,438] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,438] INFO [Broker id=2] Leader -uve-topic-28-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,442] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,442] INFO [Broker id=2] Leader -uve-topic-7-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,446] INFO [Broker id=2] Leader -uve-topic-10-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,449] INFO [Broker id=2] Leader -uve-topic-23-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,453] INFO [Broker id=2] Leader -uve-topic-1-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,459] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,459] INFO [Broker id=2] Leader -uve-topic-3-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,463] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,463] INFO [Broker id=2] Leader structured_syslog_topic-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,467] INFO [Broker id=2] Leader -uve-topic-5-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,472] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,472] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-6 starts at leader epoch 4 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,476] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,476] INFO [Broker id=2] Leader -uve-topic-4-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,481] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,481] INFO [Broker id=2] Leader -uve-topic-9-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,485] INFO [Broker id=2] Leader -uve-topic-9-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,488] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,488] INFO [Broker id=2] Leader -uve-topic-19-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,492] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,495] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,495] INFO [Broker id=2] Leader -uve-topic-17-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,499] INFO [Broker id=2] Leader -uve-topic-8-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,502] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,502] INFO [Broker id=2] Leader -uve-topic-1-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,506] INFO [Broker id=2] Leader -uve-topic-0-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,509] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,509] INFO [Broker id=2] Leader -uve-topic-24-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,512] INFO [Broker id=2] Leader -uve-topic-5-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,516] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,516] INFO [Broker id=2] Leader -uve-topic-7-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,519] INFO [Broker id=2] Leader -uve-topic-6-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,523] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,523] INFO [Broker id=2] Leader -uve-topic-23-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,527] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,527] INFO [Broker id=2] Leader -uve-topic-10-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,531] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,531] INFO [Broker id=2] Leader -uve-topic-3-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,534] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,534] INFO [Broker id=2] Leader -uve-topic-2-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,541] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,541] INFO [Broker id=2] Leader -uve-topic-18-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,544] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,544] INFO [Broker id=2] Leader -uve-topic-19-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,548] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,548] INFO [Broker id=2] Leader -uve-topic-4-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,551] INFO [Broker id=2] Leader -uve-topic-5-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,554] INFO [Broker id=2] Leader -uve-topic-6-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,557] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,557] INFO [Broker id=2] Leader -uve-topic-25-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,561] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,561] INFO [Broker id=2] Leader -uve-topic-12-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,565] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,565] INFO [Broker id=2] Leader -uve-topic-0-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,571] INFO [Broker id=2] Leader -uve-topic-4-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,575] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,575] INFO [Broker id=2] Leader -uve-topic-2-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,580] INFO [Broker id=2] Leader -uve-topic-18-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,584] INFO [Broker id=2] Leader -uve-topic-1-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,587] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,587] INFO [Broker id=2] Leader -uve-topic-9-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,591] INFO [Broker id=2] Leader -uve-topic-21-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,594] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,594] INFO [Broker id=2] Leader -uve-topic-3-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,598] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,598] INFO [Broker id=2] Leader -uve-topic-23-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,601] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,601] INFO [Broker id=2] Leader -uve-topic-24-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,605] INFO [Broker id=2] Leader -uve-topic-11-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,607] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,608] INFO [Broker id=2] Leader -uve-topic-15-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,615] INFO [Broker id=2] Leader -uve-topic-3-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,618] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,618] INFO [Broker id=2] Leader -uve-topic-28-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,621] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,621] INFO [Broker id=2] Leader -uve-topic-8-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,624] INFO [Broker id=2] Leader -uve-topic-20-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,627] INFO [Broker id=2] Leader -uve-topic-7-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,631] INFO [Broker id=2] Leader -uve-topic-27-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,634] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,634] INFO [Broker id=2] Leader -uve-topic-14-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,638] INFO [Broker id=2] Leader -uve-topic-16-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,641] INFO [Broker id=2] Leader -uve-topic-29-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,649] INFO [Broker id=2] Leader -uve-topic-24-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,652] INFO [Broker id=2] Leader -uve-topic-11-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,655] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,655] INFO [Broker id=2] Leader -uve-topic-19-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,659] INFO [Broker id=2] Leader -uve-topic-24-0 starts at leader epoch 5 from offset 836 with high watermark 836 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,662] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,662] INFO [Broker id=2] Leader -uve-topic-11-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,665] INFO [Broker id=2] Leader -uve-topic-3-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,670] INFO [Broker id=2] Leader structured_syslog_topic-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,677] INFO [Broker id=2] Leader -uve-topic-26-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,681] INFO [Broker id=2] Leader -uve-topic-13-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,684] INFO [Broker id=2] Leader -uve-topic-22-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,687] INFO [Broker id=2] Leader -uve-topic-10-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,690] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,690] INFO [Broker id=2] Leader structured_syslog_topic-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,696] INFO [Broker id=2] Leader -uve-topic-5-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,699] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,699] INFO [Broker id=2] Leader -uve-topic-25-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,703] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,703] INFO [Broker id=2] Leader -uve-topic-12-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,706] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,706] INFO [Broker id=2] Leader -uve-topic-24-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,709] INFO [Broker id=2] Leader -uve-topic-11-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,713] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,713] INFO [Broker id=2] Leader -uve-topic-26-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,716] INFO [Broker id=2] Leader -uve-topic-13-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,720] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,720] INFO [Broker id=2] Leader -uve-topic-17-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,723] INFO [Broker id=2] Leader -uve-topic-20-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,727] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-29 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,731] INFO [Broker id=2] Leader -uve-topic-22-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,734] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,734] INFO [Broker id=2] Leader -uve-topic-9-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,738] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,738] INFO [Broker id=2] Leader -uve-topic-19-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,741] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,741] INFO [Broker id=2] Leader -uve-topic-18-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,744] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,744] INFO [Broker id=2] Leader -uve-topic-24-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,747] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,747] INFO [Broker id=2] Leader -uve-topic-23-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,750] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,750] INFO [Broker id=2] Leader -uve-topic-11-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,753] INFO [Broker id=2] Leader -uve-topic-10-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,756] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,756] INFO [Broker id=2] Leader -uve-topic-3-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,759] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,760] INFO [Broker id=2] Leader -uve-topic-19-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,763] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,763] INFO [Broker id=2] Leader -uve-topic-23-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,766] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,766] INFO [Broker id=2] Leader -uve-topic-10-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,769] INFO [Broker id=2] Leader -uve-topic-15-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,772] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,772] INFO [Broker id=2] Leader -uve-topic-28-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,775] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,775] INFO [Broker id=2] Leader -uve-topic-21-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,779] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,779] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,783] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,783] INFO [Broker id=2] Leader -uve-topic-6-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,787] INFO [Broker id=2] Leader -uve-topic-19-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,790] INFO [Broker id=2] Leader -uve-topic-3-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,793] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,794] INFO [Broker id=2] Leader -uve-topic-26-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,797] INFO [Broker id=2] Leader -uve-topic-1-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,800] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,800] INFO [Broker id=2] Leader -uve-topic-9-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,804] INFO [Broker id=2] Leader -uve-topic-0-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,807] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,807] INFO [Broker id=2] Leader -uve-topic-1-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,810] INFO [Broker id=2] Leader -uve-topic-2-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,813] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,813] INFO [Broker id=2] Leader -uve-topic-25-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,821] INFO [Broker id=2] Leader -uve-topic-12-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,824] INFO [Broker id=2] Leader -uve-topic-4-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,827] INFO [Broker id=2] Leader -uve-topic-8-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,831] INFO [Broker id=2] Leader -uve-topic-0-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,834] INFO [Broker id=2] Leader -uve-topic-16-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,837] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,837] INFO [Broker id=2] Leader -uve-topic-29-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,841] INFO [Broker id=2] Leader -uve-topic-7-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,844] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,844] INFO [Broker id=2] Leader -uve-topic-8-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,847] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,847] INFO [Broker id=2] Leader -uve-topic-2-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,850] INFO [Broker id=2] Leader -uve-topic-27-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,854] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,854] INFO [Broker id=2] Leader -uve-topic-6-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,857] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,858] INFO [Broker id=2] Leader -uve-topic-7-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,861] INFO [Broker id=2] Leader -uve-topic-27-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,864] INFO [Broker id=2] Leader -uve-topic-14-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,868] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,868] INFO [Broker id=2] Leader -uve-topic-2-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,872] INFO [Broker id=2] Leader -uve-topic-24-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,876] INFO [Broker id=2] Leader -uve-topic-11-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,880] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,880] INFO [Broker id=2] Leader -uve-topic-18-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,883] INFO [Broker id=2] Leader -uve-topic-3-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,889] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,889] INFO [Broker id=2] Leader -uve-topic-23-15 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,893] INFO [Broker id=2] Leader -uve-topic-10-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,896] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,896] INFO [Broker id=2] Leader -uve-topic-4-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,899] INFO [Broker id=2] Leader -uve-topic-1-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,902] INFO [Broker id=2] Leader -uve-topic-6-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,906] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,906] INFO [Broker id=2] Leader -uve-topic-0-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,909] INFO [Broker id=2] Leader -uve-topic-9-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,912] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,912] INFO [Broker id=2] Leader -uve-topic-16-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,917] INFO [Broker id=2] Leader -uve-topic-29-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,922] INFO [Broker id=2] Leader -uve-topic-2-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,927] INFO [Broker id=2] Leader -uve-topic-1-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,931] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,931] INFO [Broker id=2] Leader -uve-topic-18-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,934] INFO [Broker id=2] Leader -uve-topic-3-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,938] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,939] INFO [Broker id=2] Leader -uve-topic-19-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,942] INFO [Broker id=2] Leader -uve-topic-25-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,946] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,946] INFO [Broker id=2] Leader -uve-topic-12-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,949] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,949] INFO [Broker id=2] Leader -uve-topic-24-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,952] INFO [Broker id=2] Leader -uve-topic-11-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,955] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,956] INFO [Broker id=2] Leader -uve-topic-15-10 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,959] INFO [Broker id=2] Leader -uve-topic-29-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,964] INFO [Broker id=2] Leader -uve-topic-28-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,967] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,967] INFO [Broker id=2] Leader -uve-topic-8-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,971] INFO [Broker id=2] Leader -uve-topic-20-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,975] INFO [Broker id=2] Leader -uve-topic-21-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,978] INFO [Broker id=2] Leader -uve-topic-18-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,982] INFO [Broker id=2] Leader structured_syslog_topic-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,987] INFO [Broker id=2] Leader -uve-topic-5-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:08,993] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,993] INFO [Broker id=2] Leader -uve-topic-27-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:08,997] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:08,997] INFO [Broker id=2] Leader -uve-topic-14-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,001] INFO [Broker id=2] Leader -uve-topic-7-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,004] INFO [Broker id=2] Leader -uve-topic-20-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,007] INFO [Broker id=2] Leader -uve-topic-27-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,011] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,011] INFO [Broker id=2] Leader -uve-topic-26-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,016] INFO [Broker id=2] Leader -uve-topic-13-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,019] INFO [Broker id=2] Leader -uve-topic-14-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,022] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-28 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,022] INFO [Broker id=2] Leader -uve-topic-23-12 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,025] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,025] INFO [Broker id=2] Leader -uve-topic-10-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,028] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,028] INFO [Broker id=2] Leader -uve-topic-19-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,031] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,031] INFO [Broker id=2] Leader -uve-topic-22-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,036] INFO [Broker id=2] Leader structured_syslog_topic-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,042] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,042] INFO [Broker id=2] Leader -uve-topic-24-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,045] INFO [Broker id=2] Leader -uve-topic-11-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,048] INFO [Broker id=2] Leader -uve-topic-26-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,052] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,052] INFO [Broker id=2] Leader -uve-topic-25-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,057] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,057] INFO [Broker id=2] Leader -uve-topic-12-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,060] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,060] INFO [Broker id=2] Leader -uve-topic-13-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,063] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,063] INFO [Broker id=2] Leader -uve-topic-21-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,065] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,066] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 5 from offset 5 with high watermark 5 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,069] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,069] INFO [Broker id=2] Leader -uve-topic-17-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,072] INFO [Broker id=2] Leader -uve-topic-9-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,076] INFO [Broker id=2] Leader -uve-topic-23-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,080] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,080] INFO [Broker id=2] Leader -uve-topic-0-0 starts at leader epoch 5 from offset 3638 with high watermark 3638 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,084] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,084] INFO [Broker id=2] Leader -uve-topic-10-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,088] INFO [Broker id=2] Leader -uve-topic-18-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,092] INFO [Broker id=2] Leader -uve-topic-19-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,095] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,095] INFO [Broker id=2] Leader -uve-topic-23-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,099] INFO [Broker id=2] Leader -uve-topic-10-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,104] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,104] INFO [Broker id=2] Leader -uve-topic-2-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,107] INFO [Broker id=2] Leader -uve-topic-28-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,112] INFO [Broker id=2] Leader -uve-topic-15-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,115] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,116] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-26 starts at leader epoch 5 from offset 6 with high watermark 6 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,119] INFO [Broker id=2] Leader -uve-topic-2-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,122] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,122] INFO [Broker id=2] Leader -uve-topic-13-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,127] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,127] INFO [Broker id=2] Leader -uve-topic-26-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,131] INFO [Broker id=2] Leader -uve-topic-12-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,134] INFO [Broker id=2] Leader -uve-topic-25-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,137] INFO [Broker id=2] Leader -uve-topic-14-6 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,140] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,140] INFO [Broker id=2] Leader -uve-topic-27-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,144] INFO [Broker id=2] Leader -uve-topic-10-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,147] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-11 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,147] INFO [Broker id=2] Leader -uve-topic-23-9 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,150] INFO [Broker id=2] Leader -uve-topic-12-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,154] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,154] INFO [Broker id=2] Leader -uve-topic-25-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,157] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,157] INFO [Broker id=2] Leader -uve-topic-11-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,160] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-3 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,160] INFO [Broker id=2] Leader -uve-topic-24-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,163] INFO [Broker id=2] Leader -uve-topic-4-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,166] INFO [Broker id=2] Leader -uve-topic-8-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,170] INFO [Broker id=2] Leader -uve-topic-0-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,173] INFO [Broker id=2] Leader -uve-topic-18-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,177] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,177] INFO [Broker id=2] Leader -uve-topic-2-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,180] INFO [Broker id=2] Leader -uve-topic-1-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,184] INFO [Broker id=2] Leader structured_syslog_topic-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,187] INFO [Broker id=2] Leader -uve-topic-7-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,191] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,191] INFO [Broker id=2] Leader -uve-topic-14-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,194] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,194] INFO [Broker id=2] Leader -uve-topic-27-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,197] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,197] INFO [Broker id=2] Leader -uve-topic-6-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,200] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,200] INFO [Broker id=2] Leader -uve-topic-2-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,203] INFO [Broker id=2] Leader -uve-topic-18-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,206] INFO [Broker id=2] Leader -uve-topic-5-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,209] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,209] INFO [Broker id=2] Leader -uve-topic-9-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,213] INFO [Broker id=2] Leader -uve-topic-22-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,216] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,216] INFO [Broker id=2] Leader -uve-topic-13-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,219] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,219] INFO [Broker id=2] Leader -uve-topic-26-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,222] INFO [Broker id=2] Leader -uve-topic-1-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,226] INFO [Broker id=2] Leader -uve-topic-17-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,229] INFO [Broker id=2] Leader -uve-topic-18-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,232] INFO [Broker id=2] Leader -uve-topic-21-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,234] INFO [Broker id=2] Leader -uve-topic-20-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,237] INFO [Broker id=2] Leader -uve-topic-22-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,240] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,240] INFO [Broker id=2] Leader -uve-topic-3-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,244] INFO [Broker id=2] Leader -uve-topic-19-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,246] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,247] INFO [Broker id=2] Leader -uve-topic-10-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,249] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-10-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,249] INFO [Broker id=2] Leader -uve-topic-11-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,253] INFO [Broker id=2] Leader -uve-topic-23-0 starts at leader epoch 2 from offset 1312 with high watermark 1312 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 1. (state.change.logger)
[2025-02-13 02:11:09,256] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,256] INFO [Broker id=2] Leader -uve-topic-24-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,260] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,260] INFO [Broker id=2] Leader -uve-topic-28-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,264] INFO [Broker id=2] Leader -uve-topic-3-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,268] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,268] INFO [Broker id=2] Leader -uve-topic-15-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,271] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-26 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,271] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-23 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,276] INFO [Broker id=2] Leader -uve-topic-19-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,279] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,279] INFO [Broker id=2] Leader -uve-topic-17-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,282] INFO [Broker id=2] Leader -uve-topic-20-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,285] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,285] INFO [Broker id=2] Leader -uve-topic-29-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,288] INFO [Broker id=2] Leader -uve-topic-16-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,292] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,292] INFO [Broker id=2] Leader -uve-topic-21-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,295] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,295] INFO [Broker id=2] Leader -uve-topic-28-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,298] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-5 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,298] INFO [Broker id=2] Leader -uve-topic-29-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,301] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,301] INFO [Broker id=2] Leader -uve-topic-15-7 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,304] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,304] INFO [Broker id=2] Leader -uve-topic-16-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,307] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,307] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-4 starts at leader epoch 5 from offset 3 with high watermark 3 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,310] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,310] INFO [Broker id=2] Leader -uve-topic-9-26 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,314] INFO [Broker id=2] Leader -uve-topic-1-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,317] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,317] INFO [Broker id=2] Leader -uve-topic-23-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,321] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,321] INFO [Broker id=2] Leader -uve-topic-10-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,324] INFO [Broker id=2] Leader structured_syslog_topic-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,328] INFO [Broker id=2] Leader -uve-topic-2-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,333] INFO [Broker id=2] Leader -uve-topic-22-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,336] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,336] INFO [Broker id=2] Leader -uve-topic-18-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,340] INFO [Broker id=2] Leader -uve-topic-6-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,343] INFO [Broker id=2] Leader -uve-topic-5-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,346] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-9 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,346] INFO [Broker id=2] Leader -uve-topic-14-3 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,350] INFO [Broker id=2] Leader -uve-topic-27-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,352] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,352] INFO [Broker id=2] Leader -uve-topic-7-11 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,361] INFO [Broker id=2] Leader -uve-topic-20-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,365] INFO [Broker id=2] Leader -uve-topic-0-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,368] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,368] INFO [Broker id=2] Leader -uve-topic-9-23 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,371] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,371] INFO [Broker id=2] Leader -uve-topic-1-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,374] INFO [Broker id=2] Leader -uve-topic-17-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,377] INFO [Broker id=2] Leader structured_syslog_topic-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,380] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition structured_syslog_topic-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,380] INFO [Broker id=2] Leader -uve-topic-5-28 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,384] INFO [Broker id=2] Leader -uve-topic-4-8 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,386] INFO [Broker id=2] Leader -uve-topic-11-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,390] INFO [Broker id=2] Leader -uve-topic-24-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,395] INFO [Broker id=2] Leader -uve-topic-13-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,399] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,399] INFO [Broker id=2] Leader -uve-topic-12-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,404] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,404] INFO [Broker id=2] Leader -uve-topic-26-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,406] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-26-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,406] INFO [Broker id=2] Leader -uve-topic-29-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,409] INFO [Broker id=2] Leader -uve-topic-16-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,412] INFO [Broker id=2] Leader -uve-topic-17-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,416] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,416] INFO [Broker id=2] Leader -uve-topic-22-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,420] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,421] INFO [Broker id=2] Leader -uve-topic-18-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,425] INFO [Broker id=2] Leader -uve-topic-21-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,428] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,429] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 5 from offset 5 with high watermark 5 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,433] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition HEALTH_CHECK_TOPIC-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,433] INFO [Broker id=2] Leader -uve-topic-17-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,439] INFO [Broker id=2] Leader -uve-topic-23-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,444] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-16 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,444] INFO [Broker id=2] Leader -uve-topic-10-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,450] INFO [Broker id=2] Leader -uve-topic-12-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,455] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,455] INFO [Broker id=2] Leader -uve-topic-25-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,459] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,459] INFO [Broker id=2] Leader -uve-topic-11-0 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,462] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-11-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,462] INFO [Broker id=2] Leader -uve-topic-19-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,468] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,468] INFO [Broker id=2] Leader -uve-topic-21-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,473] INFO [Broker id=2] Leader -uve-topic-20-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,478] INFO [Broker id=2] Leader -uve-topic-28-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,483] INFO [Broker id=2] Leader -uve-topic-15-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,487] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-23 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,487] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-20 starts at leader epoch 5 from offset 2 with high watermark 2 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,492] INFO [Broker id=2] Leader -uve-topic-22-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,497] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,497] INFO [Broker id=2] Leader -uve-topic-18-17 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,502] INFO [Broker id=2] Leader -uve-topic-14-22 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,505] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-22 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,506] INFO [Broker id=2] Leader -uve-topic-13-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,509] INFO [Broker id=2] Leader -uve-topic-26-0 starts at leader epoch 5 from offset 1047 with high watermark 1047 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,512] INFO [Broker id=2] Leader -uve-topic-27-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,517] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,517] INFO [Broker id=2] Leader -uve-topic-6-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,523] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-10 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,523] INFO [Broker id=2] Leader -uve-topic-1-14 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,527] INFO [Broker id=2] Leader -uve-topic-0-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,532] INFO [Broker id=2] Leader -uve-topic-22-5 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,537] INFO [Broker id=2] Leader -uve-topic-4-27 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,541] INFO [Broker id=2] Leader -uve-topic-3-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,546] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,546] INFO [Broker id=2] Leader -uve-topic-9-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,552] INFO [Broker id=2] Leader -uve-topic-28-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,556] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-28-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,557] INFO [Broker id=2] Leader -uve-topic-29-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,561] INFO [Broker id=2] Leader -uve-topic-15-4 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,566] INFO [Broker id=2] Leader -uve-topic-16-24 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,569] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,569] INFO [Broker id=2] Leader -uve-topic-8-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,574] INFO [Broker id=2] Leader -uve-topic-2-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,579] INFO [Broker id=2] Leader -uve-topic-3-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,583] INFO [Broker id=2] Leader -uve-topic-9-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,589] INFO [Broker id=2] Leader -uve-topic-2-25 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,594] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-2-25 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,594] INFO [Broker id=2] Leader -uve-topic-1-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,599] INFO [Broker id=2] Leader structured_syslog_topic-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,603] INFO [Broker id=2] Leader -uve-topic-22-12 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,608] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-12 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,608] INFO [Broker id=2] Leader -uve-topic-1-21 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,613] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-1-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,613] INFO [Broker id=2] Leader -uve-topic-0-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,617] INFO [Broker id=2] Leader -uve-topic-9-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,623] INFO [Broker id=2] Leader -uve-topic-4-24 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,627] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-4-24 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,627] INFO [Broker id=2] Leader -uve-topic-6-26 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,632] INFO [Broker id=2] Leader -uve-topic-5-6 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,637] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-5-6 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,637] INFO [Broker id=2] Leader -uve-topic-9-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,641] INFO [Broker id=2] Leader -uve-topic-22-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,646] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,646] INFO [Broker id=2] Leader -uve-topic-1-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,652] INFO [Broker id=2] Leader -uve-topic-17-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,656] INFO [Broker id=2] Leader -uve-topic-3-23 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,661] INFO [Broker id=2] Leader -uve-topic-19-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,665] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-19-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,666] INFO [Broker id=2] Leader -uve-topic-4-5 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,671] INFO [Broker id=2] Leader -uve-topic-5-25 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,676] INFO [Broker id=2] Leader -uve-topic-20-0 starts at leader epoch 5 from offset 897 with high watermark 897 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,681] INFO [Broker id=2] Leader -uve-topic-28-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,686] INFO [Broker id=2] Leader -uve-topic-3-4 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,690] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-3-4 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,691] INFO [Broker id=2] Leader -uve-topic-15-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,695] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-20 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,695] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-17 starts at leader epoch 5 from offset 4 with high watermark 4 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,700] INFO [Broker id=2] Leader -uve-topic-8-28 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,706] INFO [Broker id=2] Leader -uve-topic-0-10 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,710] INFO [Broker id=2] Leader -uve-topic-17-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,715] INFO [Broker id=2] Leader -uve-topic-20-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,721] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-20-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,722] INFO [Broker id=2] Leader -uve-topic-29-0 starts at leader epoch 5 from offset 849 with high watermark 849 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,726] INFO [Broker id=2] Leader -uve-topic-16-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,731] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,731] INFO [Broker id=2] Leader -uve-topic-21-1 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,735] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-21-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,736] INFO [Broker id=2] Leader -uve-topic-2-22 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,740] INFO [Broker id=2] Leader -uve-topic-9-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,745] INFO [Broker id=2] Leader -uve-topic-1-2 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,749] INFO [Broker id=2] Leader -uve-topic-23-13 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,753] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-23-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,753] INFO [Broker id=2] Leader -uve-topic-10-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,758] INFO [Broker id=2] Leader -uve-topic-17-13 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,763] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-17-13 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,763] INFO [Broker id=2] Leader structured_syslog_topic-18 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,768] INFO [Broker id=2] Leader -uve-topic-2-3 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,772] INFO [Broker id=2] Leader -uve-topic-14-19 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,777] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,777] INFO [Broker id=2] Leader -uve-topic-27-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,781] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-27-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,781] INFO [Broker id=2] Leader -uve-topic-7-27 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,786] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-27 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,786] INFO [Broker id=2] Leader -uve-topic-6-7 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,791] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-6-7 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,792] INFO [Broker id=2] Leader -uve-topic-13-18 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,798] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-13-18 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,798] INFO [Broker id=2] Leader -uve-topic-26-16 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,806] INFO [Broker id=2] Leader -uve-topic-14-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,811] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-14-0 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,811] INFO [Broker id=2] Leader -uve-topic-8-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,817] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-8-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,817] INFO [Broker id=2] Leader -uve-topic-0-20 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,822] INFO [Broker id=2] Leader -uve-topic-21-11 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,827] INFO [Broker id=2] Leader -uve-topic-12-17 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,834] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-12-17 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,834] INFO [Broker id=2] Leader -uve-topic-25-15 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,840] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-25-15 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,840] INFO [Broker id=2] Leader -uve-topic-21-20 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,846] INFO [Broker id=2] Leader -uve-topic-0-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,851] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-0-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,851] INFO [Broker id=2] Leader -uve-topic-22-2 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,856] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-22-2 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,856] INFO [Broker id=2] Leader -uve-topic-9-29 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,861] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-9-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,861] INFO [Broker id=2] Leader -uve-topic-8-9 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,866] INFO [Broker id=2] Leader -uve-topic-29-29 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,871] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-29 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,871] INFO [Broker id=2] Leader -uve-topic-11-16 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,875] INFO [Broker id=2] Leader -uve-topic-24-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,880] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-24-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,880] INFO [Broker id=2] Leader -uve-topic-18-14 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,887] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-18-14 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,888] INFO [Broker id=2] Leader -uve-topic-29-19 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,892] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-29-19 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,892] INFO [Broker id=2] Leader -uve-topic-15-1 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,897] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-15-1 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,897] INFO [Broker id=2] Leader -uve-topic-16-21 starts at leader epoch 5 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:11:09,903] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-16-21 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,903] INFO [Broker id=2] Leader -uve-topic-7-8 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was 3. (state.change.logger)
[2025-02-13 02:11:09,908] INFO [Broker id=2] Skipped the become-leader state change after marking its partition as leader with correlation id 1 from controller 3 epoch 3 for partition -uve-topic-7-8 (last update controller epoch 2) since it is already the leader for the partition. (state.change.logger)
[2025-02-13 02:11:09,920] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 3 with correlation id 2 (state.change.logger)
[2025-02-13 02:11:09,925] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 3 from controller 3 for 960 partitions (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-23-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,926] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-24-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-25-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-20-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-21-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,927] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-29-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-2-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,928] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-0-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-12-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,929] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-13-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition structured_syslog_topic-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-14-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-6-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-7-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,930] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,931] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-17-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,932] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 3 epoch 3 for partition -uve-topic-18-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,941] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 3 with correlation id 4 (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 5 from controller 3 for 960 partitions (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-23-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-24-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,946] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-25-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-20-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-21-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-29-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,947] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-2-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-0-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,948] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-12-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-13-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition structured_syslog_topic-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,949] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-14-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-6-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-7-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,950] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,960] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-17-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,961] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 3 with correlation id 5 epoch 3 for partition -uve-topic-18-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:09,970] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 3 with correlation id 6 (state.change.logger)
[2025-02-13 02:11:11,213] INFO [Controller id=2 epoch=4] Sending UpdateMetadata request to brokers Set(2) for 0 partitions (state.change.logger)
[2025-02-13 02:11:11,302] INFO [Controller id=2 epoch=4] Sending LeaderAndIsr request to broker 2 with 960 become-leader and 0 become-follower partitions (state.change.logger)
[2025-02-13 02:11:11,304] INFO [Controller id=2 epoch=4] Sending UpdateMetadata request to brokers Set(2) for 960 partitions (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 1 from controller 2 for 960 partitions (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-23-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,328] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-24-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-25-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-20-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-21-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,329] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-29-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-2-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,330] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-0-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-12-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,331] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-13-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition structured_syslog_topic-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-14-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-7-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,332] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,333] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-17-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,334] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 1 epoch 4 for partition -uve-topic-18-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,347] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 4 with correlation id 2 (state.change.logger)
[2025-02-13 02:11:11,388] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,389] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,389] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,389] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,390] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,391] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,392] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-0 state changed to (Leader:2,ISR:2,LeaderEpoch:2,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,393] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,394] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,395] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,396] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,397] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,398] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-0 state changed to (Leader:2,ISR:2,LeaderEpoch:2,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,399] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,400] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,401] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,402] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,403] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,404] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,405] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,406] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,407] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,408] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-0 state changed to (Leader:2,ISR:2,LeaderEpoch:2,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,409] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,410] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,411] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,412] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 1 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,504] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,505] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,506] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-0 state changed to (Leader:2,ISR:2,LeaderEpoch:2,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,507] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,508] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,509] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,510] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-0 state changed to (Leader:2,ISR:2,LeaderEpoch:2,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,511] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,512] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,513] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,514] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-7 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,515] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,516] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-9 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-8 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-0 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-5 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,517] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-23 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-24 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-6 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-15 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,518] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-0 state changed to (Leader:2,ISR:2,LeaderEpoch:2,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-22-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-12-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-22 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-16 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-17 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-6 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-29 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-8-21 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,519] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-3 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-27 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-21 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-19 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-12 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-11-20 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-21-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-8 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-28 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-10 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-9 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-7-13 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-16 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-18-14 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-17 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition HEALTH_CHECK_TOPIC-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-28 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-3 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-1 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-2 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-3-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-2 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-1-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-4-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-2-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-18 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-26 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-27 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-13 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-19-1 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-29-0 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-10-26 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-20-25 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,520] INFO [Controller id=2 epoch=4] Partition -uve-topic-16-15 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-26-14 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-5-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-22 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition structured_syslog_topic-4 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-28-29 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-6-23 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-23-24 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-13-25 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-0-7 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-12 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-18 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-9-11 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-27-4 state changed to (Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-17-5 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-24-10 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-14-11 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-25-19 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Partition -uve-topic-15-20 state changed to (Leader:2,ISR:2,LeaderEpoch:5,ControllerEpoch:4) after removing replica 3 from the ISR as part of transition to OfflineReplica (state.change.logger)
[2025-02-13 02:11:11,521] INFO [Controller id=2 epoch=4] Sending LeaderAndIsr request to broker 2 with 960 become-leader and 0 become-follower partitions (state.change.logger)
[2025-02-13 02:11:11,522] INFO [Controller id=2 epoch=4] Sending UpdateMetadata request to brokers Set(2) for 960 partitions (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 3 from controller 2 for 960 partitions (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,525] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-22-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-23-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-24-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-25-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-20-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-21-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,526] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-26-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-27-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-28-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-29-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition HEALTH_CHECK_TOPIC-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-2-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-3-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,527] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-0-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-0 since its associated leader epoch 2 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-1-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-11-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-12-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-8-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,528] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-13-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition structured_syslog_topic-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-9-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-14-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-6-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-7-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-12 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-6 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-9 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-3 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-0 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-27 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-24 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-21 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-18 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,529] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-15 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-4-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-10-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-5-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-19-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-15-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-16-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-16 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-8 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-19 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-2 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-13 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-5 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-10 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-29 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-7 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-23 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-26 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-4 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-20 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-1 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-28 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-17 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-25 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-14 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,530] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-11 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-22 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-17-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-29 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-18 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-7 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-26 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-15 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-4 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-23 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-12 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-1 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-28 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-17 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-9 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-20 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-14 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-25 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-3 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-6 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-22 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-0 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-11 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-19 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-8 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-24 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-5 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-16 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-27 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-10 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-21 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-2 since its associated leader epoch 4 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,531] INFO [Broker id=2] Ignoring LeaderAndIsr request from controller 2 with correlation id 3 epoch 4 for partition -uve-topic-18-13 since its associated leader epoch 5 matches the current leader epoch (state.change.logger)
[2025-02-13 02:11:11,543] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 4 with correlation id 4 (state.change.logger)
[2025-02-13 02:13:11,554] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 5 with correlation id 0 (state.change.logger)
[2025-02-13 02:13:11,583] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 1 from controller 3 for 960 partitions (state.change.logger)
[2025-02-13 02:13:11,979] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,061] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,070] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,077] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,086] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,097] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,115] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,150] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,163] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,169] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,182] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,236] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,255] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,263] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,271] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,275] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,283] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,292] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,299] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,312] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,318] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,326] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,333] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,340] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,352] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,366] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,380] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,392] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,400] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,407] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,417] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,425] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,434] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,441] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,452] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,460] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,474] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,486] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,499] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,510] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,527] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,540] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,561] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,577] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,585] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,596] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,601] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,606] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,615] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,620] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,628] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,634] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,660] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,686] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,703] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,725] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,735] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,740] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,745] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,749] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,753] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,757] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,761] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,766] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,770] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,774] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,778] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,782] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,787] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,792] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,796] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,801] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,805] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,809] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,813] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,817] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,821] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,825] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,830] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,843] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,850] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,855] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,863] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,868] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,873] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,877] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,881] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,887] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,892] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,905] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,909] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,913] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,917] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,920] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,923] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,927] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,931] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,934] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,937] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,943] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,947] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,951] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,954] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,957] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,960] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,965] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,968] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,971] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,973] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,976] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,979] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,982] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,985] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,988] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,996] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:12,999] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,005] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,036] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,041] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,050] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,058] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,064] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,070] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,079] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,083] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,088] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,098] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,103] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,110] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,115] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,118] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,122] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,134] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,137] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,141] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,145] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,149] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,152] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,155] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,159] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,166] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,172] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,179] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,190] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,201] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,206] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,210] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,219] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,232] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,240] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,247] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,259] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,262] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,270] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,274] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,278] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,282] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,285] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,288] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,310] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,314] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,318] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,326] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,331] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,342] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,350] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,353] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,357] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,360] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,363] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,366] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,369] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,373] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,377] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,381] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,384] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,389] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,392] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,396] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,401] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,410] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,417] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,421] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,424] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,436] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,441] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,444] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,448] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,452] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,455] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,463] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,467] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,472] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,476] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,483] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,487] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,493] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,497] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,501] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,504] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,508] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,512] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,515] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,519] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,522] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,525] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,528] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,534] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,537] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,542] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,546] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,551] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,555] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,558] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,561] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,565] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,573] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,578] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,585] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,589] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,611] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,623] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,639] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,644] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,647] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,651] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,655] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,658] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,661] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,664] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,668] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,670] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,673] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,676] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,682] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,685] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,688] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,691] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,694] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,697] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,701] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,704] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,707] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,710] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,712] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,715] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,718] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,722] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,728] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,732] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,738] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,744] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,753] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,756] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,760] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,764] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,769] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,777] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,782] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,786] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,789] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,792] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,795] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,798] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,801] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,804] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,806] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,809] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,812] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,814] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,816] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,820] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,824] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,827] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,831] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,835] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,839] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,844] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,847] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,851] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,855] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,859] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,863] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,867] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,870] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,874] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,877] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,880] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,882] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,885] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,888] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,890] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,892] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,896] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,899] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,902] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,904] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,906] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,908] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,910] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,912] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,915] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,917] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,920] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,922] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,925] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,928] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,930] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,932] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,935] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,937] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,943] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,947] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,950] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,952] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,955] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,957] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,960] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,962] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,964] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,969] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,972] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,975] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,979] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,981] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,983] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,986] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,988] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,990] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,994] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:13,996] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,000] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,003] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,009] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,011] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,014] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,016] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,020] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,023] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,026] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,028] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,031] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,033] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,036] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,038] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,046] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,051] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,055] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,058] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,062] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,065] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,070] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,074] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,078] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,081] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,084] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,087] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,090] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,093] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,096] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,099] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,101] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,104] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,106] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,108] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,111] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,115] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,119] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,121] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,124] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,126] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,128] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,130] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,156] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,162] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,165] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,175] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,178] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,180] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,183] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,185] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,188] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,191] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,194] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,197] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,201] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,204] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,209] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,212] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,215] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,218] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,221] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,223] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,225] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,228] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,230] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,233] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,236] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,239] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,241] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,244] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,246] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,248] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,251] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,253] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,255] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,258] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,261] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,264] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,266] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,269] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,271] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,282] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,284] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,290] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,292] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,297] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,300] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,302] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,304] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,307] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,309] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,311] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,317] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,320] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,322] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,324] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,328] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,331] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,336] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,343] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,347] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,350] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,353] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,356] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,358] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,361] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,365] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,367] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,370] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,372] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,374] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,376] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,380] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,382] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,385] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,388] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,390] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,393] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,396] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,400] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,402] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,405] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,407] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,411] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,413] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,415] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,419] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,422] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,425] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,442] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,451] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,459] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,464] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,468] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,471] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,479] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,499] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,507] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,511] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,519] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,522] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,538] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,543] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,552] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,566] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,570] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,574] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,579] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,582] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,584] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,587] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,590] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,592] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,596] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,599] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,602] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,607] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,610] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,613] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,617] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,622] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,625] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,629] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,632] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,642] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,648] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,651] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,657] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,663] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,669] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,674] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,677] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,682] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,685] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,690] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,694] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,697] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,701] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,704] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,716] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,721] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,726] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,729] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,750] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,760] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,768] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,773] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,776] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,785] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,794] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,800] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,811] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,814] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,818] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,821] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,825] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,827] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,830] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,855] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,864] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,869] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,873] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,884] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,888] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,894] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,906] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,910] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,920] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,938] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,943] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,947] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,951] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,955] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,962] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,973] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,980] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,987] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:14,996] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,001] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,005] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,008] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,012] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,015] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,022] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,034] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,042] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,051] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,056] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,059] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,066] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,069] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,072] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,080] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,084] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,089] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,092] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,096] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,099] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,101] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,104] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,106] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,109] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,116] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,137] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,144] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,148] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,157] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,170] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,176] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,181] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,184] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,190] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,192] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,197] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,200] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,205] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,208] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,210] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,212] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,215] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,218] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,220] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,223] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,226] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,233] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,242] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,250] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,254] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,257] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,261] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,264] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,267] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,269] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,272] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,276] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,279] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,282] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,285] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,288] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,298] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,303] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,306] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,309] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,312] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,316] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,320] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,322] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,335] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,344] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,350] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,356] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,361] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,363] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,369] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,371] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,379] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,383] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,386] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,389] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,392] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,395] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,398] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,400] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,403] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,445] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,453] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,457] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,461] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,467] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,478] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,481] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,487] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,491] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,496] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,501] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,504] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,506] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,512] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,515] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,518] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,520] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,523] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,532] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,535] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,541] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,546] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,549] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,551] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,554] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,560] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,567] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,571] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,573] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,578] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,582] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,588] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,590] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,593] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,596] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,598] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,603] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,606] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,608] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,611] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,618] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,621] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,624] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,626] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,629] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,632] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,635] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,637] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,639] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,644] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,652] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,655] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,658] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,661] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,677] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,682] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,694] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,697] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,699] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,713] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,718] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,722] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,730] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,733] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,736] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,739] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,741] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,746] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,753] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,768] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,782] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,785] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,790] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,793] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,796] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,799] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,802] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,804] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,807] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,810] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,813] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,815] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,818] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,822] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,824] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,827] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,829] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,831] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,834] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,836] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,841] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,844] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,848] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,854] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,876] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,879] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,882] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,884] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,887] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,889] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,892] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,895] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,896] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,899] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,901] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,903] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,905] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,908] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,910] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,912] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,915] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,917] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,919] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,921] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,927] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,930] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,933] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,936] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,939] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,942] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,945] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,950] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,956] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,976] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,984] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,987] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,989] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,991] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,994] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:15,997] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,000] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,004] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,007] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,011] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,013] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,017] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,020] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,024] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,028] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,032] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,036] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,044] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,056] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,062] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,066] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,072] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,076] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,084] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,088] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,097] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,103] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,107] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,116] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,122] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,130] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,139] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,143] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,148] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,172] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,177] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,187] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,190] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,193] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,204] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,209] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,213] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,216] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,219] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,224] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,231] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,234] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,237] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,240] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,245] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,249] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,257] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,260] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,264] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,268] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,277] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,281] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,284] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,332] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,338] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,344] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,350] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,353] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,357] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,362] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,367] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,375] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,381] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,386] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,390] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,398] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,401] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,406] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,415] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,418] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,421] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,424] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,427] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,429] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,431] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,434] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,436] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,439] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,442] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,445] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,447] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,450] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,452] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,454] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,456] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,459] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,461] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,464] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,467] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,469] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,472] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,476] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,480] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,483] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,486] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,488] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,491] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,493] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,495] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,497] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,502] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,505] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,508] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,511] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,514] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,516] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,519] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,522] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,525] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,528] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,531] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,534] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,536] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,539] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,541] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,544] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,547] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,568] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,572] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,576] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,579] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,583] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,586] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,589] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,592] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,595] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,601] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,610] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,613] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,616] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,621] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,623] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,626] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,628] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,631] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,634] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,637] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,639] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,642] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,645] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,647] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,650] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,652] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,655] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,657] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,660] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,662] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,665] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,667] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,670] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,672] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,674] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,676] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,678] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,681] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,683] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,686] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,688] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,691] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,699] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,707] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,711] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,715] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,718] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,721] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,725] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,728] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,731] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,734] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,736] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,739] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,742] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,745] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,751] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,758] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,761] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,776] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,781] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,788] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,792] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,796] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,799] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,804] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,808] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,811] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,814] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,817] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,819] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,821] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,824] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,826] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,828] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,830] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,832] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,835] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,837] ERROR [Broker id=2] Received LeaderAndIsrRequest with correlation id 1 from controller 3 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-13 02:13:16,841] INFO [Broker id=2] Stopped fetchers as part of become-follower request from controller 3 epoch 5 with correlation id 1 for 0 partitions (state.change.logger)
[2025-02-13 02:13:16,885] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 5 with correlation id 2 (state.change.logger)
[2025-02-13 02:13:16,891] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 3 from controller 3 for 960 partitions (state.change.logger)
[2025-02-13 02:13:16,910] INFO [Broker id=2] Stopped fetchers as part of LeaderAndIsr request correlationId 3 from controller 3 epoch 5 as part of the become-leader transition for 960 partitions (state.change.logger)
[2025-02-13 02:13:16,923] INFO [Broker id=2] Leader -uve-topic-22-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,957] INFO [Broker id=2] Leader -uve-topic-23-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,965] INFO [Broker id=2] Leader -uve-topic-17-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,968] INFO [Broker id=2] Leader -uve-topic-16-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,976] INFO [Broker id=2] Leader -uve-topic-29-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,980] INFO [Broker id=2] Leader -uve-topic-2-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,984] INFO [Broker id=2] Leader -uve-topic-18-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,987] INFO [Broker id=2] Leader -uve-topic-27-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,992] INFO [Broker id=2] Leader -uve-topic-14-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:16,996] INFO [Broker id=2] Leader -uve-topic-5-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,000] INFO [Broker id=2] Leader -uve-topic-16-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,003] INFO [Broker id=2] Leader -uve-topic-29-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,007] INFO [Broker id=2] Leader -uve-topic-17-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,012] INFO [Broker id=2] Leader -uve-topic-21-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,015] INFO [Broker id=2] Leader -uve-topic-11-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,019] INFO [Broker id=2] Leader -uve-topic-24-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,024] INFO [Broker id=2] Leader -uve-topic-13-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,027] INFO [Broker id=2] Leader -uve-topic-26-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,031] INFO [Broker id=2] Leader -uve-topic-8-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,035] INFO [Broker id=2] Leader -uve-topic-0-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,038] INFO [Broker id=2] Leader -uve-topic-17-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,042] INFO [Broker id=2] Leader -uve-topic-9-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,045] INFO [Broker id=2] Leader -uve-topic-0-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,049] INFO [Broker id=2] Leader -uve-topic-20-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,053] INFO [Broker id=2] Leader -uve-topic-1-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,057] INFO [Broker id=2] Leader -uve-topic-3-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,062] INFO [Broker id=2] Leader -uve-topic-2-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,066] INFO [Broker id=2] Leader -uve-topic-7-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,070] INFO [Broker id=2] Leader -uve-topic-6-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,073] INFO [Broker id=2] Leader -uve-topic-15-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,077] INFO [Broker id=2] Leader -uve-topic-28-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,080] INFO [Broker id=2] Leader -uve-topic-6-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,085] INFO [Broker id=2] Leader -uve-topic-7-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,089] INFO [Broker id=2] Leader -uve-topic-22-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,092] INFO [Broker id=2] Leader -uve-topic-0-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,096] INFO [Broker id=2] Leader -uve-topic-9-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,100] INFO [Broker id=2] Leader -uve-topic-21-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,104] INFO [Broker id=2] Leader structured_syslog_topic-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,108] INFO [Broker id=2] Leader -uve-topic-5-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,112] INFO [Broker id=2] Leader -uve-topic-4-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,117] INFO [Broker id=2] Leader -uve-topic-17-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,122] INFO [Broker id=2] Leader -uve-topic-8-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,125] INFO [Broker id=2] Leader -uve-topic-3-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,131] INFO [Broker id=2] Leader -uve-topic-4-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,134] INFO [Broker id=2] Leader -uve-topic-10-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,138] INFO [Broker id=2] Leader -uve-topic-23-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,141] INFO [Broker id=2] Leader -uve-topic-25-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,145] INFO [Broker id=2] Leader -uve-topic-20-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,149] INFO [Broker id=2] Leader -uve-topic-12-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,171] INFO [Broker id=2] Leader -uve-topic-19-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,175] INFO [Broker id=2] Leader -uve-topic-29-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,180] INFO [Broker id=2] Leader -uve-topic-16-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,188] INFO [Broker id=2] Leader -uve-topic-8-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,192] INFO [Broker id=2] Leader -uve-topic-21-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,199] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,203] INFO [Broker id=2] Leader -uve-topic-2-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,208] INFO [Broker id=2] Leader -uve-topic-9-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,212] INFO [Broker id=2] Leader -uve-topic-18-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,217] INFO [Broker id=2] Leader -uve-topic-10-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,223] INFO [Broker id=2] Leader -uve-topic-23-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,228] INFO [Broker id=2] Leader -uve-topic-14-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,232] INFO [Broker id=2] Leader -uve-topic-27-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,237] INFO [Broker id=2] Leader -uve-topic-7-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,240] INFO [Broker id=2] Leader -uve-topic-6-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,246] INFO [Broker id=2] Leader -uve-topic-8-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,255] INFO [Broker id=2] Leader -uve-topic-21-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,262] INFO [Broker id=2] Leader -uve-topic-20-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,266] INFO [Broker id=2] Leader -uve-topic-0-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,271] INFO [Broker id=2] Leader -uve-topic-17-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,275] INFO [Broker id=2] Leader -uve-topic-29-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,279] INFO [Broker id=2] Leader -uve-topic-16-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,282] INFO [Broker id=2] Leader -uve-topic-4-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,285] INFO [Broker id=2] Leader -uve-topic-13-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,288] INFO [Broker id=2] Leader -uve-topic-26-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,303] INFO [Broker id=2] Leader -uve-topic-6-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,316] INFO [Broker id=2] Leader -uve-topic-5-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,323] INFO [Broker id=2] Leader -uve-topic-12-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,329] INFO [Broker id=2] Leader -uve-topic-26-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,334] INFO [Broker id=2] Leader -uve-topic-25-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,352] INFO [Broker id=2] Leader -uve-topic-29-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,356] INFO [Broker id=2] Leader -uve-topic-16-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,370] INFO [Broker id=2] Leader -uve-topic-10-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,380] INFO [Broker id=2] Leader -uve-topic-23-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,385] INFO [Broker id=2] Leader -uve-topic-19-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,391] INFO [Broker id=2] Leader -uve-topic-25-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,396] INFO [Broker id=2] Leader -uve-topic-11-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,401] INFO [Broker id=2] Leader -uve-topic-24-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,405] INFO [Broker id=2] Leader -uve-topic-19-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,410] INFO [Broker id=2] Leader -uve-topic-28-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,414] INFO [Broker id=2] Leader -uve-topic-15-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,422] INFO [Broker id=2] Leader -uve-topic-20-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,427] INFO [Broker id=2] Leader -uve-topic-29-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,430] INFO [Broker id=2] Leader -uve-topic-16-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,437] INFO [Broker id=2] Leader -uve-topic-7-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,446] INFO [Broker id=2] Leader -uve-topic-8-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,456] INFO [Broker id=2] Leader -uve-topic-22-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,463] INFO [Broker id=2] Leader -uve-topic-18-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,472] INFO [Broker id=2] Leader -uve-topic-24-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,483] INFO [Broker id=2] Leader -uve-topic-11-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,488] INFO [Broker id=2] Leader -uve-topic-17-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,494] INFO [Broker id=2] Leader -uve-topic-22-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,499] INFO [Broker id=2] Leader -uve-topic-1-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,503] INFO [Broker id=2] Leader structured_syslog_topic-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,507] INFO [Broker id=2] Leader -uve-topic-5-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,511] INFO [Broker id=2] Leader -uve-topic-15-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,515] INFO [Broker id=2] Leader -uve-topic-28-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,520] INFO [Broker id=2] Leader -uve-topic-20-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,536] INFO [Broker id=2] Leader -uve-topic-21-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,543] INFO [Broker id=2] Leader -uve-topic-7-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,549] INFO [Broker id=2] Leader -uve-topic-3-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,593] INFO [Broker id=2] Leader -uve-topic-8-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,605] INFO [Broker id=2] Leader -uve-topic-21-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,609] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,613] INFO [Broker id=2] Leader -uve-topic-0-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,617] INFO [Broker id=2] Leader -uve-topic-24-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,621] INFO [Broker id=2] Leader -uve-topic-23-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,624] INFO [Broker id=2] Leader -uve-topic-11-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,628] INFO [Broker id=2] Leader -uve-topic-10-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,634] INFO [Broker id=2] Leader -uve-topic-19-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,641] INFO [Broker id=2] Leader -uve-topic-20-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,646] INFO [Broker id=2] Leader -uve-topic-3-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,650] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,654] INFO [Broker id=2] Leader -uve-topic-7-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,657] INFO [Broker id=2] Leader -uve-topic-17-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,661] INFO [Broker id=2] Leader -uve-topic-16-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,665] INFO [Broker id=2] Leader -uve-topic-29-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,669] INFO [Broker id=2] Leader -uve-topic-0-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,674] INFO [Broker id=2] Leader structured_syslog_topic-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,680] INFO [Broker id=2] Leader -uve-topic-9-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,688] INFO [Broker id=2] Leader -uve-topic-6-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,693] INFO [Broker id=2] Leader -uve-topic-26-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,698] INFO [Broker id=2] Leader -uve-topic-13-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,702] INFO [Broker id=2] Leader -uve-topic-5-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,706] INFO [Broker id=2] Leader -uve-topic-7-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,710] INFO [Broker id=2] Leader -uve-topic-8-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,720] INFO [Broker id=2] Leader -uve-topic-19-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,724] INFO [Broker id=2] Leader -uve-topic-4-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,729] INFO [Broker id=2] Leader -uve-topic-25-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,739] INFO [Broker id=2] Leader -uve-topic-20-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,742] INFO [Broker id=2] Leader -uve-topic-12-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,746] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,750] INFO [Broker id=2] Leader -uve-topic-16-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,754] INFO [Broker id=2] Leader -uve-topic-29-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,758] INFO [Broker id=2] Leader -uve-topic-8-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,762] INFO [Broker id=2] Leader -uve-topic-18-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,768] INFO [Broker id=2] Leader -uve-topic-1-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,772] INFO [Broker id=2] Leader -uve-topic-22-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,776] INFO [Broker id=2] Leader -uve-topic-23-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,780] INFO [Broker id=2] Leader -uve-topic-10-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,785] INFO [Broker id=2] Leader -uve-topic-2-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,788] INFO [Broker id=2] Leader -uve-topic-18-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,791] INFO [Broker id=2] Leader -uve-topic-27-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,794] INFO [Broker id=2] Leader -uve-topic-14-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,798] INFO [Broker id=2] Leader -uve-topic-15-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,801] INFO [Broker id=2] Leader -uve-topic-28-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,811] INFO [Broker id=2] Leader -uve-topic-28-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,815] INFO [Broker id=2] Leader -uve-topic-27-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,819] INFO [Broker id=2] Leader -uve-topic-14-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,824] INFO [Broker id=2] Leader -uve-topic-8-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,830] INFO [Broker id=2] Leader -uve-topic-22-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,834] INFO [Broker id=2] Leader -uve-topic-16-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,840] INFO [Broker id=2] Leader -uve-topic-15-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,845] INFO [Broker id=2] Leader -uve-topic-29-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,848] INFO [Broker id=2] Leader -uve-topic-28-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,852] INFO [Broker id=2] Leader -uve-topic-21-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,855] INFO [Broker id=2] Leader -uve-topic-17-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,858] INFO [Broker id=2] Leader -uve-topic-20-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,863] INFO [Broker id=2] Leader -uve-topic-21-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,867] INFO [Broker id=2] Leader structured_syslog_topic-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,870] INFO [Broker id=2] Leader -uve-topic-25-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,875] INFO [Broker id=2] Leader -uve-topic-12-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,880] INFO [Broker id=2] Leader -uve-topic-24-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,883] INFO [Broker id=2] Leader -uve-topic-11-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,886] INFO [Broker id=2] Leader -uve-topic-26-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,890] INFO [Broker id=2] Leader -uve-topic-13-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,897] INFO [Broker id=2] Leader -uve-topic-15-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,901] INFO [Broker id=2] Leader -uve-topic-28-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,904] INFO [Broker id=2] Leader -uve-topic-20-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,907] INFO [Broker id=2] Leader -uve-topic-7-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,911] INFO [Broker id=2] Leader -uve-topic-3-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,916] INFO [Broker id=2] Leader -uve-topic-19-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,920] INFO [Broker id=2] Leader -uve-topic-23-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,923] INFO [Broker id=2] Leader -uve-topic-10-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,928] INFO [Broker id=2] Leader -uve-topic-25-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,931] INFO [Broker id=2] Leader -uve-topic-12-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,935] INFO [Broker id=2] Leader -uve-topic-24-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,939] INFO [Broker id=2] Leader -uve-topic-11-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,942] INFO [Broker id=2] Leader -uve-topic-15-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,945] INFO [Broker id=2] Leader -uve-topic-28-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,949] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,952] INFO [Broker id=2] Leader -uve-topic-20-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,956] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,960] INFO [Broker id=2] Leader -uve-topic-6-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,964] INFO [Broker id=2] Leader -uve-topic-9-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,969] INFO [Broker id=2] Leader -uve-topic-19-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,974] INFO [Broker id=2] Leader -uve-topic-18-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,977] INFO [Broker id=2] Leader -uve-topic-22-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,982] INFO [Broker id=2] Leader -uve-topic-10-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,987] INFO [Broker id=2] Leader -uve-topic-23-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,995] INFO [Broker id=2] Leader -uve-topic-18-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:17,999] INFO [Broker id=2] Leader -uve-topic-17-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,003] INFO [Broker id=2] Leader -uve-topic-22-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,007] INFO [Broker id=2] Leader -uve-topic-14-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,011] INFO [Broker id=2] Leader -uve-topic-27-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,015] INFO [Broker id=2] Leader -uve-topic-5-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,018] INFO [Broker id=2] Leader -uve-topic-21-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,024] INFO [Broker id=2] Leader -uve-topic-28-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,027] INFO [Broker id=2] Leader -uve-topic-15-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,031] INFO [Broker id=2] Leader -uve-topic-16-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,035] INFO [Broker id=2] Leader -uve-topic-17-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,039] INFO [Broker id=2] Leader -uve-topic-13-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,042] INFO [Broker id=2] Leader -uve-topic-12-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,045] INFO [Broker id=2] Leader -uve-topic-25-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,048] INFO [Broker id=2] Leader -uve-topic-26-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,051] INFO [Broker id=2] Leader -uve-topic-14-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,056] INFO [Broker id=2] Leader -uve-topic-27-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,059] INFO [Broker id=2] Leader -uve-topic-7-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,066] INFO [Broker id=2] Leader -uve-topic-2-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,070] INFO [Broker id=2] Leader -uve-topic-14-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,073] INFO [Broker id=2] Leader -uve-topic-27-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,078] INFO [Broker id=2] Leader -uve-topic-28-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,082] INFO [Broker id=2] Leader -uve-topic-15-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,085] INFO [Broker id=2] Leader -uve-topic-7-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,089] INFO [Broker id=2] Leader -uve-topic-0-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,094] INFO [Broker id=2] Leader -uve-topic-1-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,098] INFO [Broker id=2] Leader -uve-topic-2-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,102] INFO [Broker id=2] Leader -uve-topic-9-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,106] INFO [Broker id=2] Leader -uve-topic-8-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,109] INFO [Broker id=2] Leader structured_syslog_topic-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,113] INFO [Broker id=2] Leader -uve-topic-1-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,116] INFO [Broker id=2] Leader -uve-topic-0-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,122] INFO [Broker id=2] Leader structured_syslog_topic-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,126] INFO [Broker id=2] Leader -uve-topic-4-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,130] INFO [Broker id=2] Leader -uve-topic-13-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,134] INFO [Broker id=2] Leader -uve-topic-26-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,138] INFO [Broker id=2] Leader -uve-topic-6-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,142] INFO [Broker id=2] Leader -uve-topic-8-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,146] INFO [Broker id=2] Leader -uve-topic-7-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,152] INFO [Broker id=2] Leader -uve-topic-20-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,156] INFO [Broker id=2] Leader -uve-topic-11-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,159] INFO [Broker id=2] Leader -uve-topic-24-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,163] INFO [Broker id=2] Leader -uve-topic-29-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,166] INFO [Broker id=2] Leader -uve-topic-16-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,170] INFO [Broker id=2] Leader -uve-topic-3-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,173] INFO [Broker id=2] Leader -uve-topic-11-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,176] INFO [Broker id=2] Leader -uve-topic-4-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,179] INFO [Broker id=2] Leader -uve-topic-5-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,182] INFO [Broker id=2] Leader -uve-topic-6-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,185] INFO [Broker id=2] Leader -uve-topic-2-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,189] INFO [Broker id=2] Leader -uve-topic-1-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,192] INFO [Broker id=2] Leader -uve-topic-18-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,198] INFO [Broker id=2] Leader structured_syslog_topic-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,201] INFO [Broker id=2] Leader -uve-topic-3-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,204] INFO [Broker id=2] Leader -uve-topic-2-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,208] INFO [Broker id=2] Leader -uve-topic-14-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,213] INFO [Broker id=2] Leader -uve-topic-27-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,217] INFO [Broker id=2] Leader -uve-topic-28-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,221] INFO [Broker id=2] Leader -uve-topic-15-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,225] INFO [Broker id=2] Leader -uve-topic-8-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,230] INFO [Broker id=2] Leader -uve-topic-1-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,233] INFO [Broker id=2] Leader -uve-topic-0-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,236] INFO [Broker id=2] Leader -uve-topic-20-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,240] INFO [Broker id=2] Leader structured_syslog_topic-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,243] INFO [Broker id=2] Leader -uve-topic-9-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,246] INFO [Broker id=2] Leader -uve-topic-22-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,250] INFO [Broker id=2] Leader -uve-topic-13-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,253] INFO [Broker id=2] Leader -uve-topic-12-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,256] INFO [Broker id=2] Leader -uve-topic-25-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,259] INFO [Broker id=2] Leader -uve-topic-26-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,262] INFO [Broker id=2] Leader -uve-topic-5-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,265] INFO [Broker id=2] Leader -uve-topic-12-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,268] INFO [Broker id=2] Leader -uve-topic-25-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,271] INFO [Broker id=2] Leader -uve-topic-13-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,274] INFO [Broker id=2] Leader -uve-topic-26-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,280] INFO [Broker id=2] Leader -uve-topic-7-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,285] INFO [Broker id=2] Leader -uve-topic-6-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,290] INFO [Broker id=2] Leader -uve-topic-28-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,296] INFO [Broker id=2] Leader -uve-topic-15-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,300] INFO [Broker id=2] Leader -uve-topic-7-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,303] INFO [Broker id=2] Leader -uve-topic-19-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,308] INFO [Broker id=2] Leader -uve-topic-10-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,312] INFO [Broker id=2] Leader -uve-topic-11-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,315] INFO [Broker id=2] Leader -uve-topic-24-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,319] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,322] INFO [Broker id=2] Leader -uve-topic-19-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,325] INFO [Broker id=2] Leader structured_syslog_topic-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,328] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,331] INFO [Broker id=2] Leader -uve-topic-14-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,334] INFO [Broker id=2] Leader -uve-topic-27-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,337] INFO [Broker id=2] Leader -uve-topic-10-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,340] INFO [Broker id=2] Leader -uve-topic-23-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,343] INFO [Broker id=2] Leader -uve-topic-17-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,346] INFO [Broker id=2] Leader -uve-topic-9-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,349] INFO [Broker id=2] Leader -uve-topic-14-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,352] INFO [Broker id=2] Leader -uve-topic-27-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,355] INFO [Broker id=2] Leader -uve-topic-6-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,359] INFO [Broker id=2] Leader -uve-topic-29-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,363] INFO [Broker id=2] Leader -uve-topic-16-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,366] INFO [Broker id=2] Leader -uve-topic-21-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,369] INFO [Broker id=2] Leader -uve-topic-0-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,372] INFO [Broker id=2] Leader -uve-topic-4-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,375] INFO [Broker id=2] Leader -uve-topic-8-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,380] INFO [Broker id=2] Leader -uve-topic-28-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,383] INFO [Broker id=2] Leader -uve-topic-14-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,387] INFO [Broker id=2] Leader -uve-topic-27-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,390] INFO [Broker id=2] Leader -uve-topic-29-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,393] INFO [Broker id=2] Leader -uve-topic-16-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,396] INFO [Broker id=2] Leader -uve-topic-10-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,399] INFO [Broker id=2] Leader -uve-topic-23-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,403] INFO [Broker id=2] Leader -uve-topic-12-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,407] INFO [Broker id=2] Leader -uve-topic-25-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,413] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,417] INFO [Broker id=2] Leader -uve-topic-27-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,421] INFO [Broker id=2] Leader -uve-topic-13-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,423] INFO [Broker id=2] Leader -uve-topic-26-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,427] INFO [Broker id=2] Leader -uve-topic-18-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,431] INFO [Broker id=2] Leader -uve-topic-9-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,435] INFO [Broker id=2] Leader -uve-topic-0-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,446] INFO [Broker id=2] Leader -uve-topic-1-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,450] INFO [Broker id=2] Leader -uve-topic-2-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,453] INFO [Broker id=2] Leader structured_syslog_topic-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,457] INFO [Broker id=2] Leader -uve-topic-6-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,460] INFO [Broker id=2] Leader -uve-topic-5-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,463] INFO [Broker id=2] Leader -uve-topic-14-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,466] INFO [Broker id=2] Leader -uve-topic-27-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,470] INFO [Broker id=2] Leader -uve-topic-5-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,473] INFO [Broker id=2] Leader -uve-topic-13-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,476] INFO [Broker id=2] Leader -uve-topic-6-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,479] INFO [Broker id=2] Leader -uve-topic-7-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,482] INFO [Broker id=2] Leader -uve-topic-8-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,485] INFO [Broker id=2] Leader -uve-topic-20-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,488] INFO [Broker id=2] Leader -uve-topic-11-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,490] INFO [Broker id=2] Leader -uve-topic-24-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,494] INFO [Broker id=2] Leader -uve-topic-4-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,497] INFO [Broker id=2] Leader -uve-topic-3-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,500] INFO [Broker id=2] Leader structured_syslog_topic-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,504] INFO [Broker id=2] Leader -uve-topic-5-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,507] INFO [Broker id=2] Leader -uve-topic-7-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,510] INFO [Broker id=2] Leader -uve-topic-13-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,513] INFO [Broker id=2] Leader -uve-topic-26-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,517] INFO [Broker id=2] Leader -uve-topic-6-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,520] INFO [Broker id=2] Leader -uve-topic-3-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,523] INFO [Broker id=2] Leader -uve-topic-2-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,526] INFO [Broker id=2] Leader -uve-topic-22-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,528] INFO [Broker id=2] Leader -uve-topic-19-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,531] INFO [Broker id=2] Leader structured_syslog_topic-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,534] INFO [Broker id=2] Leader -uve-topic-14-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,537] INFO [Broker id=2] Leader -uve-topic-9-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,540] INFO [Broker id=2] Leader -uve-topic-8-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,544] INFO [Broker id=2] Leader -uve-topic-21-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,549] INFO [Broker id=2] Leader -uve-topic-28-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,555] INFO [Broker id=2] Leader -uve-topic-15-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,559] INFO [Broker id=2] Leader -uve-topic-1-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,563] INFO [Broker id=2] Leader -uve-topic-0-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,566] INFO [Broker id=2] Leader -uve-topic-17-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,568] INFO [Broker id=2] Leader structured_syslog_topic-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,571] INFO [Broker id=2] Leader -uve-topic-13-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,577] INFO [Broker id=2] Leader -uve-topic-26-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,580] INFO [Broker id=2] Leader -uve-topic-4-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,584] INFO [Broker id=2] Leader structured_syslog_topic-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,587] INFO [Broker id=2] Leader -uve-topic-28-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,590] INFO [Broker id=2] Leader -uve-topic-15-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,596] INFO [Broker id=2] Leader -uve-topic-0-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,599] INFO [Broker id=2] Leader -uve-topic-7-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,602] INFO [Broker id=2] Leader -uve-topic-20-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,607] INFO [Broker id=2] Leader -uve-topic-28-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,610] INFO [Broker id=2] Leader -uve-topic-15-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,613] INFO [Broker id=2] Leader -uve-topic-12-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,624] INFO [Broker id=2] Leader -uve-topic-25-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,627] INFO [Broker id=2] Leader -uve-topic-3-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,631] INFO [Broker id=2] Leader -uve-topic-19-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,634] INFO [Broker id=2] Leader -uve-topic-4-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,638] INFO [Broker id=2] Leader -uve-topic-11-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,641] INFO [Broker id=2] Leader -uve-topic-24-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,644] INFO [Broker id=2] Leader structured_syslog_topic-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,647] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,654] INFO [Broker id=2] Leader -uve-topic-6-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,659] INFO [Broker id=2] Leader -uve-topic-13-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,663] INFO [Broker id=2] Leader -uve-topic-26-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,666] INFO [Broker id=2] Leader -uve-topic-14-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,669] INFO [Broker id=2] Leader -uve-topic-27-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,672] INFO [Broker id=2] Leader -uve-topic-18-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,676] INFO [Broker id=2] Leader -uve-topic-22-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,679] INFO [Broker id=2] Leader -uve-topic-10-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,682] INFO [Broker id=2] Leader -uve-topic-23-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,687] INFO [Broker id=2] Leader -uve-topic-6-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,691] INFO [Broker id=2] Leader -uve-topic-20-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,695] INFO [Broker id=2] Leader -uve-topic-21-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,698] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,701] INFO [Broker id=2] Leader -uve-topic-16-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,704] INFO [Broker id=2] Leader -uve-topic-29-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,707] INFO [Broker id=2] Leader -uve-topic-21-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,712] INFO [Broker id=2] Leader -uve-topic-4-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,716] INFO [Broker id=2] Leader -uve-topic-27-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,722] INFO [Broker id=2] Leader -uve-topic-14-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,730] INFO [Broker id=2] Leader -uve-topic-16-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,738] INFO [Broker id=2] Leader -uve-topic-29-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,744] INFO [Broker id=2] Leader -uve-topic-2-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,747] INFO [Broker id=2] Leader -uve-topic-2-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,750] INFO [Broker id=2] Leader -uve-topic-1-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,754] INFO [Broker id=2] Leader -uve-topic-3-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,757] INFO [Broker id=2] Leader -uve-topic-26-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,760] INFO [Broker id=2] Leader -uve-topic-13-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,764] INFO [Broker id=2] Leader -uve-topic-5-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,767] INFO [Broker id=2] Leader -uve-topic-9-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,770] INFO [Broker id=2] Leader -uve-topic-17-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,773] INFO [Broker id=2] Leader -uve-topic-1-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,776] INFO [Broker id=2] Leader -uve-topic-8-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,779] INFO [Broker id=2] Leader structured_syslog_topic-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,782] INFO [Broker id=2] Leader -uve-topic-5-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,786] INFO [Broker id=2] Leader -uve-topic-22-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,789] INFO [Broker id=2] Leader -uve-topic-26-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,792] INFO [Broker id=2] Leader -uve-topic-13-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,796] INFO [Broker id=2] Leader -uve-topic-5-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,799] INFO [Broker id=2] Leader -uve-topic-16-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,803] INFO [Broker id=2] Leader -uve-topic-29-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,806] INFO [Broker id=2] Leader -uve-topic-15-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,809] INFO [Broker id=2] Leader -uve-topic-28-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,813] INFO [Broker id=2] Leader -uve-topic-8-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,816] INFO [Broker id=2] Leader -uve-topic-5-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,819] INFO [Broker id=2] Leader -uve-topic-4-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,822] INFO [Broker id=2] Leader -uve-topic-24-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,826] INFO [Broker id=2] Leader -uve-topic-11-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,830] INFO [Broker id=2] Leader -uve-topic-4-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,834] INFO [Broker id=2] Leader structured_syslog_topic-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,837] INFO [Broker id=2] Leader -uve-topic-5-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,841] INFO [Broker id=2] Leader -uve-topic-7-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,844] INFO [Broker id=2] Leader -uve-topic-18-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,848] INFO [Broker id=2] Leader -uve-topic-1-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,851] INFO [Broker id=2] Leader -uve-topic-3-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,856] INFO [Broker id=2] Leader -uve-topic-19-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,862] INFO [Broker id=2] Leader structured_syslog_topic-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,865] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,868] INFO [Broker id=2] Leader -uve-topic-4-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,873] INFO [Broker id=2] Leader -uve-topic-25-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,876] INFO [Broker id=2] Leader -uve-topic-26-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,880] INFO [Broker id=2] Leader -uve-topic-12-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,883] INFO [Broker id=2] Leader -uve-topic-13-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,886] INFO [Broker id=2] Leader -uve-topic-4-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,889] INFO [Broker id=2] Leader -uve-topic-0-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,894] INFO [Broker id=2] Leader -uve-topic-17-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,897] INFO [Broker id=2] Leader -uve-topic-16-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,900] INFO [Broker id=2] Leader -uve-topic-29-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,904] INFO [Broker id=2] Leader -uve-topic-2-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,907] INFO [Broker id=2] Leader -uve-topic-22-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,911] INFO [Broker id=2] Leader -uve-topic-9-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,914] INFO [Broker id=2] Leader -uve-topic-21-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,917] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,921] INFO [Broker id=2] Leader -uve-topic-17-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,925] INFO [Broker id=2] Leader -uve-topic-26-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,929] INFO [Broker id=2] Leader -uve-topic-13-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,934] INFO [Broker id=2] Leader -uve-topic-15-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,937] INFO [Broker id=2] Leader -uve-topic-28-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,945] INFO [Broker id=2] Leader -uve-topic-20-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,951] INFO [Broker id=2] Leader -uve-topic-21-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,954] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,959] INFO [Broker id=2] Leader -uve-topic-27-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,964] INFO [Broker id=2] Leader -uve-topic-14-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,970] INFO [Broker id=2] Leader -uve-topic-25-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,979] INFO [Broker id=2] Leader -uve-topic-19-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,983] INFO [Broker id=2] Leader -uve-topic-20-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,988] INFO [Broker id=2] Leader -uve-topic-10-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,991] INFO [Broker id=2] Leader -uve-topic-24-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,996] INFO [Broker id=2] Leader -uve-topic-23-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:18,999] INFO [Broker id=2] Leader -uve-topic-25-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,005] INFO [Broker id=2] Leader -uve-topic-12-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,008] INFO [Broker id=2] Leader -uve-topic-27-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,012] INFO [Broker id=2] Leader -uve-topic-26-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,016] INFO [Broker id=2] Leader -uve-topic-13-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,020] INFO [Broker id=2] Leader -uve-topic-14-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,023] INFO [Broker id=2] Leader -uve-topic-6-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,027] INFO [Broker id=2] Leader -uve-topic-10-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,031] INFO [Broker id=2] Leader -uve-topic-22-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,035] INFO [Broker id=2] Leader -uve-topic-23-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,038] INFO [Broker id=2] Leader -uve-topic-18-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,042] INFO [Broker id=2] Leader -uve-topic-5-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,046] INFO [Broker id=2] Leader -uve-topic-25-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,049] INFO [Broker id=2] Leader -uve-topic-12-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,052] INFO [Broker id=2] Leader -uve-topic-18-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,060] INFO [Broker id=2] Leader -uve-topic-17-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,068] INFO [Broker id=2] Leader -uve-topic-20-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,071] INFO [Broker id=2] Leader -uve-topic-21-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,075] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,078] INFO [Broker id=2] Leader -uve-topic-22-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,081] INFO [Broker id=2] Leader -uve-topic-17-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,084] INFO [Broker id=2] Leader -uve-topic-16-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,090] INFO [Broker id=2] Leader -uve-topic-29-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,094] INFO [Broker id=2] Leader -uve-topic-21-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,098] INFO [Broker id=2] Leader structured_syslog_topic-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,102] INFO [Broker id=2] Leader -uve-topic-20-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,110] INFO [Broker id=2] Leader -uve-topic-27-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,114] INFO [Broker id=2] Leader -uve-topic-14-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,118] INFO [Broker id=2] Leader -uve-topic-16-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,121] INFO [Broker id=2] Leader -uve-topic-15-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,124] INFO [Broker id=2] Leader -uve-topic-29-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,129] INFO [Broker id=2] Leader -uve-topic-28-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,133] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,137] INFO [Broker id=2] Leader -uve-topic-25-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,140] INFO [Broker id=2] Leader -uve-topic-12-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,144] INFO [Broker id=2] Leader -uve-topic-24-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,149] INFO [Broker id=2] Leader -uve-topic-11-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,152] INFO [Broker id=2] Leader -uve-topic-26-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,155] INFO [Broker id=2] Leader -uve-topic-13-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,159] INFO [Broker id=2] Leader -uve-topic-12-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,162] INFO [Broker id=2] Leader -uve-topic-13-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,166] INFO [Broker id=2] Leader -uve-topic-5-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,172] INFO [Broker id=2] Leader -uve-topic-6-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,175] INFO [Broker id=2] Leader -uve-topic-9-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,178] INFO [Broker id=2] Leader -uve-topic-1-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,182] INFO [Broker id=2] Leader -uve-topic-8-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,186] INFO [Broker id=2] Leader -uve-topic-15-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,190] INFO [Broker id=2] Leader -uve-topic-28-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,193] INFO [Broker id=2] Leader -uve-topic-0-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,198] INFO [Broker id=2] Leader -uve-topic-7-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,203] INFO [Broker id=2] Leader -uve-topic-4-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,206] INFO [Broker id=2] Leader -uve-topic-3-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,209] INFO [Broker id=2] Leader -uve-topic-25-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,212] INFO [Broker id=2] Leader -uve-topic-12-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,216] INFO [Broker id=2] Leader -uve-topic-19-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,220] INFO [Broker id=2] Leader structured_syslog_topic-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,223] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,226] INFO [Broker id=2] Leader -uve-topic-7-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,230] INFO [Broker id=2] Leader -uve-topic-6-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,234] INFO [Broker id=2] Leader -uve-topic-10-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,237] INFO [Broker id=2] Leader -uve-topic-27-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,241] INFO [Broker id=2] Leader -uve-topic-23-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,244] INFO [Broker id=2] Leader -uve-topic-14-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,247] INFO [Broker id=2] Leader -uve-topic-2-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,250] INFO [Broker id=2] Leader -uve-topic-18-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,253] INFO [Broker id=2] Leader -uve-topic-19-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,257] INFO [Broker id=2] Leader -uve-topic-22-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,260] INFO [Broker id=2] Leader -uve-topic-24-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,264] INFO [Broker id=2] Leader -uve-topic-11-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,266] INFO [Broker id=2] Leader -uve-topic-10-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,270] INFO [Broker id=2] Leader -uve-topic-23-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,273] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,277] INFO [Broker id=2] Leader -uve-topic-4-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,280] INFO [Broker id=2] Leader -uve-topic-25-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,284] INFO [Broker id=2] Leader -uve-topic-12-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,287] INFO [Broker id=2] Leader -uve-topic-5-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,290] INFO [Broker id=2] Leader -uve-topic-4-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,293] INFO [Broker id=2] Leader -uve-topic-17-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,297] INFO [Broker id=2] Leader -uve-topic-0-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,301] INFO [Broker id=2] Leader -uve-topic-1-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,304] INFO [Broker id=2] Leader -uve-topic-16-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,307] INFO [Broker id=2] Leader -uve-topic-2-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,310] INFO [Broker id=2] Leader -uve-topic-9-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,313] INFO [Broker id=2] Leader -uve-topic-25-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,316] INFO [Broker id=2] Leader -uve-topic-12-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,319] INFO [Broker id=2] Leader -uve-topic-4-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,322] INFO [Broker id=2] Leader -uve-topic-3-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,326] INFO [Broker id=2] Leader -uve-topic-3-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,331] INFO [Broker id=2] Leader -uve-topic-0-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,334] INFO [Broker id=2] Leader -uve-topic-15-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,338] INFO [Broker id=2] Leader -uve-topic-6-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,341] INFO [Broker id=2] Leader -uve-topic-7-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,345] INFO [Broker id=2] Leader -uve-topic-8-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,348] INFO [Broker id=2] Leader -uve-topic-21-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,351] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,354] INFO [Broker id=2] Leader -uve-topic-25-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,357] INFO [Broker id=2] Leader -uve-topic-12-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,362] INFO [Broker id=2] Leader -uve-topic-19-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,365] INFO [Broker id=2] Leader -uve-topic-24-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,368] INFO [Broker id=2] Leader -uve-topic-11-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,371] INFO [Broker id=2] Leader -uve-topic-4-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,375] INFO [Broker id=2] Leader -uve-topic-24-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,380] INFO [Broker id=2] Leader -uve-topic-11-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,389] INFO [Broker id=2] Leader -uve-topic-5-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,393] INFO [Broker id=2] Leader -uve-topic-6-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,396] INFO [Broker id=2] Leader -uve-topic-27-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,400] INFO [Broker id=2] Leader -uve-topic-14-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,403] INFO [Broker id=2] Leader -uve-topic-18-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,406] INFO [Broker id=2] Leader -uve-topic-19-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,409] INFO [Broker id=2] Leader -uve-topic-10-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,413] INFO [Broker id=2] Leader -uve-topic-22-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,416] INFO [Broker id=2] Leader -uve-topic-23-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,419] INFO [Broker id=2] Leader -uve-topic-18-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,423] INFO [Broker id=2] Leader -uve-topic-24-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,427] INFO [Broker id=2] Leader -uve-topic-11-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,431] INFO [Broker id=2] Leader -uve-topic-26-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,434] INFO [Broker id=2] Leader -uve-topic-13-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,437] INFO [Broker id=2] Leader -uve-topic-25-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,440] INFO [Broker id=2] Leader -uve-topic-20-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,444] INFO [Broker id=2] Leader -uve-topic-12-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,447] INFO [Broker id=2] Leader -uve-topic-22-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,451] INFO [Broker id=2] Leader -uve-topic-16-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,454] INFO [Broker id=2] Leader -uve-topic-29-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,458] INFO [Broker id=2] Leader -uve-topic-21-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,461] INFO [Broker id=2] Leader -uve-topic-8-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,465] INFO [Broker id=2] Leader -uve-topic-17-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,469] INFO [Broker id=2] Leader -uve-topic-15-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,473] INFO [Broker id=2] Leader -uve-topic-28-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,477] INFO [Broker id=2] Leader -uve-topic-7-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,480] INFO [Broker id=2] Leader -uve-topic-10-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,484] INFO [Broker id=2] Leader -uve-topic-23-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,487] INFO [Broker id=2] Leader -uve-topic-1-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,490] INFO [Broker id=2] Leader -uve-topic-3-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,494] INFO [Broker id=2] Leader structured_syslog_topic-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,497] INFO [Broker id=2] Leader -uve-topic-5-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,500] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,504] INFO [Broker id=2] Leader -uve-topic-4-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,509] INFO [Broker id=2] Leader -uve-topic-9-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,512] INFO [Broker id=2] Leader -uve-topic-9-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,515] INFO [Broker id=2] Leader -uve-topic-19-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,519] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,521] INFO [Broker id=2] Leader -uve-topic-17-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,525] INFO [Broker id=2] Leader -uve-topic-8-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,531] INFO [Broker id=2] Leader -uve-topic-1-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,534] INFO [Broker id=2] Leader -uve-topic-0-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,538] INFO [Broker id=2] Leader -uve-topic-24-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,541] INFO [Broker id=2] Leader -uve-topic-5-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,544] INFO [Broker id=2] Leader -uve-topic-7-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,547] INFO [Broker id=2] Leader -uve-topic-6-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,554] INFO [Broker id=2] Leader -uve-topic-23-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,557] INFO [Broker id=2] Leader -uve-topic-10-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,560] INFO [Broker id=2] Leader -uve-topic-3-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,563] INFO [Broker id=2] Leader -uve-topic-2-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,567] INFO [Broker id=2] Leader -uve-topic-18-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,571] INFO [Broker id=2] Leader -uve-topic-19-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,574] INFO [Broker id=2] Leader -uve-topic-4-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,577] INFO [Broker id=2] Leader -uve-topic-5-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,581] INFO [Broker id=2] Leader -uve-topic-6-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,584] INFO [Broker id=2] Leader -uve-topic-25-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,587] INFO [Broker id=2] Leader -uve-topic-12-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,590] INFO [Broker id=2] Leader -uve-topic-0-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,593] INFO [Broker id=2] Leader -uve-topic-4-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,596] INFO [Broker id=2] Leader -uve-topic-2-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,599] INFO [Broker id=2] Leader -uve-topic-18-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,602] INFO [Broker id=2] Leader -uve-topic-1-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,605] INFO [Broker id=2] Leader -uve-topic-9-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,609] INFO [Broker id=2] Leader -uve-topic-21-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,612] INFO [Broker id=2] Leader -uve-topic-3-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,616] INFO [Broker id=2] Leader -uve-topic-23-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,621] INFO [Broker id=2] Leader -uve-topic-24-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,625] INFO [Broker id=2] Leader -uve-topic-11-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,628] INFO [Broker id=2] Leader -uve-topic-15-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,635] INFO [Broker id=2] Leader -uve-topic-3-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,640] INFO [Broker id=2] Leader -uve-topic-28-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,644] INFO [Broker id=2] Leader -uve-topic-8-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,649] INFO [Broker id=2] Leader -uve-topic-20-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,652] INFO [Broker id=2] Leader -uve-topic-7-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,655] INFO [Broker id=2] Leader -uve-topic-27-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,662] INFO [Broker id=2] Leader -uve-topic-14-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,666] INFO [Broker id=2] Leader -uve-topic-16-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,669] INFO [Broker id=2] Leader -uve-topic-29-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,672] INFO [Broker id=2] Leader -uve-topic-24-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,675] INFO [Broker id=2] Leader -uve-topic-11-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,679] INFO [Broker id=2] Leader -uve-topic-19-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,682] INFO [Broker id=2] Leader -uve-topic-24-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,686] INFO [Broker id=2] Leader -uve-topic-11-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,689] INFO [Broker id=2] Leader -uve-topic-3-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,692] INFO [Broker id=2] Leader structured_syslog_topic-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,696] INFO [Broker id=2] Leader -uve-topic-26-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,700] INFO [Broker id=2] Leader -uve-topic-13-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,704] INFO [Broker id=2] Leader -uve-topic-22-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,708] INFO [Broker id=2] Leader -uve-topic-10-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,712] INFO [Broker id=2] Leader structured_syslog_topic-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,715] INFO [Broker id=2] Leader -uve-topic-5-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,718] INFO [Broker id=2] Leader -uve-topic-25-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,722] INFO [Broker id=2] Leader -uve-topic-12-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,725] INFO [Broker id=2] Leader -uve-topic-24-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,742] INFO [Broker id=2] Leader -uve-topic-11-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,745] INFO [Broker id=2] Leader -uve-topic-26-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,748] INFO [Broker id=2] Leader -uve-topic-13-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,752] INFO [Broker id=2] Leader -uve-topic-17-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,755] INFO [Broker id=2] Leader -uve-topic-20-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,759] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,763] INFO [Broker id=2] Leader -uve-topic-22-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,766] INFO [Broker id=2] Leader -uve-topic-9-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,770] INFO [Broker id=2] Leader -uve-topic-19-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,773] INFO [Broker id=2] Leader -uve-topic-18-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,776] INFO [Broker id=2] Leader -uve-topic-24-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,780] INFO [Broker id=2] Leader -uve-topic-23-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,784] INFO [Broker id=2] Leader -uve-topic-11-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,787] INFO [Broker id=2] Leader -uve-topic-10-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,789] INFO [Broker id=2] Leader -uve-topic-3-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,792] INFO [Broker id=2] Leader -uve-topic-19-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,796] INFO [Broker id=2] Leader -uve-topic-23-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,799] INFO [Broker id=2] Leader -uve-topic-10-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,802] INFO [Broker id=2] Leader -uve-topic-15-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,804] INFO [Broker id=2] Leader -uve-topic-28-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,808] INFO [Broker id=2] Leader -uve-topic-21-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,811] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,814] INFO [Broker id=2] Leader -uve-topic-6-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,817] INFO [Broker id=2] Leader -uve-topic-19-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,820] INFO [Broker id=2] Leader -uve-topic-3-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,822] INFO [Broker id=2] Leader -uve-topic-26-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,825] INFO [Broker id=2] Leader -uve-topic-1-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,828] INFO [Broker id=2] Leader -uve-topic-9-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,832] INFO [Broker id=2] Leader -uve-topic-0-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,835] INFO [Broker id=2] Leader -uve-topic-1-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,839] INFO [Broker id=2] Leader -uve-topic-2-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,844] INFO [Broker id=2] Leader -uve-topic-25-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,850] INFO [Broker id=2] Leader -uve-topic-12-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,855] INFO [Broker id=2] Leader -uve-topic-4-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,858] INFO [Broker id=2] Leader -uve-topic-8-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,862] INFO [Broker id=2] Leader -uve-topic-0-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,865] INFO [Broker id=2] Leader -uve-topic-16-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,867] INFO [Broker id=2] Leader -uve-topic-29-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,870] INFO [Broker id=2] Leader -uve-topic-7-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,874] INFO [Broker id=2] Leader -uve-topic-8-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,877] INFO [Broker id=2] Leader -uve-topic-2-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,880] INFO [Broker id=2] Leader -uve-topic-27-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,883] INFO [Broker id=2] Leader -uve-topic-6-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,886] INFO [Broker id=2] Leader -uve-topic-7-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,889] INFO [Broker id=2] Leader -uve-topic-27-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,891] INFO [Broker id=2] Leader -uve-topic-14-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,895] INFO [Broker id=2] Leader -uve-topic-2-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,898] INFO [Broker id=2] Leader -uve-topic-24-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,900] INFO [Broker id=2] Leader -uve-topic-11-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,903] INFO [Broker id=2] Leader -uve-topic-18-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,906] INFO [Broker id=2] Leader -uve-topic-3-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,909] INFO [Broker id=2] Leader -uve-topic-23-15 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,913] INFO [Broker id=2] Leader -uve-topic-10-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,916] INFO [Broker id=2] Leader -uve-topic-4-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,918] INFO [Broker id=2] Leader -uve-topic-1-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,921] INFO [Broker id=2] Leader -uve-topic-6-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,924] INFO [Broker id=2] Leader -uve-topic-0-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,927] INFO [Broker id=2] Leader -uve-topic-9-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,930] INFO [Broker id=2] Leader -uve-topic-16-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,933] INFO [Broker id=2] Leader -uve-topic-29-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,935] INFO [Broker id=2] Leader -uve-topic-2-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,938] INFO [Broker id=2] Leader -uve-topic-1-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,941] INFO [Broker id=2] Leader -uve-topic-18-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,944] INFO [Broker id=2] Leader -uve-topic-3-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,947] INFO [Broker id=2] Leader -uve-topic-19-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,950] INFO [Broker id=2] Leader -uve-topic-25-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,953] INFO [Broker id=2] Leader -uve-topic-12-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,955] INFO [Broker id=2] Leader -uve-topic-24-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,958] INFO [Broker id=2] Leader -uve-topic-11-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,961] INFO [Broker id=2] Leader -uve-topic-15-10 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,963] INFO [Broker id=2] Leader -uve-topic-29-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,966] INFO [Broker id=2] Leader -uve-topic-28-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,968] INFO [Broker id=2] Leader -uve-topic-8-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,971] INFO [Broker id=2] Leader -uve-topic-20-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,975] INFO [Broker id=2] Leader -uve-topic-21-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,977] INFO [Broker id=2] Leader -uve-topic-18-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,981] INFO [Broker id=2] Leader structured_syslog_topic-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,984] INFO [Broker id=2] Leader -uve-topic-5-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,987] INFO [Broker id=2] Leader -uve-topic-27-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,991] INFO [Broker id=2] Leader -uve-topic-14-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,995] INFO [Broker id=2] Leader -uve-topic-7-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:19,998] INFO [Broker id=2] Leader -uve-topic-20-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,001] INFO [Broker id=2] Leader -uve-topic-27-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,004] INFO [Broker id=2] Leader -uve-topic-26-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,007] INFO [Broker id=2] Leader -uve-topic-13-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,010] INFO [Broker id=2] Leader -uve-topic-14-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,013] INFO [Broker id=2] Leader -uve-topic-23-12 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,016] INFO [Broker id=2] Leader -uve-topic-10-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,019] INFO [Broker id=2] Leader -uve-topic-19-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,022] INFO [Broker id=2] Leader -uve-topic-22-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,026] INFO [Broker id=2] Leader structured_syslog_topic-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,029] INFO [Broker id=2] Leader -uve-topic-24-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,035] INFO [Broker id=2] Leader -uve-topic-11-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,038] INFO [Broker id=2] Leader -uve-topic-26-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,042] INFO [Broker id=2] Leader -uve-topic-25-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,045] INFO [Broker id=2] Leader -uve-topic-12-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,051] INFO [Broker id=2] Leader -uve-topic-13-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,054] INFO [Broker id=2] Leader -uve-topic-21-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,057] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,061] INFO [Broker id=2] Leader -uve-topic-17-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,065] INFO [Broker id=2] Leader -uve-topic-9-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,069] INFO [Broker id=2] Leader -uve-topic-23-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,072] INFO [Broker id=2] Leader -uve-topic-0-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,075] INFO [Broker id=2] Leader -uve-topic-10-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,078] INFO [Broker id=2] Leader -uve-topic-18-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,081] INFO [Broker id=2] Leader -uve-topic-19-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,084] INFO [Broker id=2] Leader -uve-topic-23-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,089] INFO [Broker id=2] Leader -uve-topic-10-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,092] INFO [Broker id=2] Leader -uve-topic-2-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,097] INFO [Broker id=2] Leader -uve-topic-28-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,102] INFO [Broker id=2] Leader -uve-topic-15-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,106] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,109] INFO [Broker id=2] Leader -uve-topic-2-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,112] INFO [Broker id=2] Leader -uve-topic-13-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,116] INFO [Broker id=2] Leader -uve-topic-26-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,119] INFO [Broker id=2] Leader -uve-topic-12-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,122] INFO [Broker id=2] Leader -uve-topic-25-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,130] INFO [Broker id=2] Leader -uve-topic-14-6 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,137] INFO [Broker id=2] Leader -uve-topic-27-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,141] INFO [Broker id=2] Leader -uve-topic-10-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,145] INFO [Broker id=2] Leader -uve-topic-23-9 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,148] INFO [Broker id=2] Leader -uve-topic-12-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,151] INFO [Broker id=2] Leader -uve-topic-25-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,155] INFO [Broker id=2] Leader -uve-topic-11-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,158] INFO [Broker id=2] Leader -uve-topic-24-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,162] INFO [Broker id=2] Leader -uve-topic-4-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,165] INFO [Broker id=2] Leader -uve-topic-8-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,172] INFO [Broker id=2] Leader -uve-topic-0-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,175] INFO [Broker id=2] Leader -uve-topic-18-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,179] INFO [Broker id=2] Leader -uve-topic-2-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,182] INFO [Broker id=2] Leader -uve-topic-1-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,186] INFO [Broker id=2] Leader structured_syslog_topic-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,189] INFO [Broker id=2] Leader -uve-topic-7-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,194] INFO [Broker id=2] Leader -uve-topic-14-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,197] INFO [Broker id=2] Leader -uve-topic-27-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,201] INFO [Broker id=2] Leader -uve-topic-6-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,206] INFO [Broker id=2] Leader -uve-topic-2-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,209] INFO [Broker id=2] Leader -uve-topic-18-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,213] INFO [Broker id=2] Leader -uve-topic-5-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,217] INFO [Broker id=2] Leader -uve-topic-9-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,220] INFO [Broker id=2] Leader -uve-topic-22-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,223] INFO [Broker id=2] Leader -uve-topic-13-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,227] INFO [Broker id=2] Leader -uve-topic-26-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,230] INFO [Broker id=2] Leader -uve-topic-1-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,233] INFO [Broker id=2] Leader -uve-topic-17-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,236] INFO [Broker id=2] Leader -uve-topic-18-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,239] INFO [Broker id=2] Leader -uve-topic-21-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,244] INFO [Broker id=2] Leader -uve-topic-20-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,247] INFO [Broker id=2] Leader -uve-topic-22-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,253] INFO [Broker id=2] Leader -uve-topic-3-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,256] INFO [Broker id=2] Leader -uve-topic-19-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,260] INFO [Broker id=2] Leader -uve-topic-10-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,263] INFO [Broker id=2] Leader -uve-topic-11-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,266] INFO [Broker id=2] Leader -uve-topic-23-0 starts at leader epoch 4 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,269] INFO [Broker id=2] Leader -uve-topic-24-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,272] INFO [Broker id=2] Leader -uve-topic-28-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,275] INFO [Broker id=2] Leader -uve-topic-3-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,279] INFO [Broker id=2] Leader -uve-topic-15-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,283] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,287] INFO [Broker id=2] Leader -uve-topic-19-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,293] INFO [Broker id=2] Leader -uve-topic-17-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,300] INFO [Broker id=2] Leader -uve-topic-20-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,303] INFO [Broker id=2] Leader -uve-topic-29-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,306] INFO [Broker id=2] Leader -uve-topic-16-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,309] INFO [Broker id=2] Leader -uve-topic-21-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,312] INFO [Broker id=2] Leader -uve-topic-28-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,316] INFO [Broker id=2] Leader -uve-topic-29-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,319] INFO [Broker id=2] Leader -uve-topic-15-7 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,322] INFO [Broker id=2] Leader -uve-topic-16-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,325] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,329] INFO [Broker id=2] Leader -uve-topic-9-26 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,333] INFO [Broker id=2] Leader -uve-topic-1-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,336] INFO [Broker id=2] Leader -uve-topic-23-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,338] INFO [Broker id=2] Leader -uve-topic-10-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,343] INFO [Broker id=2] Leader structured_syslog_topic-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,346] INFO [Broker id=2] Leader -uve-topic-2-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,349] INFO [Broker id=2] Leader -uve-topic-22-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,353] INFO [Broker id=2] Leader -uve-topic-18-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,356] INFO [Broker id=2] Leader -uve-topic-6-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,372] INFO [Broker id=2] Leader -uve-topic-5-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,376] INFO [Broker id=2] Leader -uve-topic-14-3 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,379] INFO [Broker id=2] Leader -uve-topic-27-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,382] INFO [Broker id=2] Leader -uve-topic-7-11 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,385] INFO [Broker id=2] Leader -uve-topic-20-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,389] INFO [Broker id=2] Leader -uve-topic-0-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,391] INFO [Broker id=2] Leader -uve-topic-9-23 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,396] INFO [Broker id=2] Leader -uve-topic-1-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,405] INFO [Broker id=2] Leader -uve-topic-17-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,408] INFO [Broker id=2] Leader structured_syslog_topic-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,412] INFO [Broker id=2] Leader -uve-topic-5-28 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,415] INFO [Broker id=2] Leader -uve-topic-4-8 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,419] INFO [Broker id=2] Leader -uve-topic-11-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,421] INFO [Broker id=2] Leader -uve-topic-24-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,424] INFO [Broker id=2] Leader -uve-topic-13-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,427] INFO [Broker id=2] Leader -uve-topic-12-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,431] INFO [Broker id=2] Leader -uve-topic-26-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,434] INFO [Broker id=2] Leader -uve-topic-29-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,438] INFO [Broker id=2] Leader -uve-topic-16-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,441] INFO [Broker id=2] Leader -uve-topic-17-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,445] INFO [Broker id=2] Leader -uve-topic-22-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,448] INFO [Broker id=2] Leader -uve-topic-18-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,451] INFO [Broker id=2] Leader -uve-topic-21-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,454] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,458] INFO [Broker id=2] Leader -uve-topic-17-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,461] INFO [Broker id=2] Leader -uve-topic-23-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,465] INFO [Broker id=2] Leader -uve-topic-10-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,468] INFO [Broker id=2] Leader -uve-topic-12-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,472] INFO [Broker id=2] Leader -uve-topic-25-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,475] INFO [Broker id=2] Leader -uve-topic-11-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,478] INFO [Broker id=2] Leader -uve-topic-19-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,482] INFO [Broker id=2] Leader -uve-topic-21-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,485] INFO [Broker id=2] Leader -uve-topic-20-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,488] INFO [Broker id=2] Leader -uve-topic-28-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,492] INFO [Broker id=2] Leader -uve-topic-15-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,495] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,498] INFO [Broker id=2] Leader -uve-topic-22-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,502] INFO [Broker id=2] Leader -uve-topic-18-17 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,507] INFO [Broker id=2] Leader -uve-topic-14-22 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,510] INFO [Broker id=2] Leader -uve-topic-13-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,514] INFO [Broker id=2] Leader -uve-topic-26-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,517] INFO [Broker id=2] Leader -uve-topic-27-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,521] INFO [Broker id=2] Leader -uve-topic-6-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,524] INFO [Broker id=2] Leader -uve-topic-1-14 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,528] INFO [Broker id=2] Leader -uve-topic-0-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,532] INFO [Broker id=2] Leader -uve-topic-22-5 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,536] INFO [Broker id=2] Leader -uve-topic-4-27 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,539] INFO [Broker id=2] Leader -uve-topic-3-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,542] INFO [Broker id=2] Leader -uve-topic-9-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,546] INFO [Broker id=2] Leader -uve-topic-28-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,549] INFO [Broker id=2] Leader -uve-topic-29-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,552] INFO [Broker id=2] Leader -uve-topic-15-4 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,555] INFO [Broker id=2] Leader -uve-topic-16-24 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,559] INFO [Broker id=2] Leader -uve-topic-8-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,562] INFO [Broker id=2] Leader -uve-topic-2-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,565] INFO [Broker id=2] Leader -uve-topic-3-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,568] INFO [Broker id=2] Leader -uve-topic-9-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,572] INFO [Broker id=2] Leader -uve-topic-2-25 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,575] INFO [Broker id=2] Leader -uve-topic-1-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,578] INFO [Broker id=2] Leader structured_syslog_topic-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,581] INFO [Broker id=2] Leader -uve-topic-22-12 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,585] INFO [Broker id=2] Leader -uve-topic-1-21 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,588] INFO [Broker id=2] Leader -uve-topic-0-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,592] INFO [Broker id=2] Leader -uve-topic-9-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,595] INFO [Broker id=2] Leader -uve-topic-4-24 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,598] INFO [Broker id=2] Leader -uve-topic-6-26 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,601] INFO [Broker id=2] Leader -uve-topic-5-6 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,605] INFO [Broker id=2] Leader -uve-topic-9-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,609] INFO [Broker id=2] Leader -uve-topic-22-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,612] INFO [Broker id=2] Leader -uve-topic-1-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,616] INFO [Broker id=2] Leader -uve-topic-17-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,619] INFO [Broker id=2] Leader -uve-topic-3-23 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,623] INFO [Broker id=2] Leader -uve-topic-19-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,626] INFO [Broker id=2] Leader -uve-topic-4-5 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,629] INFO [Broker id=2] Leader -uve-topic-5-25 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,633] INFO [Broker id=2] Leader -uve-topic-20-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,637] INFO [Broker id=2] Leader -uve-topic-28-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,640] INFO [Broker id=2] Leader -uve-topic-3-4 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,643] INFO [Broker id=2] Leader -uve-topic-15-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,646] INFO [Broker id=2] Leader HEALTH_CHECK_TOPIC-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,650] INFO [Broker id=2] Leader -uve-topic-8-28 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,653] INFO [Broker id=2] Leader -uve-topic-0-10 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,657] INFO [Broker id=2] Leader -uve-topic-17-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,660] INFO [Broker id=2] Leader -uve-topic-20-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,664] INFO [Broker id=2] Leader -uve-topic-29-0 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,672] INFO [Broker id=2] Leader -uve-topic-16-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,676] INFO [Broker id=2] Leader -uve-topic-21-1 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,682] INFO [Broker id=2] Leader -uve-topic-2-22 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,686] INFO [Broker id=2] Leader -uve-topic-9-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,690] INFO [Broker id=2] Leader -uve-topic-1-2 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,694] INFO [Broker id=2] Leader -uve-topic-23-13 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,697] INFO [Broker id=2] Leader -uve-topic-10-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,700] INFO [Broker id=2] Leader -uve-topic-17-13 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,704] INFO [Broker id=2] Leader structured_syslog_topic-18 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,707] INFO [Broker id=2] Leader -uve-topic-2-3 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,710] INFO [Broker id=2] Leader -uve-topic-14-19 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,714] INFO [Broker id=2] Leader -uve-topic-27-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,719] INFO [Broker id=2] Leader -uve-topic-7-27 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,722] INFO [Broker id=2] Leader -uve-topic-6-7 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,726] INFO [Broker id=2] Leader -uve-topic-13-18 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,729] INFO [Broker id=2] Leader -uve-topic-26-16 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,732] INFO [Broker id=2] Leader -uve-topic-14-0 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,736] INFO [Broker id=2] Leader -uve-topic-8-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,746] INFO [Broker id=2] Leader -uve-topic-0-20 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,749] INFO [Broker id=2] Leader -uve-topic-21-11 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,752] INFO [Broker id=2] Leader -uve-topic-12-17 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,759] INFO [Broker id=2] Leader -uve-topic-25-15 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,762] INFO [Broker id=2] Leader -uve-topic-21-20 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,766] INFO [Broker id=2] Leader -uve-topic-0-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,769] INFO [Broker id=2] Leader -uve-topic-22-2 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,772] INFO [Broker id=2] Leader -uve-topic-9-29 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,775] INFO [Broker id=2] Leader -uve-topic-8-9 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,778] INFO [Broker id=2] Leader -uve-topic-29-29 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,782] INFO [Broker id=2] Leader -uve-topic-11-16 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,785] INFO [Broker id=2] Leader -uve-topic-24-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,788] INFO [Broker id=2] Leader -uve-topic-18-14 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,791] INFO [Broker id=2] Leader -uve-topic-29-19 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,794] INFO [Broker id=2] Leader -uve-topic-15-1 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,797] INFO [Broker id=2] Leader -uve-topic-16-21 starts at leader epoch 7 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,800] INFO [Broker id=2] Leader -uve-topic-7-8 starts at leader epoch 6 from offset 0 with high watermark 0 ISR [2] addingReplicas [] removingReplicas []. Previous leader epoch was -1. (state.change.logger)
[2025-02-13 02:13:20,816] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 5 with correlation id 4 (state.change.logger)
[2025-02-13 02:13:30,823] INFO [Broker id=2] Add 960 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 5 with correlation id 5 (state.change.logger)
[2025-02-13 02:18:16,668] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 6 from controller 3 for 320 partitions (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-18-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-29-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-2-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-17-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-21-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-26-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-24-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] 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-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-0-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-1-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-7-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] Follower -uve-topic-0-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,671] INFO [Broker id=2] 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-13 02:18:16,672] INFO [Broker id=2] Follower structured_syslog_topic-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,672] INFO [Broker id=2] Follower -uve-topic-17-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,672] INFO [Broker id=2] 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-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-4-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-20-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-29-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-2-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] 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-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-18-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] 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-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-20-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-21-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-0-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-4-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-29-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-26-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-10-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-24-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-20-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-29-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-7-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] 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-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-17-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] 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-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-1-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower structured_syslog_topic-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-28-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] 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-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-29-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] Follower -uve-topic-0-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,674] INFO [Broker id=2] 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-13 02:18:16,674] INFO [Broker id=2] 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-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-4-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-20-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-29-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-1-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-2-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-10-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-18-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-28-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower structured_syslog_topic-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-20-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-21-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-17-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-24-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-26-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-28-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-10-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-24-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-20-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-6-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,675] INFO [Broker id=2] 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-13 02:18:16,675] INFO [Broker id=2] Follower -uve-topic-18-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-17-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-21-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-28-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-2-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-28-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-1-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower structured_syslog_topic-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] 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-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-0-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-26-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-4-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] 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-13 02:18:16,676] INFO [Broker id=2] 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-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-4-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] 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-13 02:18:16,676] INFO [Broker id=2] Follower -uve-topic-6-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,676] INFO [Broker id=2] Follower structured_syslog_topic-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,680] INFO [Broker id=2] Follower -uve-topic-1-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-2-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-0-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] 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-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-26-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-28-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] 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-13 02:18:16,681] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-10-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-21-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] 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-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-10-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] 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-13 02:18:16,681] INFO [Broker id=2] Follower -uve-topic-13-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,681] INFO [Broker id=2] 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-13 02:18:16,681] INFO [Broker id=2] Follower structured_syslog_topic-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-1-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-6-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] 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-13 02:18:16,682] INFO [Broker id=2] 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-13 02:18:16,682] INFO [Broker id=2] 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-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-6-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-2-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] 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-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-28-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-21-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] 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-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-0-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-4-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-15-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-28-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] 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-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-4-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] 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-13 02:18:16,682] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,682] INFO [Broker id=2] Follower -uve-topic-6-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,683] INFO [Broker id=2] Follower -uve-topic-13-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,683] INFO [Broker id=2] Follower -uve-topic-10-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,683] INFO [Broker id=2] Follower -uve-topic-22-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,683] INFO [Broker id=2] Follower -uve-topic-21-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,683] INFO [Broker id=2] Follower -uve-topic-14-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,684] INFO [Broker id=2] 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-13 02:18:16,684] INFO [Broker id=2] Follower -uve-topic-16-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,684] INFO [Broker id=2] Follower -uve-topic-2-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,684] INFO [Broker id=2] Follower -uve-topic-1-0 starts at leader epoch 5 from offset 77 with high watermark 77. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:18:16,684] INFO [Broker id=2] 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-13 02:18:16,684] INFO [Broker id=2] 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-13 02:18:16,684] INFO [Broker id=2] Follower -uve-topic-16-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,684] INFO [Broker id=2] Follower -uve-topic-28-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,684] INFO [Broker id=2] 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-13 02:18:16,684] INFO [Broker id=2] Follower -uve-topic-4-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,684] INFO [Broker id=2] 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-13 02:18:16,725] INFO [Broker id=2] 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-13 02:18:16,725] INFO [Broker id=2] 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-13 02:18:16,725] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-13-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-22-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-21-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-15-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-25-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] 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-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-10-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-14-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] 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-13 02:18:16,725] INFO [Broker id=2] Follower -uve-topic-6-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,725] INFO [Broker id=2] 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-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-25-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-12-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-21-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-14-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] 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-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-16-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-28-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-25-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] 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-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-12-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-13-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] 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-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-15-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] 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-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-7-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-6-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] 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-13 02:18:16,726] INFO [Broker id=2] 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-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-22-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-10-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-25-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,726] INFO [Broker id=2] Follower -uve-topic-12-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-7-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-6-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-25-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-12-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-14-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-13-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-25-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-12-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-22-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-16-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-21-0 starts at leader epoch 5 from offset 77 with high watermark 77. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-15-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-10-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower HEALTH_CHECK_TOPIC-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-24-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-6-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-7-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-12-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] Follower -uve-topic-25-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,727] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-15-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-14-15 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-16-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-13-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-22-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-10-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-13-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-22-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-24-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-18-26 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-15-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-6-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-26-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-12-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-25-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-7-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-16-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-14-12 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-16-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-29-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-15-10 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-18-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-20-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-14-9 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-7-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-13-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-22-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] 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-13 02:18:16,728] INFO [Broker id=2] Follower structured_syslog_topic-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,728] INFO [Broker id=2] Follower -uve-topic-24-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-12-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-25-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-26-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-12-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-25-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-26-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-14-6 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-18-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-2-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-7-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-13-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-18-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-22-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-23-0 starts at leader epoch 5 from offset 101 with high watermark 101. Previous leader epoch was 4. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-24-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-17-28 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-20-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-16-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-29-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-15-7 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-1-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower structured_syslog_topic-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-14-3 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-7-11 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-20-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-0-23 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-1-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower structured_syslog_topic-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-17-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-24-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-12-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-26-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-16-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-17-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-18-17 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-13-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-22-5 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-4-27 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-29-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-15-4 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-2-25 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-1-21 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-4-24 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-20-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-16-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-17-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-2-22 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-17-13 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower structured_syslog_topic-18 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-26-16 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-14-0 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] 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-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-0-20 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,729] INFO [Broker id=2] Follower -uve-topic-0-29 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,730] INFO [Broker id=2] Follower -uve-topic-22-2 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,730] INFO [Broker id=2] 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-13 02:18:16,730] INFO [Broker id=2] Follower -uve-topic-24-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,730] INFO [Broker id=2] Follower -uve-topic-18-14 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,730] INFO [Broker id=2] Follower -uve-topic-29-19 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,730] INFO [Broker id=2] Follower -uve-topic-7-8 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,730] INFO [Broker id=2] Follower -uve-topic-15-1 starts at leader epoch 7 from offset 0 with high watermark 0. Previous leader epoch was 6. (state.change.logger)
[2025-02-13 02:18:16,747] INFO [Broker id=2] Stopped fetchers as part of become-follower request from controller 3 epoch 5 with correlation id 6 for 320 partitions (state.change.logger)
[2025-02-13 02:18:17,201] INFO [Broker id=2] Add 320 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 5 with correlation id 7 (state.change.logger)
[2025-02-13 02:18:17,203] INFO [Broker id=2] Handling LeaderAndIsr request correlationId 8 from controller 3 for 320 partitions (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-23-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-16-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-11-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-17-0 starts at leader epoch 8 from offset 14 with high watermark 14. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-0-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-9-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-2-0 starts at leader epoch 8 from offset 77 with high watermark 77. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-3-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-22-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-21-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-5-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-8-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-21-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-16-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-25-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-23-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-19-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-11-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-22-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-5-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-21-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-3-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-21-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-8-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-0-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,204] INFO [Broker id=2] 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-13 02:18:17,204] INFO [Broker id=2] Follower -uve-topic-3-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-13-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-5-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-7-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-19-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-8-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-23-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-27-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-22-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-21-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-28-0 starts at leader epoch 8 from offset 252 with high watermark 252. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-16-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-11-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-25-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-3-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-23-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-11-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-25-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-22-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-19-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-27-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-5-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-13-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-27-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-7-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-16-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-11-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-3-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-27-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-22-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-13-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-25-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-5-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-7-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-19-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-27-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-23-17 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] 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-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-16-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,205] INFO [Broker id=2] Follower -uve-topic-16-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-27-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-23-14 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-25-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-26-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-5-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-27-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-3-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-7-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-13-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-19-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-22-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-13-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-7-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-19-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-25-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,206] INFO [Broker id=2] Follower -uve-topic-26-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,206] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-27-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-23-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-16-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-29-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-3-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-13-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-22-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-13-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-5-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-29-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-7-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-18-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-19-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-26-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-25-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-17-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-16-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-13-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-27-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-24-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-23-8 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-25-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-13-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-22-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-5-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-18-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-17-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-16-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-22-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] 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-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-29-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-26-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-12-0 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-13-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-7-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,209] INFO [Broker id=2] Follower -uve-topic-25-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-19-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-27-0 starts at leader epoch 8 from offset 266 with high watermark 266. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-24-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-23-5 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-17-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-16-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-25-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-0-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-24-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-18-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-19-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-22-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-24-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-26-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,210] INFO [Broker id=2] 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-13 02:18:17,210] INFO [Broker id=2] Follower -uve-topic-8-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-29-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-7-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-23-2 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-9-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-17-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-0-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-2-27 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-9-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-18-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-24-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-8-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-7-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-24-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-29-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-19-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-26-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-24-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-26-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-17-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,216] INFO [Broker id=2] Follower -uve-topic-11-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,216] INFO [Broker id=2] 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-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-9-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] 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-13 02:18:17,218] INFO [Broker id=2] 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-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-8-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-0-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-29-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-2-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-7-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-2-24 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-24-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-18-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] 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-13 02:18:17,218] INFO [Broker id=2] 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-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-0-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-29-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-2-21 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-18-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-24-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-8-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,218] INFO [Broker id=2] 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-13 02:18:17,218] INFO [Broker id=2] Follower -uve-topic-21-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-26-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-11-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-17-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-9-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-18-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-2-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-24-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-8-15 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-0-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-2-18 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-18-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-9-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-26-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-17-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-21-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-3-29 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-11-22 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-29-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-2-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-18-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-11-19 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-5-28 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-29-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-18-7 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-17-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-21-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-26-0 starts at leader epoch 8 from offset 144 with high watermark 144. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,219] INFO [Broker id=2] 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-13 02:18:17,219] INFO [Broker id=2] Follower -uve-topic-0-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-9-13 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-8-12 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-3-26 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-2-6 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-9-4 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-0-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-9-1 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-9-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-17-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-3-23 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-5-25 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-20-0 starts at leader epoch 8 from offset 121 with high watermark 121. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-0-10 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-29-0 starts at leader epoch 8 from offset 80 with high watermark 80. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] 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-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-2-3 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-21-11 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-21-20 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-8-9 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,220] INFO [Broker id=2] Follower -uve-topic-11-16 starts at leader epoch 8 from offset 0 with high watermark 0. Previous leader epoch was 7. (state.change.logger)
[2025-02-13 02:18:17,238] INFO [Broker id=2] Stopped fetchers as part of become-follower request from controller 3 epoch 5 with correlation id 8 for 320 partitions (state.change.logger)
[2025-02-13 02:18:18,319] INFO [Broker id=2] Add 320 partitions and deleted 0 partitions from metadata cache in response to UpdateMetadata request sent by controller 3 epoch 5 with correlation id 9 (state.change.logger)