kafka代理处于CLOSE WAIT状态的TCP端口过多 [英] Too many TCP ports in CLOSE WAIT condition in kafka broker
问题描述
kafka代理中的TCP连接处于CLOSE_WAIT状态，导致kafka客户端中的DisconnectionException.
Too many TCP Connections are in CLOSE_WAIT status in a kafka broker causing DisconnectionException in kafka clients.
tcp6 27 0 172.31.10.143:9092 172.31.0.47:45138已建立-
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41612 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.0.47:45010 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.46.69:43000 CLOSE_WAIT-
tcp6 194 0 172.31.10.143:8080 172.31.20.219:45952 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.20.219:48006 CLOSE_WAIT-
tcp6 1 0 172.31.10.143:9092 172.31.0.47:44582 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.46.69:42828 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41934 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41758 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41584 CLOSE_WAIT-
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41852 CLOSE_WAIT-
tcp6 1 0 172.31.10.143:9092 172.31.0.47:44342 CLOSE_WAIT-
tcp6 27 0 172.31.10.143:9092 172.31.0.47:45138 ESTABLISHED -
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41612 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.0.47:45010 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.46.69:43000 CLOSE_WAIT -
tcp6 194 0 172.31.10.143:8080 172.31.20.219:45952 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.20.219:48006 CLOSE_WAIT -
tcp6 1 0 172.31.10.143:9092 172.31.0.47:44582 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.46.69:42828 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41934 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41758 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41584 CLOSE_WAIT -
tcp6 25 0 172.31.10.143:9092 172.31.46.69:41852 CLOSE_WAIT -
tcp6 1 0 172.31.10.143:9092 172.31.0.47:44342 CLOSE_WAIT -
debezium错误
Error in debezium
connect-prod |2019-02-14 06:28:54,885信息||[Consumer clientId = consumer-3，groupId = 4]将提取请求(sessionId = 1727876188，epoch = INITIAL)发送到节点2时出错:org.apache.kafka.common.errors.DisconnectException.[org.apache.kafka.clients.FetchSessionHandler] connect-prod |2019-02-14 06:28:55,448信息||[Consumer clientId = consumer-1，groupId = 4]将提取请求(sessionId = 1379896198，epoch = INITIAL)发送到节点2时出错:org.apache.kafka.common.errors.DisconnectException.[org.apache.kafka.clients.FetchSessionHandler]
connect-prod | 2019-02-14 06:28:54,885 INFO || [Consumer clientId=consumer-3, groupId=4] Error sending fetch request (sessionId=1727876188, epoch=INITIAL) to node 2: org.apache.kafka.common.errors.DisconnectException. [org.apache.kafka.clients.FetchSessionHandler] connect-prod | 2019-02-14 06:28:55,448 INFO || [Consumer clientId=consumer-1, groupId=4] Error sending fetch request (sessionId=1379896198, epoch=INITIAL) to node 2: org.apache.kafka.common.errors.DisconnectException. [org.apache.kafka.clients.FetchSessionHandler]
这可能是什么原因?
推荐答案
看来这是Kafka 2.1.0中的一个已知问题.
It appears that this is a known issue in Kafka 2.1.0.
https://issues.apache.org/jira/browse/KAFKA-7697
我认为停在Close_wait中的连接是真正问题的副作用.
I think the connections stuck in Close_wait is a side effect of the real problem.
此问题已在Kafka 2.1.1版中修复，应在几天内发布.期待它.
This issue has been fixed in Kafka version 2.1.1 which should be released in a few days. Looking forward to it.
这篇关于kafka代理处于CLOSE WAIT状态的TCP端口过多的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
