Use max join time as start timeout #3911
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yiminc
approved these changes
Feb 7, 2023
dnr
approved these changes
Feb 7, 2023
Co-authored-by: David Reiss <dnr@dnr.im>
yux0
added a commit
that referenced
this pull request
Feb 7, 2023
* Use max join time as start timeout
|
Will this PR make it into the next release and if so do you know the timeline for that? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Use max join time as start timeout.
Why?
https://github.com/uber-go/fx/pull/875/files
Fx fix the context timeout error. The server start timeout could be too short.
How did you test it?
local test:
./temporal-server --env development-cass --allow-no-auth start --service frontendPotential risks
Is hotfix candidate?
Consider for #3826