Details
Description
Current Scenario:
We found the connPoolMaxShardedConnsPerHost parameter still exists 5.0 and 6.0 documentation:
But if you try to set the value on those versions, you get an "unrecognized parameter" error:
> db.adminCommand( { setParameter: 1, connPoolMaxShardedConnsPerHost:250} ) |
{
|
"ok" : 0, |
"errmsg" : "attempted to set unrecognized parameter [connPoolMaxShardedConnsPerHost], use help:true to see options " |
}
|
mongod --setParameter connPoolMaxShardedConnsPerHost=100 --quiet
{"t":
,"s":"F", "c":"CONTROL", "id":20574, "ctx":"-","msg":"Error during global initialization","attr":{"error":
{"code":2,"codeName":"BadValue","errmsg":"Unknown --setParameter 'connPoolMaxShardedConnsPerHost'"}}}
And we can retrieve its value on 4.2.8 but we can't on 5.0.13 or 6.0.3:
v4.2.8:
> db.adminCommand( { getParameter : '*' } ).connPoolMaxShardedConnsPerHost
200
>
v5.0.13:
> db.adminCommand( { getParameter : '*' } ).connPoolMaxShardedConnsPerHost
>
v6.0.3
> db.adminCommand( { getParameter : '*' } ).connPoolMaxShardedConnsPerHost
>
It seems like the parameter doesn't exist after 5.0 but there is no release notes mentioning that and the parameter is mentioned in 5.0 documentation.