-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Minor Change
-
ALL
-
v4.4
This is inconsistent with mongod, which always rejects the writeConcern field on commands where supportsWriteConcern() returns false.
The problem is that this check is using !wcResult.usedDefault, rather than something like request.body.hasField(WriteConcernOptions::kWriteConcernField).
mongod:
> db.runCommand({ping:1, writeConcern:{w:1}})
{
"ok" : 0,
"errmsg" : "Command does not support writeConcern",
"code" : 72,
"codeName" : "InvalidOptions"
}
> db.runCommand({ping:1, writeConcern:{}})
{
"ok" : 0,
"errmsg" : "Command does not support writeConcern",
"code" : 72,
"codeName" : "InvalidOptions"
}
mongos:
mongos> db.runCommand({ping:1, writeConcern:{w:1}})
{
"ok" : 0,
"errmsg" : "Command does not support writeConcern",
"code" : 72,
"codeName" : "InvalidOptions",
"operationTime" : Timestamp(1572499322, 1),
"$clusterTime" : {
"clusterTime" : Timestamp(1572499322, 1),
"signature" : {
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
"keyId" : NumberLong(0)
}
}
}
mongos> db.runCommand({ping:1, writeConcern:{}})
{
"ok" : 1,
"operationTime" : Timestamp(1572499322, 1),
"$clusterTime" : {
"clusterTime" : Timestamp(1572499322, 1),
"signature" : {
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
"keyId" : NumberLong(0)
}
}
}
- is documented by
-
DOCS-13508 Investigate changes in SERVER-44333: mongos accepts empty wc on commands that don't support writeConcern
-
- Closed
-