Removing target-domain-not-active special-case handling #4835
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
The suspicion is that this is not actually a transient and retriable error, so this should be handled differently
Pull Request Test Coverage Report for Build 0180db2d-a271-4951-aa73-e337f98c9e3a
💛 - Coveralls |
vytautas-karpavicius
approved these changes
May 19, 2022
mkolodezny
approved these changes
May 19, 2022
davidporter-id-au
deleted the
bugfix/correct-failover-issue-target-domain-not-active
branch
davidporter-id-au
added a commit
that referenced
this pull request
May 24, 2022
The suspicion is that this is not actually a transient and retriable error, so this should be handled differently
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.
The suspicion is that this is not actually a transient and retriable error, so this should be handled differently. It's currently causing some problems for the canary and domains which failover frequently.
The errors seen in the logs show 'target domain not active' repeatedly until the domain fails back. Seeming to indicate the problem isn't transient.
The suspicion is that this was checked in
39bebb464as an optimization for the cross-domain child-workflow feature. This is not a feature which is currently live.What changed?
How did you test it?
Potential risks
Release notes
Documentation Changes