[SERVER-38354] Allow shutdown error when reading last applied optime on startup Created: 30/Nov/18 Updated: 29/Oct/23 Resolved: 20/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.7, 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Siyuan Zhou |
| Resolution: | Fixed | 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 | ||||||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||||||
| Sprint: | Repl 2018-12-17, Repl 2019-01-14 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 58 | ||||||||||||||||
| Description |
|
Shutdown errors should be acceptable in BackgroundSync::_readLastAppliedOpTimeWithHash(). |
| Comments |
| Comment by Githook User [ 22/Feb/19 ] |
|
Author: {'name': 'Siyuan Zhou', 'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com'}Message: (cherry picked from commit 9301f8067521d2e7178b698cc521eab990187aee)
(cherry picked from commit 47d5c44e53cb8414ba18564a21ca445579d86875) |
| Comment by Githook User [ 20/Dec/18 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: |
| Comment by Githook User [ 20/Dec/18 ] |
|
Author: {'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou'}Message: |
| Comment by Tess Avitabile (Inactive) [ 03/Dec/18 ] |
|
Got it, thanks for looking into this. |
| Comment by Siyuan Zhou [ 03/Dec/18 ] |
|
tess.avitabile, I think you're right that we don't have to backport to 3.6 since the fix of
|
| Comment by Siyuan Zhou [ 01/Dec/18 ] |
|
I believe shutdown becomes possible because we check for interruptions when acquiring locks in |