-
Notifications
You must be signed in to change notification settings - Fork 86
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
Feature/zenko 4641 #2183
base: development/2.10
Are you sure you want to change the base?
Feature/zenko 4641 #2183
Conversation
Hello williamlardier,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
1c9b222
to
6e8d62e
Compare
6e8d62e
to
14e4884
Compare
This will help not having two mongos servers on the same node. Issue: ZENKO-4641
We do not want to have N shard server for N nodes, because it would divide the total available resources per shard, reducing the available memory: we should reduce the need to rely on the disks as much as possible to improve the performances, as per official recommendations. Issue: ZENKO-4641
WIP
Please review https://scality.atlassian.net/wiki/spaces/OS/pages/2892824661/Artesca+XDM+with+multiple+MongoDB+shards+phase+1 before this PR.