Welcome to the MongoDB Community Forums @Rajeev_Vishal !
Restarting members of a replica set should be unnecessary to ensure a database has been completely dropped.
Please provide some more details to help investigate the issue:
Is this is a standalone replica set, or part of a sharded cluster?
Did you run
db.dropDatabase() on the primary while it was part of the replica set?
What is your version of
mongo shell as reported by
What is your version of MongoDB server as reported by
What filesize in GB is displayed in the output of
show dbs for the databases you have dropped?
Have you queried to contents of these DBs to see what collections and documents are present?
This could be normal behaviour if you have processes which continue to insert data after a database has been dropped: a database will automatically be created if new data is being inserted.
There are other possibilities depending on your answers to the questions I’ve asked above.