Remember seed uri and DNS-lookup during rediscovery #220
Conversation
This file contains hidden or 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
Routing driver now memorizes seed router uri that was used on driver creation. It is later used as a fallback in case no existing routers respond during rediscovery. Also DNS resolution of this seed uri is performed if platform supports DNS lookup (only NodeJS, functionality not available in browser). This functionality is useful when seed address exists in DNS record and does not correspond to any causal cluster member. Such setup allows driver to switch to a completely different causal cluster using DNS record manipulations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Routing driver now memorizes seed router uri that was used on driver creation. It is later used as a fallback in case no existing routers respond during rediscovery. Also DNS resolution of this seed uri is performed if platform supports DNS lookup (only NodeJS, functionality not available in browser).
This functionality is useful when seed address exists in DNS record and does not correspond to any causal cluster member. Such setup allows driver to switch to a completely different causal cluster using DNS record manipulations.