[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: Reverts changes to sharding_balance4.js from a6ccf45d. |
| Comment by Misha Tyulenev [ 24/Sep/15 ] |
|
Fixed with the changes in |
| Comment by Githook User [ 24/Sep/15 ] |
|
Author: {u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}Message: |