[SERVER-67646] Move `config.rangeDeletions` index creation into RangeDeleterService Created: 29/Jun/22 Updated: 16/Sep/22 Resolved: 16/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Silvia Surroca |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm-2849-optimizations | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding EMEA 2022-09-19 | ||||||||
| Participants: | |||||||||
| Description |
|
As part of the effort to remove the dependencies of the range-deleter from the sharding codebase, the index creation for config.rangeDeletions should be included in the RangeDeleterService. One possible way to complete this task would be to create the index on service's startup , checking the cluster role to skip the creation if the node is NOT a shard server. |
| Comments |
| Comment by Silvia Surroca [ 16/Sep/22 ] |
|
As an outcome of an internal discussion we have agreed that current implementation is as valid as the proposed one. So change has been dropped. |