Details
-
Bug
-
Status: Open
-
Blocker
-
Resolution: Unresolved
-
1.5.2
-
None
-
None
Description
in 84,it the flume ha
[root@usercenter ~]# lsof -p 3079 | grep 172.30.128.163
java 3079 root 87r IPv6 23280619 0t0 TCP 172.30.129.84:9520->172.30.128.163:33696 (ESTABLISHED)
java 3079 root 89r IPv6 23323364 0t0 TCP 172.30.129.84:9520->172.30.128.163:11565 (ESTABLISHED)
java 3079 root 160u IPv6 23331501 0t0 TCP 172.30.129.84:9520->172.30.128.163:14120 (ESTABLISHED)
java 3079 root 163u IPv6 23301662 0t0 TCP 172.30.129.84:9520->172.30.128.163:48763 (ESTABLISHED)
in 163 ,it's the flume client
tcp 0 0 ::ffff:172.30.128.163:14120 ::ffff:172.30.129.84:9520 ESTABLISHED 7348/java off (0.00/0/0)
only one connection
and in the log of 84:
tcp 0 0 ::ffff:172.30.128.163:14120 ::ffff:172.30.129.84:9520 ESTABLISHED 7348/java off (0.00/0/0)
by the source code
private void destroyConnection() {
if (client != null) {
logger.debug("Rpc sink {} closing Rpc client: {}", getName(), client);
try
catch (FlumeException e)
{ sinkCounter.incrementConnectionFailedCount(); logger.error("Rpc sink " + getName() + ": Attempt to close Rpc " + "client failed. Exception follows.", e); }}
client = null;
}
I think it calls the close method,it means the client disconnect with server,but the netstat command shouws the server also has the useless connection with client.