[SERVER-84527] Rename misleading stat names once multiple open buckets per metadata are allowed Created: 03/Jan/24 Updated: 05/Feb/24 Resolved: 05/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Damian Wasilewicz | Assignee: | Damian Wasilewicz |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Currently there are a number of statistics associated with buckets closing that might become misleadingly named once multiple open buckets per metadata are allowed. We should investigate which exact stat names become misleading once this feature is added, and update their names. |
| Comments |
| Comment by Gregory Wlodarek [ 05/Feb/24 ] |
|
We're dropping the property that compressed buckets are sorted by time. So we no longer need to support multiple open buckets per metadata. Closing as won't do. |