Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-2877

If locking of a storage dir fails, it will remove the other NN's lock file on exit

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.23.0, 1.0.0, 2.0.0-alpha
    • 1.1.0, 0.22.1
    • namenode
    • None

    Description

      In Storage.tryLock(), we call lockF.deleteOnExit() regardless of whether we successfully lock the directory. So, if another NN has the directory locked, then we'll fail to lock it the first time we start another NN. But our failed start attempt will still remove the other NN's lockfile, and a second attempt will erroneously start.

      Attachments

        1. hdfs-2877.txt
          2 kB
          Todd Lipcon

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. HDFS-2632 existing in_use.lock file is removed after failing to lock this file

          • Major - Major loss of function.
          • Resolved
          is related to

          Sub-task - The sub-task of the issue HDFS-2865 Standby namenode gets a "cannot lock storage" exception during startup

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. HDFS-1690 Name Node should not process format command while it is running.

          • Major - Major loss of function.
          • Open

          Activity

            People

              tlipcon Todd Lipcon
              tlipcon Todd Lipcon
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: