[SERVER-20448] allow sharding.autoSplit to be set at runtime Created: 17/Sep/15  Updated: 06/Dec/22  Resolved: 28/Jul/17

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

Type: Improvement Priority: Major - P3
Reporter: Andre de Frere Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-24227 Replace the autoSplit startup option ... Closed
related to SERVER-24604 Add doAutoSplit to config.settings Closed
is related to SERVER-9287 Decision to split chunk should happen... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently it is necessary to restart a mongos if you wish to change the sharding.autoSplit/--noAutoSplit behaviour.

There are some cases where temporarily preventing auto splits from occurring makes sense (like large data loads, where large numbers of splits/splitVectors may not be helpful, and the same result can be achieved by a final split), but currently this is cumbersome (as it requires nodes to be restarted).



 Comments   
Comment by Randolph Tan [ 28/Jul/17 ]

Made obsolete by SERVER-24227

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