WARN Attempting to send response via channel for which there is no open connection

在kafka屏幕输出中。可以看到很多这样的警告不知道这是什么意思。如何解决
还有关于zookeeper的问题。我有5个节点的集群 23,24,25,26,27在日志中可以看到很多

2019-05-20 05:47:19,665 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0169 with negotiated timeout 30000 for client /10.3.87.23:57553
2019-05-20 06:32:57,958 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea016a with negotiated timeout 30000 for client /10.3.87.23:34304
2019-05-20 06:38:01,912 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea016b with negotiated timeout 30000 for client /10.3.87.23:19989
2019-05-20 06:43:05,789 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea016c with negotiated timeout 30000 for client /10.3.87.23:56055
2019-05-20 07:18:35,354 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea016d with negotiated timeout 30000 for client /10.3.87.23:45158
2019-05-20 07:49:00,969 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea016e with negotiated timeout 30000 for client /10.3.87.23:45014
2019-05-20 08:09:17,947 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea016f with negotiated timeout 30000 for client /10.3.87.23:14279
2019-05-20 08:34:16,129 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0170 with negotiated timeout 30000 for client /10.3.87.23:57366
2019-05-20 08:34:16,153 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0171 with negotiated timeout 30000 for client /10.3.87.23:57384
2019-05-20 08:34:16,164 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0172 with negotiated timeout 30000 for client /10.3.87.23:57392
2019-05-20 08:34:16,179 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0173 with negotiated timeout 30000 for client /10.3.87.23:57400
2019-05-20 08:34:16,183 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0174 with negotiated timeout 30000 for client /10.3.87.23:57402
2019-05-20 08:39:45,161 [myid:1] - INFO  [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0175 with negotiated timeout 30000 for client /10.3.87.23:56001

不知道在那里找原因






发表于: 26天前   最后更新时间: 26天前   游览量:256
上一条: 到头了!
下一条: 已经是最后了!

  • 而且都是指向23这台机器
    • 这是正常info信息呀,影响功能吗?
      你在看看防火墙有开吗?有的防火墙配置看到一个连接连接时间过长 就给kill了。
        • 你说的是kafka的警告是正常的,还是说zookeeper的那个是正常的。我认为zookeeper报这么多的timeout应该不正常的,时长长达30秒
            • WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@373] - Exception causing close of session 0x0 due to java.io.IOException: Len error 1195725856
              今天还发现在23这台机器上报了几个这样的错。网上说是3.4.6的BUG。我的zookeeper的版本是3.4.10
              其他的机器我没发现有这个错误
                • 现在没有发现影响业务,频率上没有一个固定。10分钟 20分钟等出现一次。不知道这个东西是那里来的。防火墙没有做任务策略。只是kafka运行一段时间就会出错误。不知道和这个东西有没有关系
                    • 去的kafka中也经常有
                      [2019-05-21 09:45:04,120] WARN Attempting to send response via channel for which there is no open connection, connection id 7 (kafka.network.Processor)
                      [2019-05-21 09:45:11,446] WARN Attempting to send response via channel for which there is no open connection, connection id 0 (kafka.network.Processor)
                      [2019-05-21 09:45:25,075] WARN Attempting to send response via channel for which there is no open connection, connection id 7 (kafka.network.Processor)
                      [2019-05-21 09:50:02,121] WARN Attempting to send response via channel for which there is no open connection, connection id 0 (kafka.network.Processor)
                      [2019-05-21 09:50:13,734] WARN Attempting to send response via channel for which there is no open connection, connection id 5 (kafka.network.Processor)
                        • 客户端与kafka之间,客户端是否当没消息的时候,会销毁,有消息时,重新建立链接的操作。
                          之前反复刷屏告警,是因为zk版本与kafka之间不兼容,导致无法注入进去,导致反复告警,普通告警可以忽视的。
                            • 我现在重启了一下zookeeper
                              2019-05-20 08:39:45,161 [myid:1] - INFO [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aa72e41ea0175 with negotiated timeout 30000 for client /10.3.87.23:56001
                              这样的警告少了很多。但感觉我的zookeeper集群的连接数不平衡,有的节点14连接,有的节点4个连接,有的只有1个连接
                              kafka中的
                              WARN Attempting to send response via channel for which there is no open connection
                              这样的警告还是有很多
                                • 这个超时的时间和我的消费端程序设的超时是一样的但是。我在23,24,25这三台机器都有消费程序。为什么只有23的超时呢。还有日志中有26的超时。但26上没有消费程序啊。不过26的报错很少只有2-3条,其他的全是23上的报错
                                    • 我把超时的时间收集了一下
                                      09:02:45,649
                                      09:07:49,434
                                      09:12:53,758
                                      09:17:57,563
                                      09:23:01,415
                                      09:28:05,307
                                      09:33:09,181
                                      09:38:12,959
                                      09:43:17,034
                                      09:48:20,896
                                      09:53:24,488
                                      09:58:28,532
                                      感觉像是每5分钟一次。又有点像是kafka的一个管理工具
                                        • 我装的是kafka eagle这个东西是5分钟取一次数据。好像以后我关过一次。但还是有超时。它的github上也没说有关timeout的事情
                                            • 2019-05-31 15:58:06,630 [myid:1] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@192] - Accepted socket connection from /10.3.87.23:23860
                                              2019-05-31 15:58:06,633 [myid:1] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@942] - Client attempting to establish new session at /10.3.87.23:23860
                                              2019-05-31 15:58:06,636 [myid:1] - INFO [CommitProcessor:1:ZooKeeperServer@687] - Established session 0x16aedd2b8a100da with negotiated timeout 30000 for client /10.3.87.23:238
                                              60
                                              2019-05-31 15:58:08,969 [myid:1] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1044] - Closed socket connection for client /10.3.87.23:23860 which had session
                                              id 0x16aedd2b8a100da

                                              从日志来看像是连上来以后马上超时。这不可能应该要30称以后在才超时啊