[SERVER-50944] Add number of chunks and estimated routing table size to serverStatus metrics Created: 15/Sep/20 Updated: 16/Nov/21 Resolved: 16/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Dmitry Agranat | Assignee: | Garaudy Etienne |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
This information would better help us troubleshooting sharding related issues, especially related to memory consumption. |
| Comments |
| Comment by Kaloian Manassiev [ 16/Nov/21 ] |
|
Judging by the linked ticket, the router running out of memory would be a rare occurrence caused by a very specific bug, which has now been fixed. Furthermore, we're currently working on PM-2321 to reduce routing table size and after that PM-2323 will do away with the concept of chunks. After those two projects, the routing table size will no longer be an issue. This would be throw-away work and we can't spare an iteration for that, unfortunately. For the purposes of seeing trends in the size of customers' routing tables after these two projects complete, we don't need them at the granularity of FTDC and one record per day would be sufficient. |