[SERVER-7061] mongos can use invalid ptr to master conn when setShardVersion fails Created: 18/Sep/12 Updated: 11/Jul/16 Resolved: 18/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.2.1, 2.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by auto [ 18/Sep/12 ] |
|
Author: {u'date': u'2012-09-18T13:23:32-07:00', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: |
| Comment by auto [ 18/Sep/12 ] |
|
Author: {u'date': u'2012-09-18T13:23:32-07:00', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: |