netstat CLOSE_WAIT

[kikingalgo]

Hi,

i am running a process that one of its instances appears on netstat command with CLOSE_WAIT status and another instance in ESTABLISHED status
Reading About the status Here
it says

CLOSE_WAIT
Indicates that the server has received the first FIN signal from the client and the connection is in the process of being closed

So this essentially means that his is a state where socket is waiting for the application to execute close()

A socket can be in CLOSE_WAIT state indefinitely until the application closes it.
Faulty scenarios would be like filedescriptor leak, server not being execute close() on socket leading to pile up of close_wait sockets

So where should we pin point this - CCXT exchange level ? or could this be a feed issue?