[SERVER-12500] Metadata freeze command Created: 28/Jan/14  Updated: 06/Dec/22  Resolved: 13/Jan/22

Status: Closed
Project: Core Server
Component/s: Admin, Sharding
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Alexander Komyagin Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding EMEA
Participants:

 Description   

In sharded clusters some "advanced" maintenance operations like manual chunk rebalancing, performed by DBAs, can benefit from stopping the config metadata changes (i.e. balancer, splits).

It should be usable, something like sh.freeze() and sh.unfreeze(). Of course, if somebody calls this, they should be ready to handle the implications, e.g. jumbo chunks.

Currently you can shut down the second or the third config server to achieve the desired effect, but I'm hesitant to call it a solution.



 Comments   
Comment by Connie Chen [ 13/Jan/22 ]

Closing this because we have the sh.stopBalancer() command which does this today.

Generated at Thu Feb 08 03:28:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.