[SERVER-22261] MMAPv1 LSNFile may be updated ahead of what is synced to data files Created: 21/Jan/16 Updated: 27/Aug/21 Resolved: 26/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1 |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.12, 3.0.10, 3.2.3, 3.3.1 |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Sprint: | Integration F (02/01/16) | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
MMAPv1 journalling tracks the LSN of the last write to be fsynced to the data files so it knows where to start applying the journal file during recovery. Due to a sequencing error in how it is updated, it may be ahead of what is actually synced to the data files. |
| Comments |
| Comment by Githook User [ 04/Mar/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: (cherry picked from commit 0386400f728588140ccd9c896f7b87370d9bc866) |
| Comment by Githook User [ 02/Feb/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: (cherry picked from commit 0386400f728588140ccd9c896f7b87370d9bc866) |
| Comment by Githook User [ 27/Jan/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: (cherry picked from commit 0386400f728588140ccd9c896f7b87370d9bc866) |
| Comment by Mathias Stearn [ 27/Jan/16 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |