Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Server Security
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\" } }" |
}
|
}
|
Attachments
Issue Links
- is depended on by
-
SERVER-81280 Handle writeConcernErrors for FLE in bulkWrite
-
- Blocked
-