Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.2.1, 2.3.0
Affects Version/s: 2.2.0
Component/s: None
Labels:
None

Operating System:
ALL
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

(1 is duplicated by)

Assignee:: Randolph Tan
Reporter:: Greg Studer (Inactive)
Participants:: auto, Greg Studer, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Sep 18 2012 05:46:45 PM UTC
Updated:: Jul 11 2016 05:58:21 PM UTC
Resolved:: Sep 18 2012 09:24:43 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates