Our application does not gracefully autoreconnect when a replica set member is added or removed (I'm not sure about voting/promotion events). I understand that the documentation states that either of these actions raises an AutoReconnect exception.

Our code uses the ReplicaSetConnection to make connections to the db. When a change is made to the replicaset, are there any scenarios where the pymongo driver and connection pool will "autoreconnect", or do we simply need to catch AutoReconnect and manage this ourselves?

Thanks