[SERVER-22299] Add a jstest that runs moveChunk directly against a mongod that is not yet sharding aware, providing an SCCC connection string for the config servers Created: 25/Jan/16  Updated: 19/Nov/16  Resolved: 18/Feb/16

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

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: code-and-test, csrsupgrade
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding F (01/29/16), Sharding 10 (02/19/16), Sharding 11 (03/11/16)
Participants:

 Description   

Write a test that uses moveChunk to initialize the sharding state on a mongod, but uses an SCCC connection string for the config servers, even though the config servers are actually in CSRS mode, to force the mongod to perform the in-memory upgrade process from SCCC mode to CSRS mode.



 Comments   
Comment by Githook User [ 18/Feb/16 ]

Author:

{u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}

Message: SERVER-22299 add test to verify mongod upgrades to csrs mode on receiving moveChunk with SCCC string
Branch: v3.2
https://github.com/mongodb/mongo/commit/df017739cf9da74e796b74a9cc1e0640f52e3121

Comment by Spencer Brody (Inactive) [ 25/Jan/16 ]

Trickiest part of writing a test that runs moveChunk directly against a mongod will be figuring out the right params need to be sent since the mongod version of moveChunk is usually only run by a mongos, which will include things like the shard key. jstests/sharding/split_chunk.js has an example of running split directly against a mongod, which has some of these same problems, so could probably be an example of how to solve some of the problems, like finding out the write chunkVersion to send.

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