[SERVER-26716] Assertion error when downgrading to 3.2.10 from 3.4.0-rc0 Created: 20/Oct/16 Updated: 20/Nov/16 Resolved: 15/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.11, 3.4.0-rc4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Louisa Berger | Assignee: | Mathias Stearn |
| 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 | ||||||||||||
| Backport Completed: | |||||||||||||
| Sprint: | Repl 2016-11-21 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Steps to repro : The secondaries fail in the downgrade with an assertion error :
Full trace here :
|
| Comments |
| Comment by Githook User [ 16/Nov/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This was only an issue for nodes that had never done writes as a secondary (cherry picked from commit 39d650faa5436a37359ca45717d5e988fb4461cb) |
| Comment by Githook User [ 15/Nov/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This was only an issue for nodes that had never done writes as a secondary |
| Comment by Mathias Stearn [ 25/Oct/16 ] |
|
Not really. The underlying bug only causes a problem if the node has never done any writes as a secondary and wasn't initialized with 3.4. Due to the noopwriter and the unpredictability of elections, hitting this is non-deterministic. |
| Comment by Daniel Pasette (Inactive) [ 25/Oct/16 ] |
|
redbeard0531, is there a good reason to believe this was fixed in 3.4.0-rc1? |