Closed mew1033 closed 2 years ago
I've been running with these changes on my copy of the sdk for the past 3 weeks and it has completely solved my connection reset problem. I'm not sure what else should be tested, but this is working and working well for me.
Any comments here? This has definitely helped with my processes.
Hi @mew1033, we unfortunately have not had a chance to look at this PR due to resource constraints. I will personally see if we can get this merged in sooner rather than later. Thank you for your patience and understanding.
@shakeelmohamed Sounds good. Thank you for your response. I'll keep using my patched version for now.
@shakeelmohamed Just wanted to follow up on this PR. Any chance of getting it merged? I Just rebased to current develop.
Hi @mew1033 thank you for your PR. We have had a look at the changes and just wanted to check with you the reason behind keeping the default retry time to 10s. Also would request to resolve the conflicts as well as see if you can add a unit test for the changes. Thank you for your patience and understanding.
I have a long running process that connects to Splunk and executes and manages multiple jobs over (potentially) hours. Every now and then I'll get a
Connection reset by peer
error that blows everything up. This should allow me to build my Splunk connection object with a little retry logic built into the sdk.Traceback I'm getting for reference: