You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2021/07/19 16:12:00 UTC
[jira] [Updated] (KAFKA-13100) Controller cannot revert to an
in-memory snapshot
[ https://issues.apache.org/jira/browse/KAFKA-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin McCabe updated KAFKA-13100:
---------------------------------
Priority: Blocker (was: Major)
> Controller cannot revert to an in-memory snapshot
> -------------------------------------------------
>
> Key: KAFKA-13100
> URL: https://issues.apache.org/jira/browse/KAFKA-13100
> Project: Kafka
> Issue Type: Bug
> Components: controller, kraft
> Reporter: Jose Armando Garcia Sancio
> Assignee: Jose Armando Garcia Sancio
> Priority: Blocker
> Labels: kip-500
> Fix For: 3.0.0
>
>
> {code:java}
> [2021-07-16 16:34:55,578] DEBUG [Controller 3002] Executing handleRenounce[3]. (org.apache.kafka.controller.QuorumController)
> [2021-07-16 16:34:55,578] WARN [Controller 3002] Renouncing the leadership at oldEpoch 3 due to a metadata log event. Reverting to last committed offset 214. (org.apache.kafka.controller.QuorumController)
> [2021-07-16 16:34:55,579] WARN [Controller 3002] org.apache.kafka.controller.QuorumController@646b1289: failed with unknown server exception RuntimeException at epoch -1 in 1510 us. Reverting to last committed offset 214. (org.apache.kafka.controller. QuorumController)
> java.lang.RuntimeException: No snapshot for epoch 214. Snapshot epochs are: -1, 1, 3, 5, 11, 16, 21, 26, 31, 36, 41, 46, 51, 56, 61, 94, 96, 97, 107, 108, 112, 125, 126, 128, 135, 171, 208, 213
> at org.apache.kafka.timeline.SnapshotRegistry.getSnapshot(SnapshotRegistry.java:173)
> at org.apache.kafka.timeline.SnapshotRegistry.revertToSnapshot(SnapshotRegistry.java:203)
> at org.apache.kafka.controller.QuorumController.renounce(QuorumController.java:784)
> at org.apache.kafka.controller.QuorumController.access$2500(QuorumController.java:121)
> at org.apache.kafka.controller.QuorumController$QuorumMetaLogListener.lambda$handleLeaderChange$3(QuorumController.java:769)
> at org.apache.kafka.controller.QuorumController$ControlEvent.run(QuorumController.java:311)
> 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:748)
> [2021-07-16 16:34:55,580] ERROR [Controller 3002] Unexpected exception in handleException (org.apache.kafka.queue.KafkaEventQueue)
> java.lang.RuntimeException: No snapshot for epoch 214. Snapshot epochs are: -1, 1, 3, 5, 11, 16, 21, 26, 31, 36, 41, 46, 51, 56, 61, 94, 96, 97, 107, 108, 112, 125, 126, 128, 135, 171, 208, 213
> at org.apache.kafka.timeline.SnapshotRegistry.getSnapshot(SnapshotRegistry.java:173)
> at org.apache.kafka.timeline.SnapshotRegistry.revertToSnapshot(SnapshotRegistry.java:203)
> at org.apache.kafka.controller.QuorumController.renounce(QuorumController.java:784)
> at org.apache.kafka.controller.QuorumController.handleEventException(QuorumController.java:287)
> at org.apache.kafka.controller.QuorumController.access$500(QuorumController.java:121)
> at org.apache.kafka.controller.QuorumController$ControlEvent.handleException(QuorumController.java:317) at org.apache.kafka.queue.KafkaEventQueue$EventContext.run(KafkaEventQueue.java:126)
> 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:748) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)