-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Security
-
Fully Compatible
-
v8.0, v7.0
-
Security 2024-02-19, Security 2024-03-04, Security 2024-03-18, Security 2024-04-01, Security 2024-04-15, Security 2024-04-29, Security 2024-05-13, Security 2024-05-27, Security 2024-06-10, Security 2024-12-23
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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" : 1,
"nUpserted" : 0,
"nModified" : 1,
"writeError" : {
"code" : 100,
"errmsg" : "Not enough data-bearing nodes; Error details: { writeConcern: { w: 50, j: false, wtimeout: 100, provenance: \"clientSupplied\" } }"
}
}
- is depended on by
-
SERVER-81280 Handle writeConcernErrors for FLE in bulkWrite
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-102571 Check against WriteConcernError category when processing QE transactions
-
- Closed
-
- related to
-
-
- Closed
-