socket.connect does not appear to be thread safe about datadogpy HOT 4 CLOSED

Thank you for such a detailed feedback @mikejr !
We'll spend more time looking at this during the next few days to bring the appropriate modifications.

from datadogpy.

Hi @mikejr,

I have been running more tests, but I am unable to identify any thread safety related issue.
While running your snippet, I only see [Errno 61] Connection refused exception raised when socket.connect is used.

About [Errno 61] Connection refused

This message indicates that an ICMP Destination Unreachable response has been received in reply to a packet sent to an unbound port on the server.

This is an expected behavior here: in a "connected" mode, the socket would report (with enough delay to receive it) any ICMP response. Thus, I see the same exception when using a single thread and a few seconds wait between two socket.send calls. At the opposite, I see no exceptions, when socket.connect targets to a listening port.

@mikejr can you confirm that you are seing the same exception ? If so, we should investigate on the host side to understand why it becomes unreachable (defficient, restarting DogStatsd server ?).

Yann

from datadogpy.

@yannmh Yep, thats the same error and it does occur when DogStatsd is unavailable. I was trying to avoid spamming the logs when shutting down DogStatsd. Will take another route. Thanks for looking into it.

from datadogpy.

Thanks for confirming.
I am closing the issue. Please feel free to reopen if needed.

from datadogpy.