-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust documentation based on new load balancer support. #212
Conversation
Can't spot any differences other than additional newlines. |
coordinator, so the requests can be answered correctly without any additional | ||
configuration. However, this incurs a small performance penalty due to the extra | ||
request across the internal network. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ewoutp The paragraph above is the main change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. We should also adjust the 2 paragraphs below, since they will no longer be needed, unless you want to avoid a small latency penalty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need some text tweaks and then wait for the change to be available in a release,
coordinator, so the requests can be answered correctly without any additional | ||
configuration. However, this incurs a small performance penalty due to the extra | ||
request across the internal network. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. We should also adjust the 2 paragraphs below, since they will no longer be needed, unless you want to avoid a small latency penalty.
|
||
ArangoDB will transparently forward any mismatched requests to the correct | ||
coordinator, so the requests can be answered correctly without any additional | ||
configuration. However, this incurs a small performance penalty due to the extra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest to replace performance by latency
The load balancer support is currently in devel in the main repo. It will be back-ported to 3.3 for sure, but has not been done yet. Do the docs here apply for 3.3? 3.2?