- We are using the zookeeper less Kafka (kafka Kraft).
- The cluster is having 3 nodes.
- One of the nodes gets automatically shut down randomly.
- Checked the logs but didn't get the exact reason.
- Sharing the logs below. Kafka version - 3.3.1
[2023-04-13 01:49:17,531] INFO [RaftManager nodeId=1] Completed transition to Unattached(epoch=37112, voters=[1, 2, 3], electionTimeoutMs=982) (org.apache.kafka.raft.QuorumState)
[2023-04-13 02:00:33,902] WARN [Controller 1] Renouncing the leadership due to a metadata log event. We were the leader at epoch 37116, but in the new epoch 37117, the leader is (none). Reverting to last committed offset 28292807. (org.apache.kafka.controller.QuorumController)
[2023-04-13 02:00:33,936] INFO [RaftManager nodeId=1] Completed transition to Unattached(epoch=37118, voters=[1, 2, 3], electionTimeoutMs=1497) (org.apache.kafka.raft.QuorumState)
[2023-04-13 02:00:35,014] ERROR [Controller 1] processBrokerHeartbeat: unable to start processing because of NotControllerException. (org.apache.kafka.controller.QuorumController)
[2023-04-13 02:12:21,883] WARN [Controller 1] Renouncing the leadership due to a metadata log event. We were the leader at epoch 37129, but in the new epoch 37131, the leader is (none). Reverting to last committed offset 28294206. (org.apache.kafka.controller.QuorumController)
[2023-04-13 02:13:41,328] WARN [Controller 1] Renouncing the leadership due to a metadata log event. We were the leader at epoch 37141, but in the new epoch 37142, the leader is (none). Reverting to last committed offset 28294325. (org.apache.kafka.controller.QuorumController)
[2023-04-13 02:13:41,328] INFO [Controller 1] writeNoOpRecord: failed with NotControllerException in 16561838 us (org.apache.kafka.controller.QuorumController)
[2023-04-13 02:13:41,328] INFO [Controller 1] maybeFenceReplicas: failed with NotControllerException in 8520846 us (org.apache.kafka.controller.QuorumController)
[2023-04-13 02:13:41,328] INFO [BrokerToControllerChannelManager broker=1 name=heartbeat] Client requested disconnect from node 1 (org.apache.kafka.clients.NetworkClient)
[2023-04-13 02:13:41,329] INFO [BrokerLifecycleManager id=1] Unable to send a heartbeat because the RPC got timed out before it could be sent. (kafka.server.BrokerLifecycleManager)
[2023-04-13 02:13:41,351] ERROR Encountered fatal fault: exception while renouncing leadership (org.apache.kafka.server.fault.ProcessExitingFaultHandler)
java.lang.NullPointerException
at org.apache.kafka.timeline.SnapshottableHashTable$HashTier.mergeFrom(SnapshottableHashTable.java:125)
at org.apache.kafka.timeline.Snapshot.mergeFrom(Snapshot.java:68)
at org.apache.kafka.timeline.SnapshotRegistry.deleteSnapshot(SnapshotRegistry.java:236)
at org.apache.kafka.timeline.SnapshotRegistry$SnapshotIterator.remove(SnapshotRegistry.java:67)
at org.apache.kafka.timeline.SnapshotRegistry.revertToSnapshot(SnapshotRegistry.java:214)
at org.apache.kafka.controller.QuorumController.renounce(QuorumController.java:1232)
at org.apache.kafka.controller.QuorumController.access$3300(QuorumController.java:150)
at org.apache.kafka.controller.QuorumController$QuorumMetaLogListener.lambda$handleLeaderChange$3(QuorumController.java:1076)
at org.apache.kafka.controller.QuorumController$QuorumMetaLogListener.lambda$appendRaftEvent$4(QuorumController.java:1101)
at org.apache.kafka.controller.QuorumController$ControlEvent.run(QuorumController.java:496)
at org.apache.kafka.queue.KafkaEventQueue$EventContext.run(KafkaEventQueue.java:121)
at org.apache.kafka.queue.KafkaEventQueue$EventHandler.handleEvents(KafkaEventQueue.java:200)
at org.apache.kafka.queue.KafkaEventQueue$EventHandler.run(KafkaEventQueue.java:173)
at java.lang.Thread.run(Thread.java:750)
[2023-04-13 02:13:41,385] INFO [BrokerServer id=1] Transition from STARTED to SHUTTING_DOWN (kafka.server.BrokerServer)
Disclaimer: The information in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful. Drishti is neither liable for the improper, incomplete transmission of the information contained in this communication nor any delay in its receipt. The communication is not intended to operate as an electronic signature under any applicable law. Drishti assumes no responsibility for any loss or damage resulting from the use of e-mails.
Comments
Post a Comment