Add paragraph on not using a load balancer #36999
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
The transport client validates that each time it connects to a particular address it reaches the same node. This means that it does not support a simple load balancer which exposes multiple nodes at a single address. This change calls this situation out explicitly in the docs. Relates elastic#30141.
DaveCTurner
added
>docs
|
Pinging @elastic/es-core-infra |
|
NB only targeted at branches 5.6 to 6.3 - this restriction no longer applies in 6.4+. |
|
run oss docs tests |
tlrx
approved these changes
Jan 7, 2019
DaveCTurner
added a commit
that referenced
this pull request
Jan 7, 2019
The transport client validates that each time it connects to a particular address it reaches the same node. This means that it does not support a simple load balancer which exposes multiple nodes at a single address. This change calls this situation out explicitly in the docs. Relates #30141.
DaveCTurner
added a commit
that referenced
this pull request
Jan 7, 2019
The transport client validates that each time it connects to a particular address it reaches the same node. This means that it does not support a simple load balancer which exposes multiple nodes at a single address. This change calls this situation out explicitly in the docs. Relates #30141.
DaveCTurner
added a commit
that referenced
this pull request
Jan 7, 2019
The transport client validates that each time it connects to a particular address it reaches the same node. This means that it does not support a simple load balancer which exposes multiple nodes at a single address. This change calls this situation out explicitly in the docs. Relates #30141.
DaveCTurner
added a commit
that referenced
this pull request
Jan 7, 2019
The transport client validates that each time it connects to a particular address it reaches the same node. This means that it does not support a simple load balancer which exposes multiple nodes at a single address. This change calls this situation out explicitly in the docs. Relates #30141.
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 transport client validates that each time it connects to a particular
address it reaches the same node. This means that it does not support a simple
load balancer which exposes multiple nodes at a single address. This change
calls this situation out explicitly in the docs.
Relates #30141.