[SERVER-79025] Mongos Fsync with lock command should use mongos fsyncUnlock command Created: 17/Jul/23  Updated: 29/Oct/23  Resolved: 10/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 4.4.25, 7.0.2, 5.0.22, 6.0.11

Type: Task Priority: Major - P3
Reporter: Nandini Bhartiya Assignee: David Chen (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0, v5.0, v4.4
Participants:
Linked BF Score: 0

 Description   

In case of failure, the mongos fsync with lock command must unlock any locked shards. To do so, it has its own implementation of the fsync Unlock functionality. It would be better for it to invoke the mongos fsyncUnlock command if possible.



 Comments   
Comment by Githook User [ 15/Sep/23 ]

Author:

{'name': 'David Chen', 'email': 'david.chen@mongodb.com', 'username': ''}

Message: SERVER-79025: Rework fsync (lock: true) command to rely on fsync unlock command when lock fails.

(cherry picked from commit db5f8b7b0d128ee4b1fef9b3db0f651d55e65165)
(cherry picked from commit 3b954d87d14897088d280606c63404c8341baa13)
(cherry picked from commit 2def5060b0d4342183270b2206ddb3ffea039079)
Branch: v4.4
https://github.com/mongodb/mongo/commit/2b8ddac4997626e30418b7f0e07362d5982e75ee

Comment by Githook User [ 13/Sep/23 ]

Author:

{'name': 'David Chen', 'email': 'david.chen@mongodb.com', 'username': ''}

Message: SERVER-79025: Rework fsync (lock: true) command to rely on fsync unlock command when lock fails.

(cherry picked from commit db5f8b7b0d128ee4b1fef9b3db0f651d55e65165)
(cherry picked from commit 3b954d87d14897088d280606c63404c8341baa13)
Branch: v5.0
https://github.com/mongodb/mongo/commit/652a544a0b3cd6857147f8cab0faa795e834e2c7

Comment by Githook User [ 12/Sep/23 ]

Author:

{'name': 'David Chen', 'email': 'david.chen@mongodb.com', 'username': ''}

Message: SERVER-79025: Rework fsync (lock: true) command to rely on fsync unlock command when lock fails.

(cherry picked from commit db5f8b7b0d128ee4b1fef9b3db0f651d55e65165)
Branch: v6.0
https://github.com/mongodb/mongo/commit/c1dc8e30707d1f35eb1f469d3e7068a6d78fd2eb

Comment by Githook User [ 30/Aug/23 ]

Author:

{'name': 'David Chen', 'email': 'david.chen@mongodb.com', 'username': ''}

Message: SERVER-79025: Rework fsync (lock: true) command to rely on fsync unlock command when lock fails.

(cherry picked from commit db5f8b7b0d128ee4b1fef9b3db0f651d55e65165)
Branch: v7.0
https://github.com/mongodb/mongo/commit/2415c43ce2964b2d17112254d1eeb36572fc933b

Comment by Githook User [ 10/Aug/23 ]

Author:

{'name': 'David Chen', 'email': 'david.chen@mongodb.com', 'username': ''}

Message: SERVER-79025: Rework fsync (lock: true) command to rely on fsync unlock command when lock fails.
Branch: master
https://github.com/mongodb/mongo/commit/db5f8b7b0d128ee4b1fef9b3db0f651d55e65165

Generated at Thu Feb 08 06:39:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.