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

lsidTTLIndex is incorrect after modifying localLogicalSessionTimeoutMinutes in sharded cluster

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Cluster Scalability
    • 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            james.kovacs@mongodb.com James Kovacs
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: