这家伙太懒，什么都没留下
这家伙太懒，什么都没留下
你好 破案了，是代码没有catch异常。。。我真的~，结果存储程序出错后消费程序直接停在那里了。。。晕死 可能就是某一个设备上报的确实有错，因为他们是按顺序上报的，导致的有数据的总有，没有数据的总没。。。也算是一个教训
昨天还在想是不是因为多线程 merge into 导死锁了~~还是谢谢你了
我怀疑消费者代码那块的逻辑，重点排查下吧，看看消费者是否用了多线程导致的。
或者你直接拿官方的例子，什么也不要改，直接运行。
额 有点看不太懂~~
[root@jichao ~]# netstat -unltpa | grep 9092
tcp6 0 0 :::9092 :::* LISTEN 83611/java
tcp6 0 0 192.168.11.222:31349 192.168.11.222:9092 ESTABLISHED 84391/java
tcp6 0 0 192.168.11.222:31369 192.168.11.222:9092 ESTABLISHED 84568/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:33341 ESTABLISHED 83611/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:31369 ESTABLISHED 83611/java
tcp6 1 0 192.168.11.222:31211 192.168.11.222:9092 CLOSE_WAIT 83611/java
tcp6 0 0 192.168.11.222:33341 192.168.11.222:9092 ESTABLISHED 87966/java
tcp6 0 0 192.168.11.222:31371 192.168.11.222:9092 ESTABLISHED 84568/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:31347 ESTABLISHED 83611/java
tcp6 14 0 192.168.11.222:31347 192.168.11.222:9092 ESTABLISHED 84391/java
tcp6 0 0 192.168.11.222:31377 192.168.11.222:9092 ESTABLISHED 84568/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:31349 ESTABLISHED 83611/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:31377 ESTABLISHED 83611/java
tcp6 0 0 192.168.11.222:32747 192.168.11.222:9092 ESTABLISHED 86221/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:31375 ESTABLISHED 83611/java
tcp6 0 0 192.168.11.222:32749 192.168.11.222:9092 ESTABLISHED 86221/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:32747 ESTABLISHED 83611/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:32749 ESTABLISHED 83611/java
tcp6 0 0 192.168.11.222:9092 192.168.11.222:31371 ESTABLISHED 83611/java
tcp6 0 0 192.168.11.222:31375 192.168.11.222:9092 ESTABLISHED 84568/java
我粘出来
[root@jichao ~]# jps
52499 Bootstrap
84391 Bootstrap
84695 jar
88935 Jps
52567 Bootstrap
83289 QuorumPeerMain
84568 jar
83611 Kafka
86221 ConsoleConsumer
52349 Bootstrap
87966 ConsoleProducer
