[SERVER-60351] Writing last vote to "local.replset.election" should not acquire PBWM lock Created: 30/Sep/21 Updated: 29/Oct/23 Resolved: 01/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2021-10-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 136 | ||||||||
| Description |
|
When a replica set node persists the last response to replSetRequestVotes to the local.replset.election, it currently acquires the PBWM lock as part of the collection lock acquisition. This is unnecessary and could affect availability when the node is having issues during oplog application. The node can opt out of acquiring the PBWM lock using the ShouldNotConflictWithSecondaryBatchApplicationBlock. This issue was previously raised (see comment) as part of SERVER-48398. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 01/Oct/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |