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

Provide better error messages when fs.default.name is invalid

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      this the followon to HADOOP-5687 - its not enough to detect bad uris, we need good error messages and a set of tests to make sure everything works as intended.

      Attachments

        1. HADOOP-5095-1.patch
          7 kB
          Steve Loughran

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. HDFS-2965 Starting HDFS with blank configuration fails

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MAPREDUCE-406 setting fs.default.name to an invalid URI format kills init thread in JobTracker

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-5200 NPE when the namenode comes up but the filesystem is set to file://

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. HADOOP-5687 Hadoop NameNode throws NPE if fs.default.name is the default value

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              stevel@apache.org Steve Loughran
              stevel@apache.org Steve Loughran
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: