Hi @Debalina_Saha and welcome to MongoDB community forums!!
As mentioned in the MongoDB documentation:
Each sharded cluster must have its own config servers. Do not use the same config servers for different sharded clusters.
It’s important to note that applying administrative operations could potentially have an impact on the performance of the sharded cluster. In this particular case, we would like to suggest considering the use of more than one config server to handle any potential performance impacts that may arise from the deployment. This could help to mitigate any potential issues and ensure that the cluster continues to run smoothly.
Also, the forum post mentions a workaround solution for the similar issue.
If the above recommendations does not work, could you help us with the output for the following:
- sh.status() during the timeout.
- rs.status() from the primary shard server.
- Also could you share details on VM setup and how has the deployment been created.
Regards
Aasawari