[SERVER-8270] gle doesn't distiguish between error types when finding errors Created: 22/Jan/13 Updated: 11/Jul/16 Resolved: 07/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.8, 2.2.2, 2.3.2 |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
... in some cases, think this can result in a faulty connection getting returned to the pool, resulting in multiple errors. |
| Comments |
| Comment by Greg Studer [ 07/Mar/14 ] |
|
Fixed by the rewrite of mongos GLE. |
| Comment by Greg Studer [ 23/Jan/13 ] |
|
To clarify - client_info.cpp::getLastError() has several try/catch blocks which just catch all std::exceptions and return the connections to the pool. If these are socket exceptions, we probably should not return the connection. |