-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.0-rc0
-
Component/s: Admin
-
ALL
The result of a successful setParameter with one parameter to set is
{ was: <old value>, ok: 1 }. However, if you set two parameters, you get back
{ was: <first old value>, was: <second old value>, ok: 1}, which many client drivers seem to turn into
{ was: <one of the old values>, ok: 1}.
Further, if you pass multiple parameters to setParameter, and one of the sets fails, some of the parameters will have been set and some not, and the response will contain a "was" field for one of the successful sets, ok: 0 and errmsg of "not allowed to change [<first encountered unsettable field>]" or some such.
- is duplicated by
-
SERVER-11702 setParameter command results not complete
- Closed
- is related to
-
SERVER-18985 setParameter should log at level 0
- Closed
- related to
-
SERVER-5092 Better named logging with tracing
- Closed