[SERVER-39131] Refactor storage engine lock file support Created: 22/Jan/19  Updated: 29/Oct/23  Resolved: 23/Jan/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.6.17, 4.1.8, 4.0.15

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

Issue Links:
Backports
Depends
is depended on by SERVER-39133 Make mongocryptd host Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0, v3.6
Participants:

 Description   

Currently, the storage engine lock file code hard codes the name of the lock file. This could should be refactored to stop hard coding the file name.

Also, the file name is hard coded in three different files.



 Comments   
Comment by Githook User [ 31/Dec/19 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-39131 Refactor storage engine lock file support

(cherry picked from commit 6cc1024d908e4929928d8bd5002f85f6a57980b4)
Branch: v4.0
https://github.com/mongodb/mongo/commit/18ebea98d850402b3b6be7fda89df1029ab5091f

Comment by Githook User [ 31/Dec/19 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-39131 Refactor storage engine lock file support

(cherry picked from commit 6cc1024d908e4929928d8bd5002f85f6a57980b4)
Branch: v3.6
https://github.com/mongodb/mongo/commit/4a0eda133d4e045b41c2bf1371648e0645ff1e55

Comment by Githook User [ 23/Jan/19 ]

Author:

{'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com', 'name': 'Mark Benvenuto'}

Message: SERVER-39131 Refactor storage engine lock file support
Branch: master
https://github.com/mongodb/mongo/commit/6cc1024d908e4929928d8bd5002f85f6a57980b4

Generated at Thu Feb 08 04:51:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.