[SERVER-12689] Improve log message when capped cursor is overrun Created: 12/Feb/14 Updated: 06/Dec/22 Resolved: 02/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Ben Becker | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Description |
|
When a capped cursor is overrun, the following warning is displayed on the server:
Perhaps it's not worth warning in the case of an overrun, given that this is the nature of a capped collection (and the client can interpret an empty result set with a dead cursor as a possible indicator of this state). If it is worth logging something, it would be helpful to explicitly state why the cursor was invalidated. |
| Comments |
| Comment by David Storch [ 02/Feb/16 ] |
|
This was fixed under |