启动Confluent时Schema Registry启动失败，进程无法正常完成

Hey there, let's troubleshoot this Confluent startup issue step by step. Based on what you've shared, the problems with Kafka and Schema Registry are likely cascading from a core configuration or connectivity mismatch—let's break it down:

You mentioned ZooKeeper runs fine alone, but errors pop up when starting Kafka. This is probably the root cause that's blocking Schema Registry too. Here's what to check:

• Verify ZooKeeper's actual status: Run zkServer.sh status (Linux/macOS) or zk-server.bat status (Windows) to confirm it's in a healthy state (either leader or follower), not stuck in an error loop.
• Double-check Kafka's ZK config: Open your Kafka server.properties file and make sure the zookeeper.connect parameter matches ZooKeeper's listening address and port (from zoo.cfg's clientPort, default is 2181). For example: zookeeper.connect=localhost:2181—no typos, extra spaces, or wrong ports allowed.
• Inspect ZooKeeper logs: Look into logs/zookeeper.log for the exact error thrown when starting Kafka. Common culprits include:
  • Max connection limit exceeded: ZooKeeper defaults to 60 concurrent connections; if you have other services using ZK, you might need to increase maxClientCnxns in zoo.cfg.
  • Version mismatch: Ensure all Confluent components (ZK, Kafka, Schema Registry) are on the same version—mixing different versions can cause compatibility issues.

Schema Registry relies entirely on Kafka to store schemas in the _schemas topic, so it'll keep failing until Kafka is stable. Once Kafka is up:

• Validate Schema Registry's Kafka config: Open schema-registry.properties and confirm kafkastore.bootstrap.servers points to your running Kafka cluster (e.g., localhost:9092 for a single node).
• Ensure the _schemas topic exists: If previous startup attempts failed, this topic might not have been created automatically. Create it manually with:

  kafka-topics.sh --create --topic _schemas --bootstrap-server localhost:9092 --partitions 1 --replication-factor 1 --config cleanup.policy=compact
  

  The cleanup.policy=compact is mandatory here—Schema Registry requires this topic to use log compaction.
• Check Schema Registry logs: Look for repeated error keywords in logs/schema-registry.log (e.g., "Failed to connect to Kafka", "Authorization failed"). If it's a permission issue, make sure the Schema Registry service account has read/write access to the _schemas topic via Kafka ACLs.

Instead of starting all components at once, verify each one works individually first:

1. Start ZooKeeper and confirm it's healthy.
2. Start Kafka, then run kafka-topics.sh --list --bootstrap-server localhost:9092 to confirm Kafka is responsive.
3. Create the _schemas topic if needed.
4. Start Schema Registry, then test it with curl http://localhost:8081/subjects—you should get an empty array or a list of existing schema subjects if everything works.

内容的提问来源于stack exchange，提问作者Scicrazed