-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
v8.2, v8.0
-
ClusterScalability Jan5-Jan19, ClusterScalability 19Jan-2Feb, ClusterScalability 2Feb-16Feb
-
(copied to CRM)
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Today, when a cluster transitions from embedded to dedicated config servers we use transitionToDedicatedConfigServer() which uses removeShard().
We drain sharded collections and then use range deletions to remove any data from the embedded config server safely in case it gets added back to the cluster as a config shard. For any other removeShard operation, we don't complete range deletions because the shard will be removed.
Waiting on range deletions to transition to dedicated config servers is unnecessary. Atlas cannot complete the transition and reduce the tier to an M30 for a config server until range deletions are complete which can be very slow and resource intensive.
- causes
-
SERVER-119117 Exclusion of pending range deletions in transition to dedicated progress check can cause commit to fail
-
- Closed
-
- is depended on by
-
TOOLS-4077 Investigate changes in SERVER-103990: Skip range deletions when transitioning from embedded to dedicated config servers
-
- Closed
-
- is related to
-
SERVER-77359 Allow enabling/disabling the range deleter at runtime
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Blocked
-