Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-2760

mapreduce.jobtracker.split.metainfo.maxsize typoed in mapred-default.xml

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.23.0
    • Fix Version/s: 0.23.0
    • Component/s: documentation
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      The configuration mapreduce.jobtracker.split.metainfo.maxsize is incorrectly included in mapred-default.xml as mapreduce.job.split.metainfo.maxsize. It seems that jobtracker is correct, since this is a JT-wide property rather than a job property.

      1. mr-2760.txt
        0.5 kB
        Todd Lipcon

        Issue Links

          Activity

          Hide
          Todd Lipcon added a comment -

          Trivial patch

          Show
          Todd Lipcon added a comment - Trivial patch
          Hide
          Eli Collins added a comment -

          +1

          Show
          Eli Collins added a comment - +1
          Hide
          Eli Collins added a comment -

          I've committed this. Thanks Todd!

          Show
          Eli Collins added a comment - I've committed this. Thanks Todd!
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Mapreduce-trunk-Commit #760 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/760/)
          MAPREDUCE-2760. mapreduce.jobtracker.split.metainfo.maxsize typoed in mapred-default.xml. Contributed by Todd Lipcon

          eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1153260
          Files :

          • /hadoop/common/trunk/mapreduce/src/java/mapred-default.xml
          • /hadoop/common/trunk/mapreduce/CHANGES.txt
          Show
          Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk-Commit #760 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/760/ ) MAPREDUCE-2760 . mapreduce.jobtracker.split.metainfo.maxsize typoed in mapred-default.xml. Contributed by Todd Lipcon eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1153260 Files : /hadoop/common/trunk/mapreduce/src/java/mapred-default.xml /hadoop/common/trunk/mapreduce/CHANGES.txt
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Mapreduce-trunk #751 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/751/)
          MAPREDUCE-2760. mapreduce.jobtracker.split.metainfo.maxsize typoed in mapred-default.xml. Contributed by Todd Lipcon

          eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1153260
          Files :

          • /hadoop/common/trunk/mapreduce/src/java/mapred-default.xml
          • /hadoop/common/trunk/mapreduce/CHANGES.txt
          Show
          Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk #751 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/751/ ) MAPREDUCE-2760 . mapreduce.jobtracker.split.metainfo.maxsize typoed in mapred-default.xml. Contributed by Todd Lipcon eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1153260 Files : /hadoop/common/trunk/mapreduce/src/java/mapred-default.xml /hadoop/common/trunk/mapreduce/CHANGES.txt
          Hide
          Abhishek Gayakwad added a comment -

          Why this property is jobtracker level property, when it can be changed for each job by setting required value in job config.

          Show
          Abhishek Gayakwad added a comment - Why this property is jobtracker level property, when it can be changed for each job by setting required value in job config.
          Hide
          Harsh J added a comment -

          Abhishek,

          Its a bug if the JT level property is not honored and is able to be replaced by a client sent conf. You can try to finalize the JT property to enforce it if it is so (only as a workaround).

          In any case, to report bugs, please file a new JIRA rather than reopen closed older ones; thanks!

          Show
          Harsh J added a comment - Abhishek, Its a bug if the JT level property is not honored and is able to be replaced by a client sent conf. You can try to finalize the JT property to enforce it if it is so (only as a workaround). In any case, to report bugs, please file a new JIRA rather than reopen closed older ones; thanks!
          Hide
          Abhishek Gayakwad added a comment -

          No intensions to reopen it, just wanted to know that only this property name is corrected or there is some code modified to actually tie this property at JT level.

          Show
          Abhishek Gayakwad added a comment - No intensions to reopen it, just wanted to know that only this property name is corrected or there is some code modified to actually tie this property at JT level.
          Hide
          Abhishek Gayakwad added a comment -

          Raised MAPREDUCE-5106 jira mentioning that this property is honoured at job level as well.

          Show
          Abhishek Gayakwad added a comment - Raised MAPREDUCE-5106 jira mentioning that this property is honoured at job level as well.

            People

            • Assignee:
              Todd Lipcon
              Reporter:
              Todd Lipcon
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development