[
https://issues.apache.org/jira/browse/KAFKA-16662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848434#comment-17848434
]
Jianbin Chen commented on KAFKA-16662:
--------------------------------------
When I executed ./bin/kafka-features.sh --bootstrap-server 10.58.16.231:9092
upgrade --metadata 3.7, It continuously outputs the following exception
{panel:title=我的标题}
[2024-05-22 11:30:36,491] INFO [UnifiedLog partition=remote-test-5,
dir=/data01/kafka-logs-351] Incremented log start offset to 26267689 due to
leader offset increment (kafka.log.UnifiedLog)
[2024-05-22 11:30:36,497] INFO [UnifiedLog partition=remote-test2-0,
dir=/data01/kafka-logs-351] Incremented log start offset to 3099360 due to
leader offset increment (kafka.log.UnifiedLog)
[2024-05-22 11:30:37,149] ERROR Failed to propagate directory assignments
because the Controller returned error STALE_BROKER_EPOCH
(org.apache.kafka.server.AssignmentsManager)
[2024-05-22 11:30:38,064] ERROR Failed to propagate directory assignments
because the Controller returned error STALE_BROKER_EPOCH
(org.apache.kafka.server.AssignmentsManager)
[2024-05-22 11:30:39,376] ERROR Failed to propagate directory assignments
because the Controller returned error STALE_BROKER_EPOCH
(org.apache.kafka.server.AssignmentsManager)
[2024-05-22 11:30:41,486] ERROR Failed to propagate directory assignments
because the Controller returned error STALE_BROKER_EPOCH
(org.apache.kafka.server.AssignmentsManager)
[2024-05-22 11:30:43,794] INFO [BrokerLifecycleManager id=3] Unable to register
broker 3 because the controller returned error INVALID_REGISTRATION
(kafka.server.BrokerLifecycleManager)
[2024-05-22 11:30:45,224] ERROR Failed to propagate directory assignments
because the Controller returned error STALE_BROKER_EPOCH
(org.apache.kafka.server.AssignmentsManager)
{panel}
controller logs：
{code:java}
java.util.concurrent.CompletionException:
org.apache.kafka.common.errors.StaleBrokerEpochException: Expected broker epoch
41885255, but got broker epoch -1
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:347)
at
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:636)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at
java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2194)
at
org.apache.kafka.controller.QuorumController$ControllerWriteEvent.complete(QuorumController.java:880)
at
org.apache.kafka.controller.QuorumController$ControllerWriteEvent.handleException(QuorumController.java:871)
at
org.apache.kafka.queue.KafkaEventQueue$EventContext.completeWithException(KafkaEventQueue.java:148)
at
org.apache.kafka.queue.KafkaEventQueue$EventContext.run(KafkaEventQueue.java:137)
at
org.apache.kafka.queue.KafkaEventQueue$EventHandler.handleEvents(KafkaEventQueue.java:210)
at
org.apache.kafka.queue.KafkaEventQueue$EventHandler.run(KafkaEventQueue.java:181)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: org.apache.kafka.common.errors.StaleBrokerEpochException: Expected
broker epoch 41885255, but got broker epoch -1{code}
> UnwritableMetadataException: Metadata has been lost
> ---------------------------------------------------
>
> Key: KAFKA-16662
> URL: https://issues.apache.org/jira/browse/KAFKA-16662
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.7.0
> Environment: Docker Image (bitnami/kafka:3.7.0)
> via Docker Compose
> Reporter: Tobias Bohn
> Priority: Major
> Attachments: log.txt
>
>
> Hello,
> First of all: I am new to this Jira and apologize if anything is set or
> specified incorrectly. Feel free to advise me.
> We currently have an error in our test system, which unfortunately I can't
> solve, because I couldn't find anything related to it. No solution could be
> found via the mailing list either.
> The error occurs when we want to start up a node. The node runs using Kraft
> and is both a controller and a broker. The following error message appears at
> startup:
> {code:java}
> kafka | [2024-04-16 06:18:13,707] ERROR Encountered fatal fault: Unhandled
> error initializing new publishers
> (org.apache.kafka.server.fault.ProcessTerminatingFaultHandler)
> kafka | org.apache.kafka.image.writer.UnwritableMetadataException: Metadata
> has been lost because the following could not be represented in metadata
> version 3.5-IV2: the directory assignment state of one or more replicas
> kafka | at
> org.apache.kafka.image.writer.ImageWriterOptions.handleLoss(ImageWriterOptions.java:94)
> kafka | at
> org.apache.kafka.metadata.PartitionRegistration.toRecord(PartitionRegistration.java:391)
> kafka | at org.apache.kafka.image.TopicImage.write(TopicImage.java:71)
> kafka | at
> org.apache.kafka.image.TopicsImage.write(TopicsImage.java:84)
> kafka | at
> org.apache.kafka.image.MetadataImage.write(MetadataImage.java:155)
> kafka | at
> org.apache.kafka.image.loader.MetadataLoader.initializeNewPublishers(MetadataLoader.java:295)
> kafka | at
> org.apache.kafka.image.loader.MetadataLoader.lambda$scheduleInitializeNewPublishers$0(MetadataLoader.java:266)
> kafka | at
> org.apache.kafka.queue.KafkaEventQueue$EventContext.run(KafkaEventQueue.java:127)
> kafka | at
> org.apache.kafka.queue.KafkaEventQueue$EventHandler.handleEvents(KafkaEventQueue.java:210)
> kafka | at
> org.apache.kafka.queue.KafkaEventQueue$EventHandler.run(KafkaEventQueue.java:181)
> kafka | at java.base/java.lang.Thread.run(Thread.java:840)
> kafka exited with code 0 {code}
> We use Docker to operate the cluster. The error occurred while we were trying
> to restart a node. All other nodes in the cluster are still running correctly.
> If you need further information, please let us know. The complete log is
> attached to this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
