[SERVER-4279] Mongos does not throw/handle cursor timeouts Created: 14/Nov/11 Updated: 01/Feb/12 Resolved: 01/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ryan Nitz | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
If you open a cursor with a timeout value to a mongos and it takes more than the timeout value to walk the cursor and then it moves to another shard, mongos aborts the cursor and does not properly notify the drivers the timeout has occurred (silent failure). From the driver perspective, it receives an empty object and then closes the cursor. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 01/Feb/12 ] |