On Windows, TCP Ports are staying in TIME_WAIT State With docker setup even after client closing

[shanmuk-quartic]

On Windows, TCP Ports are staying in TIME_WAIT State With docker setup even after client closing

Let us say I open a client connection to scheduler and submitted a task and waited for result after operation completes, closed the task. Does this process open a new port?

On Linux this is working great but in windows, port is in TIME_WAIT state

Thank you all for your help

[guillaumeeb]

Hi @shanmuk-quartic, welcome to Dask community!

@shanmuk-quartic

Does this process open a new port?

Yes creating a Client connected to a Scheduler does open a new port for Client to Scheduler communications.

@shanmuk-quartic

On Linux this is working great but in windows, port is in TIME_WAIT state

How is this a problem for you? According to this post, it is normal to see TIME_WAIT state for 2 to 4 minutes after a connexion has been closed on Windows.