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

Intent Lock timeout lead to server crash

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: 4.4.1
    • Fix Version/s: 4.9.0, 4.4.4
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Execution Team 2021-01-25

      Description

      Our MongoDB server had a few instances where it crashed after seeing the following log message,

       

      {{

      Unknown macro: {"t"}

      ,"s":"F", "c":"CONTROL", "id":4757800, "ctx":"conn455","msg":"Writing fatal message","attr":{"message":"DBException::toString(): LockTimeout: Unable to acquire IS lock on '

      Unknown macro: {16140901064495857683}

      ' within 5ms.\nActual exception type: mongo::error_details::ExceptionForImpl<(mongo::ErrorCodes::Error)24, mongo::ExceptionForCat<(mongo::ErrorCategory)2> >\n"}}}}

       
      I can understand that it causes writing to fail, but why would it be a fatal error? This can entirely be due to a transient hardware issues such as slow access to disk.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              yan.zhou@cubistsystematic.com Yan Zhou
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: