首先：一定要先启动ZooKeeper 再启动Kafka 顺序不可以改变。
先关闭kafka ，再关闭zookeeper。
启动ZooKeeper后不要暴力关闭命令行，否则接下来启动kafka时会连接不上，显示Timeout错误
两个都不能暴力关闭
kafka关闭时：
现象：在windows的命令行里启动kafka之后，当关闭命令行窗口时，就会强制关闭kafka。这种关闭方式为暴力关闭，很可能会导致kafka无法完成对日志文件的解锁。届时，再次启动kafka的时候，就会提示日志文件被锁，无法成功启动。
方案：将kafka的日志文件全部删除，再次启动即可。
建议：不要暴力关闭kafka，建议通过在命令行执行kafka-server-stop命令来关闭它。
其他：将来在Linux上部署kafka之后，采用后台运行的方式，就会避免这样的问题。
[2022-05-03 22:20:39,636] INFO [ThrottledChannelReaper-Fetch]: Starting (kafka.server.ClientQuotaManager$ThrottledChannelReaper)
[2022-05-03 22:20:39,636] INFO [ThrottledChannelReaper-Produce]: Starting (kafka.server.ClientQuotaManager$ThrottledChannelReaper)
[2022-05-03 22:20:39,639] INFO [ThrottledChannelReaper-Request]: Starting (kafka.server.ClientQuotaManager$ThrottledChannelReaper)
[2022-05-03 22:20:39,687] INFO Log directory d:\work\data\kafka-logs not found, creating it. (kafka.log.LogManager)
[2022-05-03 22:20:39,714] INFO Loading logs. (kafka.log.LogManager)
[2022-05-03 22:20:39,732] INFO Logs loading complete in 18 ms. (kafka.log.LogManager)
[2022-05-03 22:20:39,748] INFO Starting log cleanup with a period of 300000 ms. (kafka.log.LogManager)
[2022-05-03 22:20:39,767] INFO Starting log flusher with a default period of 9223372036854775807 ms. (kafka.log.LogManager)
log4j:ERROR Failed to rename [D:\kafka\kafka_2.12-2.3.0/logs/log-cleaner.log] to [D:\kafka\kafka_2.12-2.3.0/logs/log-cleaner.log.2022-05-03-21].
[2022-05-03 22:20:40,356] INFO Awaiting socket connections on 0.0.0.0:9092. (kafka.network.Acceptor)
[2022-05-03 22:20:40,403] INFO [SocketServer brokerId=0] Created data-plane acceptor and processors for endpoint : EndPoint(null,9092,ListenerName(PLAINTEXT),PLAINTEXT) (kafka.network.SocketServer)
[2022-05-03 22:20:40,406] INFO [SocketServer brokerId=0] Started 1 acceptor threads for data-plane (kafka.network.SocketServer)
[2022-05-03 22:20:40,447] INFO [ExpirationReaper-0-Produce]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2022-05-03 22:20:40,447] INFO [ExpirationReaper-0-Fetch]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2022-05-03 22:20:40,447] INFO [ExpirationReaper-0-DeleteRecords]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2022-05-03 22:20:40,452] INFO [ExpirationReaper-0-ElectPreferredLeader]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2022-05-03 22:20:40,486] INFO [LogDirFailureHandler]: Starting (kafka.server.ReplicaManager$LogDirFailureHandler)
[2022-05-03 22:20:40,529] INFO Creating /brokers/ids/0 (is it secure? false) (kafka.zk.KafkaZkClient)
[2022-05-03 22:20:40,561] INFO Stat of the created znode at /brokers/ids/0 is: 24,24,1651587640550,1651587640550,1,0,0,72060518031163392,200,0,24
(kafka.zk.KafkaZkClient)
[2022-05-03 22:20:40,562] INFO Registered broker 0 at path /brokers/ids/0 with addresses: ArrayBuffer(EndPoint(LAPTOP-5S4ELDN5,9092,ListenerName(PLAINTEXT),PLAINTEXT)), czxid (broker epoch): 24 (kafka.zk.KafkaZkClient)
[2022-05-03 22:20:40,566] WARN No meta.properties file under dir d:\work\data\kafka-logs\meta.properties (kafka.server.BrokerMetadataCheckpoint)
[2022-05-03 22:20:40,642] INFO [ExpirationReaper-0-topic]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2022-05-03 22:20:40,642] INFO [ExpirationReaper-0-Heartbeat]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2022-05-03 22:20:40,642] INFO [ExpirationReaper-0-Rebalance]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2022-05-03 22:20:40,670] INFO Successfully created /controller_epoch with initial epoch 0 (kafka.zk.KafkaZkClient)
[2022-05-03 22:20:40,687] INFO [GroupCoordinator 0]: Starting up. (kafka.coordinator.group.GroupCoordinator)
[2022-05-03 22:20:40,689] INFO [GroupCoordinator 0]: Startup complete. (kafka.coordinator.group.GroupCoordinator)
[2022-05-03 22:20:40,696] INFO [GroupMetadataManager brokerId=0] Removed 0 expired offsets in 7 milliseconds. (kafka.coordinator.group.GroupMetadataManager)
[2022-05-03 22:20:40,716] INFO [ProducerId Manager 0]: Acquired new producerId block (brokerId:0,blockStartProducerId:0,blockEndProducerId:999) by writing to Zk with path version 1 (kafka.coordinator.transaction.ProducerIdManager)
[2022-05-03 22:20:40,756] INFO [TransactionCoordinator id=0] Starting up. (kafka.coordinator.transaction.TransactionCoordinator)
[2022-05-03 22:20:40,759] INFO [TransactionCoordinator id=0] Startup complete. (kafka.coordinator.transaction.TransactionCoordinator)
[2022-05-03 22:20:40,759] INFO [Transaction Marker Channel Manager 0]: Starting (kafka.coordinator.transaction.TransactionMarkerChannelManager)
[2022-05-03 22:20:40,829] INFO [/config/changes-event-process-thread]: Starting (kafka.common.ZkNodeChangeNotificationListener$ChangeEventProcessThread)
[2022-05-03 22:20:40,841] INFO [SocketServer brokerId=0] Started data-plane processors for 1 acceptors (kafka.network.SocketServer)
[2022-05-03 22:20:40,855] INFO Kafka version: 2.3.0 (org.apache.kafka.common.utils.AppInfoParser)
[2022-05-03 22:20:40,856] INFO Kafka commitId: fc1aaa116b661c8a (org.apache.kafka.common.utils.AppInfoParser)
[2022-05-03 22:20:40,857] INFO Kafka startTimeMs: 1651587640843 (org.apache.kafka.common.utils.AppInfoParser)
[2022-05-03 22:20:40,865] INFO [KafkaServer id=0] started (kafka.server.KafkaServer)
