Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-2988

Improve error message when storage directory lock fails

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.2-alpha
    • Component/s: namenode
    • Labels:
    • Hadoop Flags:
      Reviewed

      Description

      Currently, the error message is fairly opaque to a non-developer ("Cannot lock storage" or something). Instead, we should have some improvments:

      • when we create the in_use.lock file, we should write the hostname/PID that locked the file
      • if the lock fails, and in_use.lock exists, the error message should say something like "It appears that another namenode (pid 23423 on host foo.example.com) has already locked the storage directory."
      • if the lock fails, and no lock file exists, the error message should say something like "if this storage directory is mounted via NFS, ensure that the appropriate nfs lock services are running."
      1. HDFS-2988.patch
        9 kB
        Miomir Boljanovic
      2. HDFS-2988.patch
        4 kB
        Miomir Boljanovic
      3. HDFS-2988.patch
        4 kB
        Miomir Boljanovic
      4. HDFS-2988.patch
        5 kB
        Harsh J

        Activity

          People

          • Assignee:
            Miomir Boljanovic
            Reporter:
            Todd Lipcon
          • Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development