[SERVER-16877] dataSize command doesn't report some errors Created: 15/Jan/15 Updated: 18/Feb/16 Resolved: 18/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.8.0-rc5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
If the collection scan fails, we just log a warning "Internal error while reading" and then the command returns possibly incomplete or erroneous results with no error indication. |
| Comments |
| Comment by David Storch [ 18/Feb/16 ] |
|
Closing as a duplicate of |
| Comment by Tess Avitabile (Inactive) [ 28/Jan/16 ] |
|
There's a second issue here that dataSize is erroneously logging an error when maxObjects is passed. |
| Comment by J Rassi [ 15/Jan/15 ] |
|
This is |
| Comment by Eric Milkie [ 15/Jan/15 ] |
|
The datasize2.js test actually hits this condition, but the test still passes. |