[SERVER-2177] Expose stats for number of moves during an update (not in-place) per collection Created: 06/Dec/10 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Performance, Tools |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | metrics, mmapv1, stats | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
It would be good to expose the number of moves required for each collection. This will help in diagnosing problems of constantly growing docs when it might not have been expected. Once the paddingFactor is adjustable per collection this will also be a useful stats for helping understand when to tune that. Expose this in mongostat (in an extended/advanced mode?). |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 10/Apr/11 ] |
|
It would also be good to include this number with the results of getLastError after an update. |