[SERVER-4699] mongos can segfault after primary failover Created: 17/Jan/12 Updated: 11/Jul/16 Resolved: 17/Jan/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | 2.0.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| 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 |
|
If a primary fails during a shard version reset, it's possible for the master connection to be free'd and then re-used separately. |
| Comments |
| Comment by Greg Studer [ 17/Jan/12 ] |
|
Fix is in 2.0.3 : https://github.com/mongodb/mongo/commit/3eaa472e9a55c60b58446cc62c4ce3e5d420267e |