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,