[SERVER-20568] Secondaries must not throw shard version exceptions Created: 22/Sep/15  Updated: 27/Sep/16  Resolved: 24/Sep/15

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Misha Tyulenev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding A (10/09/15)
Participants:

 Description   

Now that we send chunk version information in the find command instead of through setShardVersion, we need to make sure not to set sharding state from a find command received on a secondary, or we may trigger shard version exceptions incorrectly



 Comments   
Comment by Githook User [ 24/Sep/15 ]

Author:

{u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}

Message: SERVER-20530 SERVER-20568 Disable useCCC in sharding_balance4.js

Reverts changes to sharding_balance4.js from a6ccf45d.
Branch: master
https://github.com/mongodb/mongo/commit/11febdeeb39c8dbcda39f22e6860cb434f3d64a6

Comment by Misha Tyulenev [ 24/Sep/15 ]

Fixed with the changes in SERVER-20530

Comment by Githook User [ 24/Sep/15 ]

Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: SERVER-20530 SERVER-20568 mongos with stale config returns wrong results
Branch: master
https://github.com/mongodb/mongo/commit/a6ccf45d2a6239604cdbf820b9db5cb6d45e851e

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