Apache kafka 模式注册表赢得'；t升级到Confluent 4.1后启动

我最近将Confluent升级到4.1，但schema registry似乎有一些问题。在

合流启动时

架构注册表（因此ksql服务器）无法启动

以下是我在schema registry的日志中发现的错误：

[2018-04-20 11:27:38,426] ERROR Error starting the schema registry (io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication:65)
io.confluent.kafka.schemaregistry.exceptions.SchemaRegistryInitializationException: Error initializing kafka store while initializing schema registry
        at io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry.init(KafkaSchemaRegistry.java:203)
        at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.setupResources(SchemaRegistryRestApplication.java:63)
        at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.setupResources(SchemaRegistryRestApplication.java:41)
        at io.confluent.rest.Application.createServer(Application.java:165)
        at io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain.main(SchemaRegistryMain.java:43)
Caused by: io.confluent.kafka.schemaregistry.storage.exceptions.StoreInitializationException: io.confluent.kafka.schemaregistry.storage.exceptions.StoreException: Failed to write Noop record to kafka store.
        at io.confluent.kafka.schemaregistry.storage.KafkaStore.init(KafkaStore.java:139)
        at io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry.init(KafkaSchemaRegistry.java:201)
        ... 4 more
Caused by: io.confluent.kafka.schemaregistry.storage.exceptions.StoreException: Failed to write Noop record to kafka store.
        at io.confluent.kafka.schemaregistry.storage.KafkaStore.getLatestOffset(KafkaStore.java:423)
        at io.confluent.kafka.schemaregistry.storage.KafkaStore.waitUntilKafkaReaderReachesLastOffset(KafkaStore.java:276)
        at io.confluent.kafka.schemaregistry.storage.KafkaStore.init(KafkaStore.java:137)
        ... 5 more
Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition.
        at org.apache.kafka.clients.producer.internals.FutureRecordMetadata.valueOrError(FutureRecordMetadata.java:94)
        at org.apache.kafka.clients.producer.internals.FutureRecordMetadata.get(FutureRecordMetadata.java:77)
        at org.apache.kafka.clients.producer.internals.FutureRecordMetadata.get(FutureRecordMetadata.java:29)
        at io.confluent.kafka.schemaregistry.storage.KafkaStore.getLatestOffset(KafkaStore.java:418)
        ... 7 more
Caused by: org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition.
[2018-04-20 11:27:38,430] INFO Shutting down schema registry (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:726)
[2018-04-20 11:27:38,430] INFO [kafka-store-reader-thread-_schemas]: Shutting down (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:66)
[2018-04-20 11:27:38,431] INFO [kafka-store-reader-thread-_schemas]: Stopped (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:66)
[2018-04-20 11:27:38,440] INFO [kafka-store-reader-thread-_schemas]: Shutdown completed (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:66)
[2018-04-20 11:27:38,446] INFO KafkaStoreReaderThread shutdown complete. (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:227)

我不知道为什么会报告此错误，并且错误消息对我来说没有太大意义

失败后，

confluent start schema registry

和

confluent start ksql server

启动这两个服务，但在启动ksql时，我收到以下警告：

**************** WARNING ******************
Remote server address may not be valid:
Error issuing GET to KSQL server
Caused by: java.net.ConnectException: Connection refused (Connection refused)
Caused by: Could not connect to the server.
*******************************************

尝试运行命令时（例如，

显示表格；

）会报告以下错误：

ksql> show tables;
Error issuing POST to KSQL server
Caused by: java.net.ConnectException: Connection refused (Connection refused)
Caused by: Could not connect to the server.

---

EDIT:我通过销毁当前运行（

confluent destroy）解决了这个问题。

但如果有人能解释这个问题，那将很有趣

从您发布的信息来看，感觉您可能在某个地方有一些僵尸进程或坏数据，尽管我不能确定

架构注册表抱怨它无法向Kafka写入消息，因为Kafka代理抱怨它不拥有架构注册表正在写入的主题分区。这可能是由于以前的Kafka代理（来自旧安装）仍在运行造成的

升级前您是否停止了合流

使用

合流销毁

，正如您所做的那样，平铺/重置安装始终是一个不错的选择，只要您对数据不感兴趣。检查伪进程（或使用旧的“重新启动机器”技巧），也可以是在事情没有按照您预期的方式运行时开始的好地方

很高兴现在一切都好了：D

---

安迪

从你发布的信息来看，你可能在某个地方有一些僵尸进程或坏数据，尽管我不能确定

架构注册表抱怨它无法向Kafka写入消息，因为Kafka代理抱怨它不拥有架构注册表正在写入的主题分区。这可能是由于以前的Kafka代理（来自旧安装）仍在运行造成的

升级前您是否停止了合流

使用

合流销毁

，正如您所做的那样，平铺/重置安装始终是一个不错的选择，只要您对数据不感兴趣。检查伪进程（或使用旧的“重新启动机器”技巧），也可以是在事情没有按照您预期的方式运行时开始的好地方

很高兴现在一切都好了：D

---

安迪

我不确定升级前是否运行了

合流停止

。很可能我没有，所以我想这可能会导致问题！干杯。我不确定在升级之前是否运行了

汇合站

。很可能我没有，所以我想这可能会导致问题！干杯