[SERVER-84081] FLE2 write error hides write concern error Created: 11/Dec/23  Updated: 05/Jan/24

Status: Needs Scheduling
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Erwin Pe Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from SERVER-81246 FLE WriteConcernError behavior unclear Closed
Related
related to SERVER-27067 Some Commands do not wait for write c... Closed
related to SERVER-78311 mongos does not report writeConcernEr... Closed
Assigned Teams:
Cluster Scalability
Operating System: ALL
Steps To Reproduce:

1. spin up a single-node replica set
2. create a FLE2 encrypted collection: "basic" using an encrypted client.
3. run the command: {insert: "basic", documents: [{_id: 1}]}
4. then, run the command:
{insert: "basic", documents: [{_id: 1}], writeConcern: {w: 3}}
5. check that the result of the second insert only contains a DuplicateKey write error, and no UnsatisfiableWriteConcern error

Participants:

 Description   

If a FLE2 write encounters both a write error and a write concern error (WCE), the WCE is omitted from the response. This is inconsistent with the behavior of writes on normal collections where both the WCE and write errors are included in the response. This issue applies to both mongod and mongos.


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