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

Lock acquisition timeout should always throw rather than fail silently with LOCK_TIMEOUT result

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.9
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Storage NYC 2019-02-11, Storage NYC 2019-02-25

      SERVER-39106 fixed a problem about lock acquisition: When ticket acquisition times out due to _maxLockTimeout, it should throw rather than fail silently with LOCK_TIMEOUT result.

      However, the contract of lock acquisition is not very clear right now:

      1. If the lock acquisition times out due to _maxLockTimeout, it should throw.
      2. If the lock acquisition times out due to deadline specified by callers, it should silently return LOCK_TIMEOUT

      This ticket is to try to simplify the contract so that it always throw an exception.

            Assignee:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Reporter:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: