[DOCS-13476] Investigate changes in SERVER-46249: Cluster createIndexes and createCollection may fail to run in readConcern-specifying transactions Created: 28/Feb/20  Updated: 13/Nov/23  Due: 03/Apr/20  Resolved: 09/Apr/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: docs-query
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-46249 Disallow createIndexes and createColl... Closed
Related
related to DOCS-13448 4.4 Known Issues Closed
related to DOCS-13500 Investigate changes in SERVER-46119: ... Closed
Participants:
Days since reply: 3 years, 43 weeks, 6 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

This will be a known error for PM-1168. Please ensure it is in release notes for 4.4.

Description of Linked Ticket

The test concurrent_drops_and_creates.js can be modified to create a scenario where createIndexes and createCollection can fail with the following message:

"Command create does not support { readConcern: { level: \"snapshot\", provenance: \"clientSupplied\" } } :: caused by :: read concern not supported",

This failure occurs if concurrent_drops_and_creates.js explicitly creates a collection or an index inside this transaction (instead of the highlighted lines), and is run inside sharded_jscore_txns.

I spun up a ShardingTest locally and attempted the same sequence of events as this test, but I did not run into the error, which leads me to believe something about the testing configuration results in readConcern getting explicitly forwarded to the cluster create and cluster createIndexes commands.

Note that this error does not occur when running the same test (with the above modification) in replica_sets_jscore_passthrough.

As an update, it looks like in order to reproduce this error, createCollection/createIndexes needs to be run after another operation inside a transaction. If either is the first operation inside the transaction, the error does not occur.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 09/Apr/20 ]

Author:

{'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}

Message: (DOCS-13476): createCollections and createIndexes in transactions must use RC local
Branch: master
https://github.com/mongodb/docs/commit/8731a300b1c2c38740e75d9dab5ea27c080e7da3

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