[SERVER-86299] FLE WriteConcernError behavior Created: 06/Feb/24  Updated: 07/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Frederic Vitzikam Assignee: Backlog - Security Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-81280 Handle writeConcernErrors for FLE in ... Blocked
Assigned Teams:
Server Security
Participants:

 Description   

I think there is still an issue with FLE WriteConcernError after https://jira.mongodb.org/browse/SERVER-81246:

At the end of bulk_write_update.js, I added

res = edb.basic.update({_id: 1}, {$set: {middle: "F"}}, {writeConcern: {w: 50, j: false, wtimeout: 100}});
print("TODO WIP " + tojson(res));

Then depending on the suite, it behaves differently:

buildscripts/resmoke.py run -j16 --suite fle2_sharding --additionalFeatureFlags featureFlagBulkWriteCommand src/mongo/db/modules/enterprise/jstests/fle2/bulk_write_update.js > /tmp/tmp.txt 2>&1
 
{
	"nMatched" : 1,
	"nUpserted" : 0,
	"nModified" : 1,
	"writeConcernError" : {
		"code" : 100,
		"codeName" : "UnsatisfiableWriteConcern",
		"errmsg" : "Not enough data-bearing nodes",
		"errInfo" : {
			"writeConcern" : {
				"w" : 50,
				"j" : false,
				"wtimeout" : 100,
				"provenance" : "clientSupplied"
			}
		}
}
 
 
buildscripts/resmoke.py run -j16 --suite sharded_collections_jscore_passthrough --additionalFeatureFlags featureFlagBulkWriteCommand src/mongo/db/modules/enterprise/jstests/fle2/bulk_write_update.js > /tmp/tmp2.txt 2>&1
 
{
	"nMatched" : 0,
	"nUpserted" : 0,
	"nModified" : 0,
	"writeError" : {
		"code" : 100,
		"errmsg" : "Not enough data-bearing nodes; Error details: { writeConcern: { w: 50, j: false, wtimeout: 100, provenance: \"clientSupplied\" } }"
	}
}


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