[SERVER-8617] db.stats(scale) and db.collection.stats(scale) are inconsistent w.r.t. "avgObjSize" Created: 19/Feb/13 Updated: 23/Jul/15 Resolved: 21/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Michael Haren | Assignee: | Unassigned |
| 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 |
|
When I run
Each result is in kilobytes except avgObjSize. For that field, db.stats() and db.stats(1024) produce the exact same unscaled number. When I run
however, avgObjSize is scaled correctly. The value should be scaled by both commands. |
| Comments |
| Comment by Ramon Fernandez Marina [ 21/Jul/15 ] |
|
mharen, my colleagues point out that this is an intentional behavior to avoid displaying things like "avgObjSize: 0.0000000321", and this is reflected in the documentation. Regards, |