Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.1, v8.0, v7.0, v6.0
Sprint:
Cluster Scalability 2025-03-17
Linked BF Score:
200
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

We need to wait for write concern even on no-op writes. Today, we try to enforce doing this here, but some commands won't have taken the global write lock on the opCtx (e.g. create collection in a sharded cluster) and so will miss waiting. We should just always set the lastOp to the systemLastOp for write requests as long as we're not in a txn.

causes

SERVER-102765 Create collection can be rollbacked and not retried on a Replica Set cluster

Closed

is related to

SERVER-102765 Create collection can be rollbacked and not retried on a Replica Set cluster

Closed

SERVER-102312 Ensure that mongos upgrades the WC of a shardCollection request to 'majority' when possible

Closed

related to

SERVER-104220 Router must take into account drop collection write concern error

Closed

SERVER-104331 Perform an audit over non-sharding DDLs to ensure that they all honor the received WC parameter in case of no-op

Closed

Assignee:: Janna Golden
Reporter:: Janna Golden
Participants:: Githook User, Janna Golden
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Mar 10 2025 03:38:29 PM UTC
Updated:: May 02 2025 06:05:10 PM UTC
Resolved:: Mar 12 2025 04:44:59 PM UTC
Confidence Status Last Update:: 10/Mar/25 3:38 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates