From 0e9392409e25fc22c420d4e89bc3801c2e8b91ed Mon Sep 17 00:00:00 2001 From: Arnob Kumar Saha Date: Wed, 27 Sep 2023 04:00:07 +0600 Subject: [PATCH] Mongo configServer should have at least 3 repliacs (#275) Signed-off-by: Arnob kumar saha --- docs/addons/mongodb/sharding/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/addons/mongodb/sharding/index.md b/docs/addons/mongodb/sharding/index.md index ec9ee927..e5c1783a 100644 --- a/docs/addons/mongodb/sharding/index.md +++ b/docs/addons/mongodb/sharding/index.md @@ -90,6 +90,8 @@ $ kubectl apply -f https://github.com/stashed/docs/raw/{{< param "info.version" mongodb.kubedb.com/sample-mgo-sh created ``` +MongoDB [recommends](https://www.mongodb.com/docs/manual/core/replica-set-members/#replica-set-members) that there should be at least 3 replicas for a replicaSet configuration. For a sharded MongoDB setup, a secondary configserver is locked while running `mongodump` utility for backup. This can result in various issues like sharding commands get stucked, primary-secondary syncing issue etc. So, ensure at least 3 configServer replicas by specifying >= 3 replicas in `.spec.shardTopology.configServer.replicas` field. + KubeDB will deploy a MongoDB database according to the above specification. It will also create the necessary secrets and services to access the database. Let's check if the database is ready to use,