Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-50823

MongoDB Does not consider maxSessions

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Community Answered
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.5
    • Component/s: Stability
    • Labels:
      None
    • ALL
    • Hide
      1. Set the parameter maxSession 2 million.
      2. Restart the nodes.
      3. Increase the logical sessions count over 1 Million.
      4. After hitting the threshold the queries will return "cannot add session into the cache". With TooManyLogicalSessions.
      Show
      Set the parameter maxSession 2 million. Restart the nodes. Increase the logical sessions count over 1 Million. After hitting the threshold the queries will return "cannot add session into the cache". With  TooManyLogicalSessions.

      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:

      • Router:
        • 3 with 8GB RAM and 4 core CPU each.
      • Configuration:
        • 3 with 8GB RAM and 4 core CPU each.
      • Arbiter:
        • 3 with 8GB RAM and 4 core CPU each.
      • Data Nodes:
        • 3 with 16 GB RAM and 4 core CPU each.

      And we do not have any db/collection in sharding.

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            vikscool97@gmail.com vikrant raghuvanshi
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: