[SERVER-64810] Setting granularity values of timeseries collections on shards to invalid entries Created: 22/Mar/22 Updated: 26/Jun/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Rui Liu | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | techdebt, time-series | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Sprint: | Execution Team 2023-05-01, Execution Team 2023-05-15, Execution Team 2023-05-29 |
| Participants: |
| Description |
|
Once the time series collection is sharded, we will no longer make use of the granularity values on the shards, but will read the values saved on the config server instead. We could make this behaviour more explicit by setting the values on the shards to invalid entries so that usage of granularity values on shards will fail. |
| Comments |
| Comment by Henrik Edin [ 09/Jun/23 ] |
|
Sending this to the backlog. I do not believe this is causing any issues apart from being confusing and potentially error-prone. |
| Comment by Ana Meza [ 05/Sep/22 ] |
|
Removing Sprint since this is a ticket in the Backlog |