[SERVER-34449] Handle upgrade/downgrade for autosplitting logic Created: 12/Apr/18  Updated: 29/Oct/23  Resolved: 09/Aug/18

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

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-08-13
Participants:

 Description   

Say we change autosplitting logic to occur on mongod in version V2 and version V1 uses autosplitting logic on mongos. If we have a cluster with mixed mongos and mongod versions, e.g. mongos is V1 and mongod is V2, we'll want to turn off the autosplitting logic in mongod so splits aren't initiated from two different places



 Comments   
Comment by Githook User [ 09/Aug/18 ]

Author:

{'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com', 'username': 'saltzm'}

Message: SERVER-34448 Enable autosplitting on the shard and disable on mongos

SERVER-34449 Handle upgrade/downgrade logic for autosplitting on shard

SERVER-34448 Wait for chunk splitting in top chunk optimization tests

SERVER-34448 Require persistence in shard_existing_coll_chunk_count.js
Branch: master
https://github.com/mongodb/mongo/commit/da38575dde0a316c30d6579fa61a8c64376a4062

Generated at Thu Feb 08 04:36:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.