[SERVER-47881] Make ReplicationCoordinatorImpl::getLatestWriteOpTime return StatusWith<OpTime> Created: 01/May/20 Updated: 29/Oct/23 Resolved: 04/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.4.0-rc3 |
| Fix Version/s: | 4.4.0-rc4, 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kelsey Schubert | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | Repl 2020-05-18 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 35 | ||||||||||||
| Description |
|
Observed while dogfooding on an internal cluster. After upgrade, whenever the automation agent would write to local.clustermanager, we would throw this uassert: |
| Comments |
| Comment by Githook User [ 05/May/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: (cherry picked from commit 892bce4528b2ec97d9f264b5a982d54da0e4971d) |
| Comment by Githook User [ 04/May/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |
| Comment by Lingzhi Deng [ 01/May/20 ] |
|
ReplicationCoordinatorImpl::getLatestWriteOpTime is only called here in ReplClientInfo::setLastOpToSystemLastOpTim. And we ignore NotMaster errors. It seems weird if this error gets leaked to clients. |