Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-891

DataNode no longer needs to check for dfs.network.script

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.23.0
    • Fix Version/s: 2.0.0-alpha
    • Component/s: datanode
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Looking at the code for DataNode.instantiateDataNode())} , I see that it calls {{system.exit(-1) if it is not happy with the configuration

          if (conf.get("dfs.network.script") != null) {
            LOG.error("This configuration for rack identification is not supported" +
                " anymore. RackID resolution is handled by the NameNode.");
            System.exit(-1);
          }
      

      This is excessive. It should throw an exception and let whoever called the method decide how to handle it. The DataNode.main() method will log the exception and exit with a -1 value, but other callers (such as anything using MiniDFSCluster will now see a meaningful message rather than some Junit "tests exited without completing" warning.

      Easy to write a test for the correct behaviour: start a MiniDFSCluster with this configuration set, see what happens.

      1. hdfs-891.txt
        1 kB
        Eli Collins
      2. HDFS-891.patch
        0.9 kB
        Harsh J

        Issue Links

          Activity

            People

            • Assignee:
              Harsh J
              Reporter:
              Steve Loughran
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development