Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

how to avoid CLOSE_WAIT on the ambari-server

Highlighted

how to avoid CLOSE_WAIT on the ambari-server

hi all

when we run the


netstat -nape | grep -i close


on the ambari server machine , we see many CLOSE_WAIT

the pid - 1998 represented the YARN

and pid 8344 - represented the mapred


netstat -nape | grep -i close
tcp        1      0 197.23.12.36:42977       197.23.12.68:50010       CLOSE_WAIT  1013       30780754   8344/java
tcp        1      0 197.23.12.36:43148       197.23.12.62:50010       CLOSE_WAIT  1013       30778553   8344/java
tcp        1      0 197.23.12.36:42959       197.23.12.68:50010       CLOSE_WAIT  1013       30759752   8344/java
tcp6       1      0 197.23.12.36:36606       197.23.12.35:8188        CLOSE_WAIT  1011       524012     1998/java
tcp6       1      0 197.23.12.36:36592       197.23.12.35:8188        CLOSE_WAIT  1011       526356     1998/java
tcp6       1      0 197.23.12.36:36591       197.23.12.35:8188        CLOSE_WAIT  1011       517442     1998/java
tcp6       1      0 197.23.12.36:36579       197.23.12.35:8188        CLOSE_WAIT  1011       520633     1998/java
tcp6       1      0 197.23.12.36:52152       197.23.12.35:8188        CLOSE_WAIT  1011       562004     1998/java
tcp6       1      0 197.23.12.36:36588       197.23.12.35:8188        CLOSE_WAIT  1011       522512     1998/java
tcp6       1      0 197.23.12.36:36584       197.23.12.35:8188        CLOSE_WAIT  1011       520634     1998/java
tcp6       1      0 197.23.12.36:36590       197.23.12.35:8188        CLOSE_WAIT  1011       522513     1998/java
tcp6       1      0 197.23.12.36:36589       197.23.12.35:8188        CLOSE_WAIT  1011       511322     1998/java
tcp6       1      0 197.23.12.36:36586       197.23.12.35:8188        CLOSE_WAIT  1011       511321     1998/java
tcp6       1      0 197.23.12.36:36607       197.23.12.35:8188        CLOSE_WAIT  1011       520635     1998/java
tcp6       1      0 197.23.12.36:36602       197.23.12.35:8188        CLOSE_WAIT  1011       526357     1998/java
tcp6       1      0 197.23.12.36:36587       197.23.12.35:8188        CLOSE_WAIT  1011       524009     1998/java
tcp6       1      0 197.23.12.36:36593       197.23.12.35:8188        CLOSE_WAIT  1011       524010     1998/java
tcp6       1      0 197.23.12.36:36603       197.23.12.35:8188        CLOSE_WAIT  1011       522137     1998/java 

my question , how we can avoid this CLOSE_WAIT ? on our ambari server ?

more details

197.23.12.36 - is the mabari server ( master2 )

197.23.12.35 - is the master1 machine

On master1/master2 - we have the active/standby resource manager

and App Timeline Server on master1

* just note , I guess if we restart the YARN or the mapred , then CLOSE_WAIT will gone , but this isn't solution , and we checked also the free memory and it is ok on the ambari server

Michael-Bronson
1 REPLY 1
Highlighted

Re: how to avoid CLOSE_WAIT on the ambari-server

New Contributor

hi Michael Bronson, have you fixed it? I have the same question. look forward to your reply109791-屏幕快照-2019-07-04-下午54224.png

Don't have an account?
Coming from Hortonworks? Activate your account here