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

session refresh does not use localLogicalSessionTimeoutMinutes to delete old sessions

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Community Answered
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.3
    • Component/s: None
    • None
    • ALL
    • Hide

      set localLogicalSessionTimeoutMinutes: 120 and cursorTimeoutMillis : 7200000

      restart mongoDB,

      start a cursor, get a few records and wait for 40mn, issue a getMore on the cursor (try to retrieve all the cursor's values).

      You'll get a cursorNotFound error

      Show
      set localLogicalSessionTimeoutMinutes: 120 and cursorTimeoutMillis : 7200000 restart mongoDB, start a cursor, get a few records and wait for 40mn, issue a getMore on the cursor (try to retrieve all the cursor's values). You'll get a cursorNotFound error
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If you change localLogicalSessionTimeoutMinutes parameter to a value greater then 30, for example 120, sessions are still deleted after 30mn. And the attached cursors are deleted too

       

      2020-03-11T14:42:57.041+0000 I QUERY [LogicalSessionCacheRefresh] killing cursor: 4547660581473595061 as part of killing session(s)

      program was started at 14:07 

       

        1. mongod.log.1
          79 kB

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            rj-10gen@arsynet.com Remi Jolin
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: