[SERVER-27913] Make sure the last applied hash is corresponding to the last applied optime in bgsync start() Created: 03/Feb/17 Updated: 05/Apr/17 Resolved: 28/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Siyuan Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 2017-03-06 | ||||||||
| Participants: | |||||||||
| Description |
|
In bgsync start(), the last applied hash is read from the disk outside mutex, but the last applied optime is read while holding the mutex. We need to make sure they are synced. The last applied hash is only used for PV0, so this issue will go away when PV0 is deprecated. |
| Comments |
| Comment by Githook User [ 04/Apr/17 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message:
(cherry picked from commit 1da3111dc238698e4e70672b7ba260a368121e50) |
| Comment by Githook User [ 28/Feb/17 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message:
|