Ignore duplicate key error from refreshLogicalSessionCacheNow

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Sharding 2018-12-17
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      refreshLogicalSessionCacheNow can run in parallel with logical sessions cache refresh thread and hence call LogicalSessinsCacheImpl::_refresh method concurrently which will result in returning duplicate key error.
      As refreshLogicalSessionCacheNow is a part of test its ok to ignore the duplicate key status in some cases to improve test reliability.

              Assignee:
              Matthew Saltz (Inactive)
              Reporter:
              Misha Tyulenev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: