Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-566

Add default port for jobtracker (mapred.job.tracker)

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      HADOOP-3317 standardizes port 8020 as the default port for NameNode / HDFS URIs. The mapred.job.tracker property has no such analogue.

      I propose specifying a default port of 8021 if no port-component is specified in the user's mapred.job.tracker property.

      1. HADOOP-5578.patch
        4 kB
        Aaron Kimball

        Issue Links

          Activity

          Hide
          hadoopqa Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12403720/HADOOP-5578.patch
          against trunk revision 759398.

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 3 new or modified tests.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 findbugs. The patch does not introduce any new Findbugs warnings.

          +1 Eclipse classpath. The patch retains Eclipse classpath integrity.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          -1 core tests. The patch failed core unit tests.

          -1 contrib tests. The patch failed contrib unit tests.

          Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/testReport/
          Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
          Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/artifact/trunk/build/test/checkstyle-errors.html
          Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/console

          This message is automatically generated.

          Show
          hadoopqa Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12403720/HADOOP-5578.patch against trunk revision 759398. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 Eclipse classpath. The patch retains Eclipse classpath integrity. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/70/console This message is automatically generated.
          Hide
          kimballa Aaron Kimball added a comment -
          • Core test failure is in pipes; doubt that this is related. ("Forked Java VM exited abnormally" is all it says)
          • Contrib test failures are in capacity scheduler; these are also unrelated.
          Show
          kimballa Aaron Kimball added a comment - Core test failure is in pipes; doubt that this is related. ("Forked Java VM exited abnormally" is all it says) Contrib test failures are in capacity scheduler; these are also unrelated.
          Hide
          tomwhite Tom White added a comment -

          +1

          Looks good to me.

          Show
          tomwhite Tom White added a comment - +1 Looks good to me.
          Hide
          amar_kamat Amar Kamat added a comment -

          I would rather go for an end to end test case which brings up jobtracker with 3 different configs namely

          1. hostname
          2. hostname:
          3. hostname:port

          and test what hostname:port values are actually used. Wouldnt that work? Also I think Namenode does something similar. Cant we factor out this port(checking/adding) code?

          Show
          amar_kamat Amar Kamat added a comment - I would rather go for an end to end test case which brings up jobtracker with 3 different configs namely hostname hostname: hostname:port and test what hostname:port values are actually used. Wouldnt that work? Also I think Namenode does something similar. Cant we factor out this port(checking/adding) code?
          Hide
          tomwhite Tom White added a comment -

          Cancelling pending tests.

          Show
          tomwhite Tom White added a comment - Cancelling pending tests.
          Hide
          aw Allen Wittenauer added a comment -

          Stale at this point.

          Show
          aw Allen Wittenauer added a comment - Stale at this point.

            People

            • Assignee:
              kimballa Aaron Kimball
              Reporter:
              kimballa Aaron Kimball
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development