-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 2.6.0-rc0
-
Component/s: Replication
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Example showing it is currently allowed:
> rs.initiate()
{
"info2" : "no configuration explicitly specified -- making one",
"me" : "redbeard:27017",
"info" : "Config now saved locally. Should come online in about a minute.",
"ok" : 1
}
foo:PRIMARY> conf = rs.conf()
{
"_id" : "foo",
"version" : 1,
"members" : [
{
"_id" : 0,
"host" : "redbeard:27017"
}
]
}
foo:PRIMARY> conf.settings = {getLastErrorDefaults: {w:0}}
{ "getLastErrorDefaults" : { "w" : 0 } }
foo:PRIMARY> conf
{
"_id" : "foo",
"version" : 1,
"members" : [
{
"_id" : 0,
"host" : "redbeard:27017"
}
],
"settings" : {
"getLastErrorDefaults" : {
"w" : 0
}
}
}
foo:PRIMARY> rs.reconfig(conf)
{ "ok" : 1 }
foo:PRIMARY> rs.conf()
{
"_id" : "foo",
"version" : 2,
"members" : [
{
"_id" : 0,
"host" : "redbeard:27017"
}
],
"settings" : {
"getLastErrorDefaults" : {
"w" : 0
}
}
}
- is related to
-
SERVER-15655 Secondary can't join if w:0 is in getLastErrorDefaults
-
- Closed
-
-
SERVER-15859 Don't allow w:0 in getLastErrorDefaults in new replication code
-
- Closed
-
-
SERVER-13056 Write commands should ignore w:0 when specified in replset getLastErrorDefaults
-
- Closed
-
-
SERVER-18407 Ensure getLastErrorDefaults/getLastErrorModes are satisfiable
-
- Closed
-
- related to
-
SERVER-15623 Test that w:0 is prohibited in getLastErrorDefaults
-
- Closed
-