[SERVER-22498] Fix migration session id multiversion failure Created: 05/Feb/16 Updated: 19/Nov/16 Resolved: 08/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.3, 3.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | Sharding 10 (02/19/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Migration fails from 3.2 mongod to 3.0 mongod. In a migration, a 3.2 donor mongod generates a migration session id, saves it, and then sends it to a 3.0 recipient mongod, which ignores it. The 3.0 recipient then sends requests to the 3.2 donor without a session id. The 3.2 donor rejects the empty session id requests because it doesn't match the id it generated... If the 3.2 donor receives a request without a session id, ignore the match results. |
| Comments |
| Comment by Githook User [ 08/Feb/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: (cherry picked from commit a6903e29adf6a674711a4cbcd8f4cf3b9bd66432) |
| Comment by Githook User [ 08/Feb/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |