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

localLogicalSessionTimeoutMinutes does not affect lsidTTLIndex

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.3
    • Component/s: Sharding
    • Labels:
      None
    • ALL
    • Hide

      1. start mongod:

      mongod --setParameter localLogicalSessionTimeoutMinutes=1 --setParameter logicalSessionRefreshMillis=1000
      

      the logicalSessionRefreshMillis is overriden to force index recreation sooner than default Refresh interval of 5 min

      The log will show

       
      [LogicalSessionCacheRefresh] Failed to refresh session cache: Location13111: wrong type for field (expireAfterSeconds) long != int
      

      verify that the timeout did not change:

      use confg
      db.system.sessions.getIndexes()
      

      verify that the {expireAfterSecods}} value in {lsidTTLIndex}} is 1800. While its expected to be 60 with the new value of the parameter.

      
      
      Show
      1. start mongod: mongod --setParameter localLogicalSessionTimeoutMinutes=1 --setParameter logicalSessionRefreshMillis=1000 the logicalSessionRefreshMillis is overriden to force index recreation sooner than default Refresh interval of 5 min The log will show [LogicalSessionCacheRefresh] Failed to refresh session cache: Location13111: wrong type for field (expireAfterSeconds) long != int verify that the timeout did not change: use confg db.system.sessions.getIndexes() verify that the {expireAfterSecods}} value in {lsidTTLIndex}} is 1800. While its expected to be 60 with the new value of the parameter.

      lsidTTLIndex on config.system.sessions is not recreated when localLogicalSessionTimeoutMinutes is set to non default

            Assignee:
            misha.tyulenev@mongodb.com Misha Tyulenev
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: