Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
3.3.8
-
None
-
Sharding
-
ALL
Description
if the write command doesn't pass the write concern
example shell session to CSRS primary to demonstrate:
test-configRS:PRIMARY> use config
|
switched to db config
|
test-configRS:PRIMARY> db.user.insert({ x: 1 })
|
WriteResult({ "nInserted" : 1 })
|
db.user.insert({ x: 2 }, { writeConcern: { w: 1 }})
|
WriteResult({
|
"writeError" : {
|
"code" : 2,
|
"errmsg" : "w: 'majority' is the only valid write concern when writing to config server replica sets, got: { w: 1, wtimeout: 0 }"
|
}
|
})
|
Attachments
Issue Links
- duplicates
-
SERVER-24738 Config servers incorrectly allow w:1 writes if no write concern is specified
-
- Closed
-