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

lsidTTLIndex is incorrect after modifying localLogicalSessionTimeoutMinutes in sharded cluster

    XMLWordPrintable

Details

    • Bug
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Sharding
    • None
    • ALL
    • Sharding 2019-10-07, Sharding 2019-10-21, Sharding 2019-11-04, Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13

    Description

      If you create a sharded cluster running MongoDB 3.6 or later, the config server primary will create a sharded collection config.system.sessions with a TTL index lsidTTLIndex with an expiresAfterSeconds set to localLogicalSessionTimeoutMinutes x 60. If you later restart all cluster nodes with a new localLogicalSessionTimeoutMinutes, the TTL indexes on the shards is not updated to the new value. If you drop the lsidTTLIndex, it will be recreated with the correct value.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding-nyc Backlog - Sharding NYC
              james.kovacs@mongodb.com James Kovacs
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated: