[DOCS-15836] connPoolMaxShardedConnsPerHost it's documented but does not work after MongoDB 5.0 onwards. Created: 23/Jan/23 Updated: 05/Feb/24 Resolved: 05/Feb/24 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 5.0.0, 6.0.0 |
| Fix Version/s: | 5.0.0, 6.0.0 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Zelmar Michelini | Assignee: | Caleb Thompson |
| Resolution: | Done | Votes: | 0 |
| Labels: | backlog, bug, release | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 week, 2 days ago |
| Story Points: | 2 |
| 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:
,"s":"F", "c":"CONTROL", "id":20574, "ctx":"-","msg":"Error during global initialization","attr":{"error": {"code":2,"codeName":"BadValue","errmsg":"Unknown --setParameter '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. |
| Comments |
| Comment by Caleb Thompson [ 29/Jan/24 ] |