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

Arbiter nodes log error messages when try to create session collection or check if it exists

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • Sharding 2020-06-01

    Description

      Arbiters do not need to try to set up sessions collection.
      Currently they are (3.6.8 - confirmed) [LogicalSessionCacheReap] Sessions collection is not set up; waiting until next sessions reap interval: Can not create config.system.sessions collection

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36964 Prevent secondaries in SessionsCollectionRS from attempting to set up the sessions collection.

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-54064 Sessions on arbiters accumulate and cannot be cleared out

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-48674 Check if replication is enabled before checking if the node is an arbiter in LogicalSessionCacheImpl

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              cheahuychou.mao@mongodb.com Cheahuychou Mao
              misha.tyulenev@mongodb.com Misha Tyulenev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: