[SERVER-78154] Detect on-going DDL operations in fsync with lock command Created: 15/Jun/23  Updated: 29/Oct/23  Resolved: 08/Aug/23

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

Type: Task Priority: Major - P3
Reporter: Nandini Bhartiya Assignee: Jada Lilleboe (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-78157 Test the mongos fsync lock command wh... Closed
Problem/Incident
causes SERVER-80246 Fsync test is not correctly checking ... Closed
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0
Participants:
Linked BF Score: 161

 Description   

The mongos fsync with lock command should ensure that there are no DDL operations in progress on any shard. The fsync with lock command must first lock the shard and then verify if any DDL operations are in progress (this ordering of operations, inhibits any new DDL operation from starting before locking the shard). If any in-progress DDL operations are detected on any shard, the mongos fsync with lock command must fail, unlock any locked shards and return an appropriate error to the user.

Determine if an additional parameter (to detect DDL operations in progress) must be passed while broadcasting the fsync with lock command to all shards.

This capability will only be available in v6.0 and above. 



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

Author:

{'name': 'Nandini Bhartiya', 'email': 'nandini.bhartiya@mongodb.com', 'username': 'nandinibhartiyaMDB'}

Message: SERVER-78154: Detect ongoing DDL operations during fsync command

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

Comment by Githook User [ 30/Aug/23 ]

Author:

{'name': 'Jada Lilleboe', 'email': 'jada.lilleboe@mongodb.com', 'username': 'jadalilleboe'}

Message: SERVER-78154: Detect ongoing DDL operations during fsync command

(cherry picked from commit e678c890ac426426c68d1904f509dcc88402594a)
Branch: v7.0
https://github.com/mongodb/mongo/commit/2a02cc5453e7cea5974346e284e971639171dc9e

Comment by Githook User [ 07/Aug/23 ]

Author:

{'name': 'Jada Lilleboe', 'email': 'jada.lilleboe@mongodb.com', 'username': 'jadalilleboe'}

Message: SERVER-78154: Detect ongoing DDL operations during fsync command
Branch: master
https://github.com/mongodb/mongo/commit/e678c890ac426426c68d1904f509dcc88402594a

Comment by Githook User [ 01/Aug/23 ]

Author:

{'name': 'Sviatlana Zuiko', 'email': 'sviatlana.zuiko@mongodb.com', 'username': 'szuiko'}

Message: Revert "SERVER-78154 Detect ongoing DDL operations during fsync command"

This reverts commit f15a5ab8fd1b80727b79aac641a77076107f2ebf.
Branch: minh.luu-no_compile_sys-perf
https://github.com/mongodb/mongo/commit/411ca7daed901052f44f53f064d195066df810f3

Comment by Githook User [ 31/Jul/23 ]

Author:

{'name': 'Sviatlana Zuiko', 'email': 'sviatlana.zuiko@mongodb.com', 'username': 'szuiko'}

Message: Revert "SERVER-78154 Detect ongoing DDL operations during fsync command"

This reverts commit f15a5ab8fd1b80727b79aac641a77076107f2ebf.
Branch: master
https://github.com/mongodb/mongo/commit/411ca7daed901052f44f53f064d195066df810f3

Comment by Githook User [ 27/Jul/23 ]

Author:

{'name': 'Jada Lilleboe', 'email': 'jada.lilleboe@mongodb.com', 'username': 'jadalilleboe'}

Message: SERVER-78154 Detect ongoing DDL operations during fsync command
Branch: master
https://github.com/mongodb/mongo/commit/f15a5ab8fd1b80727b79aac641a77076107f2ebf

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