Mongos can crash if an error occurs with a replica set while trying to set the shard version - because checkShardVersion uses the legacy masterConn() call, it retains a pointer to the now-invalid connection.
Potential fix is to retry not with the same connection but with the replica set connection object.
- is duplicated by
-
SERVER-7093 Mongos crashed because of "got not master" with signal 11
- Closed
-
SERVER-6539 Mongos crashed because of mongod cannot reach.
- Closed
-
SERVER-7029 Mongos crash on replica set failover
- Closed
-
SERVER-7564 mongos crash (segfault) under load
- Closed
-
SERVER-7043 mongos crashes on shard failover during migration
- Closed
-
SERVER-8074 mongos segfault on replica set member shutdown
- Closed