[SERVER-50823] MongoDB Does not consider maxSessions Created: 09/Sep/20 Updated: 27/Oct/23 Resolved: 21/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 4.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | vikrant raghuvanshi | Assignee: | Dmitry Agranat |
| Resolution: | Community Answered | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
MongoDb Community version 4.0.5 does not seems to consider settings for maxSession Tried setting a different count then the default but it still gives error after the default active session count is reached. The only way to avoid that is to restart the whole cluster(or the replica nodes where the error is coming from).
Cluster Setup:
And we do not have any db/collection in sharding. |
| Comments |
| Comment by Dmitry Agranat [ 15/Sep/20 ] | |||||
|
Thanks vikscool97@gmail.com for all the additional details, we really appreciate this. | |||||
| Comment by vikrant raghuvanshi [ 14/Sep/20 ] | |||||
|
Sure, | |||||
| Comment by Dmitry Agranat [ 14/Sep/20 ] | |||||
|
Thanks for the update vikscool97@gmail.com, could you please clarify about the "improper shutdown of nodes"? Was it a power shutdown or anything else? | |||||
| Comment by vikrant raghuvanshi [ 14/Sep/20 ] | |||||
|
Hi Dima, Apologies for the delay. Thanks for the suggestion of checking the system.sessions. And again thanks for all the quick help. | |||||
| Comment by Dmitry Agranat [ 10/Sep/20 ] | |||||
|
In order for us to investigate this issue, we'll need to gather some information. Please provide the following:
Also, could you please clarify the reported issue:
Thanks, |