[SERVER-24558] Shard variant of 'moveChunk' should not check for exact collection version Created: 14/Jun/16  Updated: 05/Jul/16  Resolved: 14/Jun/16

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 16 (06/24/16)
Participants:
Linked BF Score: 0

 Description   

The changes for SERVER-24467 tightened the checks around collection version mismatch in the moveChunk command. However, this breaks the initial partitioning of a hashed sharded collection by a 3.2 mongos, because 3.2 it does not refresh the collection metadata between iterations.

In order to preserve backwards compatibility with 3.2 we should remove the exact collection version check.



 Comments   
Comment by Githook User [ 14/Jun/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-24558 Fix hash_shard_num_chunks.js
Branch: master
https://github.com/mongodb/mongo/commit/a489945f3c97620a2852326aac24b98458ea8c77

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