Remove the Session objects for expired transaction sessions whose logical session hasn't expired

XMLWordPrintableJSON

    • Fully Compatible
    • v6.0
    • Sharding NYC 2022-06-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, when reaping sessions from memory, if the LogicalSessionCache reaper finds that a logical session hasn't expired, it would skip reaping its transaction sessions from the SessionCatalog entirely including the ones that are expired and not in-use. This could cause the SessionCatalog to end up with a lot of expired sessions if the external client just keeps using the same logical session.

      Note that the on-disk states for those expired transactions still get deleted in this step.

              Assignee:
              Jack Mulrow
              Reporter:
              Cheahuychou Mao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: