[SERVER-20530] mongos with stale config returns wrong results when useClientClusterCursor=true Created: 21/Sep/15 Updated: 07/Oct/15 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: | Misha Tyulenev | 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 |
| Steps To Reproduce: | Run the jstests/sharding/zero_shard_version.js testcase. )); ) returns "null" |
| Sprint: | QuInt A (10/12/15) |
| Participants: |
| Description |
|
Mongos returns null result for
When mongo has correct sharding data it returns a document. The bug happens when mongo caches stale config where user collection is unsharded. |
| Comments |
| Comment by Githook User [ 25/Sep/15 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: Reverts changes to coll_epoch_test1.js from a6ccf45d. |
| 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 Githook User [ 24/Sep/15 ] |
|
Author: {u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}Message: |
| Comment by Githook User [ 24/Sep/15 ] |
|
Author: {u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}Message: |