chore(conf) update default C* policy to 'RequestRoundRobin' #4004
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
Introduced in 0.14, this new LB policy has been used in the wild and should be considered stable. Since, in the context of Kong, this LB policy has no downside and can potentially significantly reduce latency, it is appropriate to use it as the default policy for 1.0. This ensures that Kong is optimally configured from the get-go, as several complaints about C* queries latency could have been mitigated by this policy (although it is not the largest factor in those complaints). By ensuring a given request reuses an existing connection, we avoid additional handshake time (greatly worsened by SSL and authentication if configured), and ensure consistency of data throughout the request.
bungle
added
the
pr/ready
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.
Introduced in 0.14, this new LB policy has been used in the wild and
should be considered stable. Since, in the context of Kong, this LB
policy has no downside and can potentially significantly reduce latency,
it is appropriate to use it as the default policy for 1.0. This ensures
that Kong is optimally configured from the get-go, as several complaints
about C* queries latency could have been mitigated by this policy
(although it is not the largest factor in those complaints).
By ensuring a given request reuses an existing connection, we avoid
additional handshake time (greatly worsened by SSL and authentication if
configured), and ensure consistency of data throughout the request.