[SERVER-6685] shard3.js fails strangely in 2.0 mongod/2.2 mongos Created: 01/Aug/12 Updated: 11/Jul/16 Resolved: 08/Aug/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Probably related to new collection epoch detection. |
| Comments |
| Comment by auto [ 09/Aug/12 ] |
|
Author: {u'date': u'2012-08-09T08:25:33-07:00', u'email': u'spencer@10gen.com', u'name': u'Spencer T Brody'}Message: Make handling of stale configs in ParallelSortClusteredCursor safer |
| Comment by auto [ 08/Aug/12 ] |
|
Author: {u'date': u'2012-08-07T12:52:51-07:00', u'email': u'spencer@10gen.com', u'name': u'Spencer T Brody'}Message: Check result object of command for stale config in ParallelSortClusteredCursor. |
| Comment by Kristina Chodorow (Inactive) [ 07/Aug/12 ] |
|
Looks like the shard/config server were running 2.0.6, so sending ts|inc as the version number. The mongos was running 2.2, so expecting ts|inc|epoch as the version and got an EOO instead of an epoch. We might want to handle this case (have the mongos say "aha, the epoch is missing, I must be talking to an old mongod" and do... something). But this is the opposite of the recommended upgrade path. |