shubhamb12
shubhamb12
Hi, Thanks for the response. The problem is we have around 400 pipelines and this issue has never creeped up for any of them. Infact for this particular pipeline this...
Btw if I disable the statsd client with noopsstatsD there is no error. So this error specifically originates from this lib
The statsD is already as init step on job graph creation. I am not sure where else we can init it.
Is there a way I can gracefully handle this exception ? The io interruption is breaking the application and then Job can never boot again Also I have added the...