Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.18.3
    • Fix Version/s: 0.18.3
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      SafeModeInfo.leave() acquires locks in an incorrect order, which causes the deadlock.
      It first acquires the SafeModeInfo lock, then calls FSNamesystem.processMisReplicatedBlocks(), which requires the global FSNamesystem lock.
      It should be the other way around: first FSNamesystem lock, then SafeModeInfo.

      1. safeModeDeadlock.patch
        1 kB
        Konstantin Shvachko
      2. safeModeDeadlock-0-18.patch
        1 kB
        Konstantin Shvachko
      3. safeModeDeadlock-0-18.patch
        1 kB
        Konstantin Shvachko

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Konstantin Shvachko
            Reporter:
            Konstantin Shvachko
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development