[SERVER-56963] Prevent secondaries from waiting for write concern when they've taken write locks Created: 14/May/21  Updated: 29/Oct/23  Resolved: 17/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-56641 Fix Test: jstests/aggregation/sources... Closed
Problem/Incident
causes SERVER-57494 Race between stepdown and retrying wr... Closed
Related
related to SERVER-56962 Temporarily disable mode_merge_insert... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2021-05-17, Repl 2021-05-31
Participants:
Linked BF Score: 160

 Comments   
Comment by Githook User [ 25/Jun/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: Revert "SERVER-56963 Prevent secondaries from waiting for write concern when they've taken write locks"

This reverts commit 23c40392fd939334752d2b20a75e77e89517feea.
Branch: v5.0
https://github.com/mongodb/mongo/commit/927d7919f2537c9270953f944a15d2a013332702

Comment by Githook User [ 25/Jun/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: Revert "SERVER-56963 Prevent secondaries from waiting for write concern when they've taken write locks"

This reverts commit 23c40392fd939334752d2b20a75e77e89517feea.
Branch: master
https://github.com/mongodb/mongo/commit/66aba33d6a49475c2c331388138c8980c83a28ca

Comment by Githook User [ 17/May/21 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-56963 Prevent secondaries from waiting for write concern when they've taken write locks
Branch: master
https://github.com/mongodb/mongo/commit/23c40392fd939334752d2b20a75e77e89517feea

Generated at Thu Feb 08 05:40:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.