[SERVER-57649] DDL coordinator dist lock acquisition must be resilient to CSRS stepdowns Created: 11/Jun/21  Updated: 29/Oct/23  Resolved: 17/Jun/21

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: PM-1965-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
causes SERVER-68193 Sharding DDL coordinator can lock its... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-06-14, Sharding EMEA 2021-06-28
Participants:
Linked BF Score: 146

 Description   

Distributed locks acquisitions may fail while recovering the dist lock manager in case the config sever primary concurrently steps down.

DDL coordinators' locks acquisition phase must take this into account and retry indefinitely.



 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 [ 17/Jun/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-57649 DDL coordinator dist lock acquisition must be resilient to CSRS stepdowns

(cherry picked from commit fc1ea44740c05ab73ce0bcf8a1897aa322b1d057)
Branch: v5.0
https://github.com/mongodb/mongo/commit/7a59105d2b769d3a86c956cc08af01d6bd59fd82

Comment by Githook User [ 16/Jun/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-57649 DDL coordinator dist lock acquisition must be resilient to CSRS stepdowns
Branch: master
https://github.com/mongodb/mongo/commit/fc1ea44740c05ab73ce0bcf8a1897aa322b1d057

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