Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow configuration of workers to back off completely if the server is not available
See original GitHub issueIs your feature request related to a problem? Please describe.
I want the workers to stop trying to connecting to the server if the server is not available using WorkflowServiceStubsOptions
Describe the solution you’d like I’d like to configure workers to stop polling/trying to connecting to the server if the server is not available after a specified time period.
Describe alternatives you’ve considered N/A
Additional context Slack discussion https://temporalio.slack.com/archives/CTT84KXK9/p1620663515093300
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we may have both backoff and a parameter that specifies maximum retry period after which we give up and kill the worker. I can see situations where both types of behavior might be desirable based on the specifics of the deployment infrastructure being used.
@eminn Will implement health check. This has already been done in Go SDK see client.go#L417