昨天刚部署好kafka集群,是在windows虚拟机上部署的,三个zookeeepr和三个kafka,都是部署在同一台虚拟机上。然后今天同事测试项目代码连接我部署的kafka集群时,下午他就发了这个报错信息给我:
1 partitions have leader brokers without a matching listener,including [gw651_downstream-0].
我打开虚拟机,去到kafka和zookeeper运行黑窗口中就看到了如下错误,想请问下是什么原因?我该怎么解决这个bug?
其中一个zookeeper黑窗口发现如下信息:
java.io.IOException:远程主机强迫关闭了一个现有的连接.
at sun.nio.ch.SocketDispatcher.read0<Native Method>
at sun.nio.ch.SocketDispatcher.read<SocketDispatcher.java.java:43>
at sun.nio.ch.IOUtil.readIntoNativeBuffer<IOUtil.java:223>
at sun.nio.ch.IOUtil.read<IOUtil.java:197>
at sun.nio.ch.SocketChannelImpl.read<SocketChannelImpl.java:380>
at org.apache.zookeeper.server.NIOServerCnxn.doIO<NIOServerCnxn.java:324>
其中一个Kafka黑窗口有发现如下信息:
[error occurred during error reporting (nul1l). id 0xc0000005 ]
# There is insufficient memory for the Java Runtine Environnent to continue。
# Native memory allocation (malloc) failed to allocate 32744 bytes for ChunkPoo1::allocate
# An error report file with more infornation is saved as:
# C:\javaPro\kafka\kafka_2.12-2.5.0-1\bin\windows\hs_err_pid3984.log
# Compiler replay data is saved as:
# C:\javaPro\kafka\kafka_2.12-25.0-1\bin\windows\replay_pid3984.log
还有一个kafka黑窗口发现如下:
Caused by: java.io.I0Exception:存储空间不足,无法处理此命令.
at java.io.FileOutputStream.writeBytes<Native Method>
at java.io.FileOutputStream.write<FileOutputStream.java:326>
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221>
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java-291)
at sun.nio.cs.StreamEncoder.implFlush<StreamEncoder.java:295>
at sun.nio.cs.StreamEncoder.flush<OutputStreamWriter.java:229)
at java.io.BufferedWriter.flush(BufferedWriter.java:254>
at kafka.server.checkpoints.CheckpointFile.liftedTree1$1<CheckpointFile.scala:66>
at kafka.server.checkpoints.CheckpointFile.write<checkpointFile.scala:50>
at kafka.server.checkpoints.0ffsetCheckpointFile.write<OffsetCheckpointFile.scala:59>
at kafka.server.ReplicaManager.$anonfun$checkpointHighWatermarks$8<ReplicaManager.scala:1601>
.....
后面还有一句话:
WARN Stopping serving logs in dir C:\tmp\kafka-logs-2 <kafka.log.LogManager>
ERROR Shutdown broker because all log dirs in C:\tmp\kafka-logs-2 have failed <kafka.log.LogManager>
执行kafka命令时信息显示如下:
kafka-topics.sh --zookeeper localhost:2181 --describe --topic test600
Topic: test600 PartitionCount: 1 ReplicationFactor: 1 Configs:
Topic: test600 Partition: 0 Leader: none Replicas: 2 Isr: 2
kafka-topics.bat --zookeeper localhost:2182 --describe --topic gw651_downstream
Topic: gw651_downstream PartitionCount: 1 ReplicationFactor: 1 Configs:
Topic: gw651_downstream Partition: 0 Leader: none Replicas: 1 Isr: 1
昨天刚部署好kafka集群,是在windows虚拟机上部署的,三个zookeeepr和三个kafka,都是部署在同一台虚拟机上.然后今天同事测试项目代码连接我部署的kafka集群时,下午他就发了这个报错信息给我:1 partitions have leader brokers without a matching listener,including [gw651_downstream-0].
我打开虚拟机,去到kafka和zookeeper运行黑窗口中就看到了如下错误,想请问下是什么原因?我该怎么解决这个bug? :
其中一个zookeeper黑窗口发现如下信息:
java.io.IOException:远程主机强迫关闭了一个现有的连接.
at sun.nio.ch.SocketDispatcher.read0
at sun.nio.ch.SocketDispatcher.read
at sun.nio.ch.IOUtil.readIntoNativeBuffer
at sun.nio.ch.IOUtil.read
at sun.nio.ch.SocketChannelImpl.read
at org.apache.zookeeper.server.NIOServerCnxn.doIO
其中一个Kafka黑窗口有发现如下信息:
[error occurred during error reporting (nul1l). id 0xc0000005 ]
还有一个kafka黑窗口发现如下:
Caused by: java.io.I0Exception:存储空间不足,无法处理此命令.
at java.io.FileOutputStream.writeBytes
at java.io.FileOutputStream.write
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221>
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java-291)
at sun.nio.cs.StreamEncoder.implFlush
at sun.nio.cs.StreamEncoder.flush
at kafka.server.checkpoints.CheckpointFile.liftedTree1$1
at kafka.server.checkpoints.CheckpointFile.write
at kafka.server.checkpoints.0ffsetCheckpointFile.write
at kafka.server.ReplicaManager.$anonfun$checkpointHighWatermarks$8
.....
后面还有一句话:
WARN Stopping serving logs in dir C:\tmp\kafka-logs-2
ERROR Shutdown broker because all log dirs in C:\tmp\kafka-logs-2 have failed
1.命令:kafka-topics.sh --zookeeper localhost:2181 --describe --topic test600
Topic: test600 PartitionCount: 1 ReplicationFactor: 1 Configs:
Topic: test600 Partition: 0 Leader: none Replicas: 2 Isr: 2
2.命令:kafka-topics.bat --zookeeper localhost:2182 --describe --topic gw651_downstream
Topic: gw651_downstream PartitionCount: 1 ReplicationFactor: 1 Configs:
Topic: gw651_downstream Partition: 0 Leader: none Replicas: 1 Isr: 1
昨天刚部署好kafka集群,是在windows虚拟机上部署的,三个zookeeepr和三个kafka,都是部署在同一台虚拟机上.然后今天同事测试项目代码连接我部署的kafka集群时,下午他就发了这个报错信息给我:1 partitions have leader brokers without a matching listener,including [gw651_downstream-0].
我打开虚拟机,去到kafka和zookeeper运行黑窗口中就看到了如下错误,想请问下是什么原因?我该怎么解决这个bug? :
其中一个zookeeper黑窗口发现如下信息:
java.io.IOException:远程主机强迫关闭了一个现有的连接.
at sun.nio.ch.SocketDispatcher.read0
at sun.nio.ch.SocketDispatcher.read
at sun.nio.ch.IOUtil.readIntoNativeBuffer
at sun.nio.ch.IOUtil.read
at sun.nio.ch.SocketChannelImpl.read
at org.apache.zookeeper.server.NIOServerCnxn.doIO
其中一个Kafka黑窗口有发现如下信息:
[error occurred during error reporting (nul1l). id 0xc0000005 ]
还有一个kafka黑窗口发现如下:
Caused by: java.io.I0Exception:存储空间不足,无法处理此命令.
at java.io.FileOutputStream.writeBytes
at java.io.FileOutputStream.write
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221>
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java-291)
at sun.nio.cs.StreamEncoder.implFlush
at sun.nio.cs.StreamEncoder.flush
at kafka.server.checkpoints.CheckpointFile.liftedTree1$1
at kafka.server.checkpoints.CheckpointFile.write
at kafka.server.checkpoints.0ffsetCheckpointFile.write
at kafka.server.ReplicaManager.$anonfun$checkpointHighWatermarks$8
.....
后面还有一句话:
WARN Stopping serving logs in dir C:\tmp\kafka-logs-2
ERROR Shutdown broker because all log dirs in C:\tmp\kafka-logs-2 have failed
1.命令:kafka-topics.sh --zookeeper localhost:2181 --describe --topic test600
Topic: test600 PartitionCount: 1 ReplicationFactor: 1 Configs:
Topic: test600 Partition: 0 Leader: none Replicas: 2 Isr: 2
2.命令:kafka-topics.bat --zookeeper localhost:2182 --describe --topic gw651_downstream
Topic: gw651_downstream PartitionCount: 1 ReplicationFactor: 1 Configs:
Topic: gw651_downstream Partition: 0 Leader: none Replicas: 1 Isr: 1