Hi,
We have 6 replicasets used in our production environment and we are seeing at odd times the following error in our application logs

Exception: Failed on findOne(): 16340 No replica set monitor active and no
cached seed found for set: rs5

I can't find a reference to this error code or message, so putting in a ticket hoping someone can help us understand what happens. This usually fails and recovers 10-20 minutes later.

When this happens, we check and the replica set is alive and healthy.

We are using the c++ driver and using mongo 2.2