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

TestHighRamJob fails due to the change in MAPREDUCE-5785

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-alpha1
    • Fix Version/s: 3.0.0-alpha1
    • Component/s: contrib/gridmix, mrv2
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      TestHighRamJob fails by this.

      -------------------------------------------------------
       T E S T S
      -------------------------------------------------------
      Running org.apache.hadoop.mapred.gridmix.TestHighRamJob
      Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.162 sec <<< FAILURE! - in org.apache.hadoop.mapred.gridmix.TestHighRamJob
      testHighRamFeatureEmulation(org.apache.hadoop.mapred.gridmix.TestHighRamJob)  Time elapsed: 1.102 sec  <<< FAILURE!
      java.lang.AssertionError: expected:<1024> but was:<-1>
      	at org.junit.Assert.fail(Assert.java:88)
      	at org.junit.Assert.failNotEquals(Assert.java:743)
      	at org.junit.Assert.assertEquals(Assert.java:118)
      	at org.junit.Assert.assertEquals(Assert.java:555)
      	at org.junit.Assert.assertEquals(Assert.java:542)
      	at org.apache.hadoop.mapred.gridmix.TestHighRamJob.testHighRamConfig(TestHighRamJob.java:98)
      	at org.apache.hadoop.mapred.gridmix.TestHighRamJob.testHighRamFeatureEmulation(TestHighRamJob.java:117)
      
      1. MAPREDUCE-6234.001.patch
        3 kB
        Masatake Iwasaki
      2. MAPREDUCE-6234.002.patch
        3 kB
        Masatake Iwasaki
      3. MAPREDUCE-6234.003.patch
        2 kB
        Masatake Iwasaki

        Issue Links

          Activity

          Hide
          iwasakims Masatake Iwasaki added a comment -

          The cause of the test failure is the change of default value of mapreduce.map.memory.mb and mapreduce.reduce.memory.mb by MAPREDUCE-5785. Though the default value defined in mapred-default.xml from 1024 to -1 (which means turning on auto deriving from the value of -Xmx in java.opts), MRJobConfig.DEFAULT_MAP_MEMORY_MB and MRJobConfig.DEFAULT_REDUCE_MEMORY_MB are still 1024. Those are used in a few place such as the test in Gridmix.

          Show
          iwasakims Masatake Iwasaki added a comment - The cause of the test failure is the change of default value of mapreduce.map.memory.mb and mapreduce.reduce.memory.mb by MAPREDUCE-5785 . Though the default value defined in mapred-default.xml from 1024 to -1 (which means turning on auto deriving from the value of -Xmx in java.opts), MRJobConfig.DEFAULT_MAP_MEMORY_MB and MRJobConfig.DEFAULT_REDUCE_MEMORY_MB are still 1024. Those are used in a few place such as the test in Gridmix.
          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/12696003/MAPREDUCE-6234.001.patch
          against trunk revision 5f9a0dd.

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

          -1 tests included. The patch doesn't appear to include any new or modified tests.
          Please justify why no new tests are needed for this patch.
          Also please list what manual steps were performed to verify this patch.

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

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          -1 findbugs. The patch appears to introduce 13 new Findbugs (version 2.0.3) warnings.

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

          +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.

          Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5141//testReport/
          Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5141//artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
          Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5141//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/12696003/MAPREDUCE-6234.001.patch against trunk revision 5f9a0dd. +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. -1 findbugs . The patch appears to introduce 13 new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5141//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5141//artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5141//console This message is automatically generated.
          Hide
          iwasakims Masatake Iwasaki added a comment -

          Findbugs warnings are irrelevant. There is work in progress in MAPREDUCE-6225.

          Show
          iwasakims Masatake Iwasaki added a comment - Findbugs warnings are irrelevant. There is work in progress in MAPREDUCE-6225 .
          Hide
          iwasakims Masatake Iwasaki added a comment -

          I did not add tests because the existing tests in TestJobConf cover the change.

          Show
          iwasakims Masatake Iwasaki added a comment - I did not add tests because the existing tests in TestJobConf cover the change.
          Hide
          iwasakims Masatake Iwasaki added a comment -

          I missed MAPREDUCE-6223 which seems to be related. I could not reproduce the failure in TestJobConf of hadoop-mapreduce-client-jobclient with the patch of this issue.

          Show
          iwasakims Masatake Iwasaki added a comment - I missed MAPREDUCE-6223 which seems to be related. I could not reproduce the failure in TestJobConf of hadoop-mapreduce-client-jobclient with the patch of this issue.
          Hide
          ajisakaa Akira Ajisaka added a comment -

          Looks good to me. The patch also fixes TestJobConf reported by MAPREDUCE-6223.

          Show
          ajisakaa Akira Ajisaka added a comment - Looks good to me. The patch also fixes TestJobConf reported by MAPREDUCE-6223 .
          Hide
          ozawa Tsuyoshi Ozawa added a comment -

          Masatake Iwasaki thank you for taking this JIRA. Currently, -1 for this fix.

          I think we should fix test side to follow default configuration since the assertion only check whether check if the high ram properties are not set.

              // check if the high ram properties are not set
              assertEquals(expectedMapMB, 
                           simulatedConf.getLong(MRJobConfig.MAP_MEMORY_MB,
                                                 MRJobConfig.DEFAULT_MAP_MEMORY_MB));
              assertEquals(expectedReduceMB, 
                           simulatedConf.getLong(MRJobConfig.REDUCE_MEMORY_MB, 
                                                 MRJobConfig.DEFAULT_MAP_MEMORY_MB));
          

          We should also rethink what we should test in TestHighRamJob - it refers JT_MAX_MAPMEMORY_MB or some old configurations. Do we really need this tests?

          Show
          ozawa Tsuyoshi Ozawa added a comment - Masatake Iwasaki thank you for taking this JIRA. Currently, -1 for this fix. I think we should fix test side to follow default configuration since the assertion only check whether check if the high ram properties are not set. // check if the high ram properties are not set assertEquals(expectedMapMB, simulatedConf.getLong(MRJobConfig.MAP_MEMORY_MB, MRJobConfig.DEFAULT_MAP_MEMORY_MB)); assertEquals(expectedReduceMB, simulatedConf.getLong(MRJobConfig.REDUCE_MEMORY_MB, MRJobConfig.DEFAULT_MAP_MEMORY_MB)); We should also rethink what we should test in TestHighRamJob - it refers JT_MAX_MAPMEMORY_MB or some old configurations. Do we really need this tests?
          Hide
          ozawa Tsuyoshi Ozawa added a comment -

          s/whether check if the high ram properties are not set./whether the high ram properties are set./

          Show
          ozawa Tsuyoshi Ozawa added a comment - s/whether check if the high ram properties are not set./whether the high ram properties are set./
          Hide
          iwasakims Masatake Iwasaki added a comment -

          I agree that the code of gridmix should be updated. But I think it is very confusing that MRJobConfig.DEFAULT_MAP_MEMORY_MB is not same with the value of mapreduce.map.memory.mb in mapred-default.xml and it should be fixed without regarding to the test failure of gridmix.

          Show
          iwasakims Masatake Iwasaki added a comment - I agree that the code of gridmix should be updated. But I think it is very confusing that MRJobConfig.DEFAULT_MAP_MEMORY_MB is not same with the value of mapreduce.map.memory.mb in mapred-default.xml and it should be fixed without regarding to the test failure of gridmix.
          Hide
          ozawa Tsuyoshi Ozawa added a comment -

          Make sense.

          Gera Shegalov, do you know the reason that DEFAULT_MAP_MEMORY_MB is not updated in MAPREDUCE-5785? If there is no reason, I think we can apply this patch to trunk.

          Show
          ozawa Tsuyoshi Ozawa added a comment - Make sense. Gera Shegalov , do you know the reason that DEFAULT_MAP_MEMORY_MB is not updated in MAPREDUCE-5785 ? If there is no reason, I think we can apply this patch to trunk.
          Hide
          jira.shegalov Gera Shegalov added a comment -

          I apologize, I am a little tied up right now to do a thorough review. Looking into resolving this is on my list. I was thinking that direct references to to DEFAULT_*_MEMORY_MB should be wrapped in a single method. Maybe Karthik Kambatla can chime in in the meantime.

          Show
          jira.shegalov Gera Shegalov added a comment - I apologize, I am a little tied up right now to do a thorough review. Looking into resolving this is on my list. I was thinking that direct references to to DEFAULT_*_MEMORY_MB should be wrapped in a single method. Maybe Karthik Kambatla can chime in in the meantime.
          Hide
          iwasakims Masatake Iwasaki added a comment -

          .002 addresses my comment in MAPREDUCE-6223. Tests needing default value in conf can use MRJobConfig.DEFAULT_MAP_MEMORY_MB and test needing the value processed by JobConf#getMemoryRequired can use JobConf.DEFAULT_MAP_MEMORY_REQUIRED.

          Show
          iwasakims Masatake Iwasaki added a comment - .002 addresses my comment in MAPREDUCE-6223 . Tests needing default value in conf can use MRJobConfig.DEFAULT_MAP_MEMORY_MB and test needing the value processed by JobConf#getMemoryRequired can use JobConf.DEFAULT_MAP_MEMORY_REQUIRED .
          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/12696990/MAPREDUCE-6234.002.patch
          against trunk revision 02f154a.

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

          -1 tests included. The patch doesn't appear to include any new or modified tests.
          Please justify why no new tests are needed for this patch.
          Also please list what manual steps were performed to verify this patch.

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

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          -1 findbugs. The patch appears to introduce 13 new Findbugs (version 2.0.3) warnings.

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

          +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.

          Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5172//testReport/
          Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5172//artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
          Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5172//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/12696990/MAPREDUCE-6234.002.patch against trunk revision 02f154a. +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. -1 findbugs . The patch appears to introduce 13 new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5172//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5172//artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5172//console This message is automatically generated.
          Hide
          varun_saxena Varun Saxena added a comment -

          Tsuyoshi Ozawa,
          Below is the description of the config.

          <description>
            The amount of memory to request from the scheduler for each 		
            map task. If this is not specified or is non-positive, it is inferred from
            mapreduce.map.java.opts and mapreduce.job.heap.memory-mb.ratio.
            If java-opts are also not specified, we set it to 1024.
          </description>
          

          -1 basically indicates map memory has to be taken from java opts first. And if not found, will be set as 1024 by default. So effective default value is 1024(if java opts don't exist). This is mentioned in config description.
          I don't think not making DEFAULT_MAP_MEMORY_MB as -1 is an oversight. That is how the developer has written the code. It had an impact on TestJobConf in hadoop-mapreduce-jobclient though. MAPREDUCE-6239 is raised to address consolidating of two TestJobConf classes.

          Maybe MAPREDUCE-6223 can fix the test case failure and this can address making it consistent.
          Thoughts ?

          Show
          varun_saxena Varun Saxena added a comment - Tsuyoshi Ozawa , Below is the description of the config. <description> The amount of memory to request from the scheduler for each map task. If this is not specified or is non-positive, it is inferred from mapreduce.map.java.opts and mapreduce.job.heap.memory-mb.ratio. If java-opts are also not specified, we set it to 1024. </description> -1 basically indicates map memory has to be taken from java opts first. And if not found, will be set as 1024 by default. So effective default value is 1024(if java opts don't exist). This is mentioned in config description. I don't think not making DEFAULT_MAP_MEMORY_MB as -1 is an oversight. That is how the developer has written the code. It had an impact on TestJobConf in hadoop-mapreduce-jobclient though. MAPREDUCE-6239 is raised to address consolidating of two TestJobConf classes. Maybe MAPREDUCE-6223 can fix the test case failure and this can address making it consistent. Thoughts ?
          Hide
          iwasakims Masatake Iwasaki added a comment -

          Varun Saxena, some tests need not "effective default value" but value literally set in conf. The name DEFAULT_MAP_MEMORY_MB implies the default value of "mapreduce.map.memory.mb". 1024 is the value defermined from "mapreduce.map.memory.mb" and "mapreduce.map.java.opts". If we need the 1024 in some constants, it should not be named as DEFAULT_MAP_MEMORY_MB. The .002 patch addresses this.

          Show
          iwasakims Masatake Iwasaki added a comment - Varun Saxena , some tests need not "effective default value" but value literally set in conf. The name DEFAULT_MAP_MEMORY_MB implies the default value of "mapreduce.map.memory.mb". 1024 is the value defermined from "mapreduce.map.memory.mb" and "mapreduce.map.java.opts". If we need the 1024 in some constants, it should not be named as DEFAULT_MAP_MEMORY_MB. The .002 patch addresses this.
          Hide
          varun_saxena Varun Saxena added a comment -

          Masatake Iwasaki, I am not saying that we should or should not make DEFAULT_MAP_MEMORY_MB -1. We can probably make it consistent(as other configs are) and use another constant for 1024. I am frankly fine either ways.

          Answering to Tsuyoshi Ozawa's comment, I meant this probably wasn't an oversight while fixing MAPREDUCE-5785 because code seems to be written in a manner where value of 1024 in DEFAULT_MAP_MEMORY_MB is necessary(as per current code).

          As Gera said, probably Karthik can chime in on this one.

          Show
          varun_saxena Varun Saxena added a comment - Masatake Iwasaki , I am not saying that we should or should not make DEFAULT_MAP_MEMORY_MB -1. We can probably make it consistent(as other configs are) and use another constant for 1024. I am frankly fine either ways. Answering to Tsuyoshi Ozawa 's comment, I meant this probably wasn't an oversight while fixing MAPREDUCE-5785 because code seems to be written in a manner where value of 1024 in DEFAULT_MAP_MEMORY_MB is necessary(as per current code). As Gera said, probably Karthik can chime in on this one.
          Hide
          iwasakims Masatake Iwasaki added a comment -

          Thanks for the clarification, Varun Saxena. I might misunderstand that you don't agree the change by comment beggining with "-1"

          Show
          iwasakims Masatake Iwasaki added a comment - Thanks for the clarification, Varun Saxena . I might misunderstand that you don't agree the change by comment beggining with "-1"
          Hide
          kasha Karthik Kambatla added a comment -

          Thanks for working on this, folks. As you might see in the description of the config, it is kind of hard to pick a single value for DEFAULT_MAP_MEMORY_MB, and the most appropriate value seemed 1024 since we fallback to that value. I like Gera's proposal of adding a helper method to get the default value; however, I wonder if that would just translate to calling JobConf#getMemoryRequired on the default conf.

          Show
          kasha Karthik Kambatla added a comment - Thanks for working on this, folks. As you might see in the description of the config, it is kind of hard to pick a single value for DEFAULT_MAP_MEMORY_MB, and the most appropriate value seemed 1024 since we fallback to that value. I like Gera's proposal of adding a helper method to get the default value; however, I wonder if that would just translate to calling JobConf#getMemoryRequired on the default conf.
          Hide
          iwasakims Masatake Iwasaki added a comment -

          003 fixes test failure without changing the value of DEFAULT_*_MEMORY_MB.

          Show
          iwasakims Masatake Iwasaki added a comment - 003 fixes test failure without changing the value of DEFAULT_*_MEMORY_MB.
          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/12697632/MAPREDUCE-6234.003.patch
          against trunk revision 260b5e3.

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

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

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

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings.

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

          +1 core tests. The patch passed unit tests in hadoop-tools/hadoop-gridmix.

          Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5179//testReport/
          Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5179//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/12697632/MAPREDUCE-6234.003.patch against trunk revision 260b5e3. +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-tools/hadoop-gridmix. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5179//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5179//console This message is automatically generated.
          Hide
          kasha Karthik Kambatla added a comment -

          +1. Checking this in.

          Show
          kasha Karthik Kambatla added a comment - +1. Checking this in.
          Hide
          kasha Karthik Kambatla added a comment -

          Just committed this to trunk. Thanks Masatake for fixing this, Gera and Tsuyoshi for your reviews.

          Show
          kasha Karthik Kambatla added a comment - Just committed this to trunk. Thanks Masatake for fixing this, Gera and Tsuyoshi for your reviews.
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-trunk-Commit #7136 (See https://builds.apache.org/job/Hadoop-trunk-Commit/7136/)
          MAPREDUCE-6234. TestHighRamJob fails due to the change in MAPREDUCE-5785. (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0)

          • hadoop-mapreduce-project/CHANGES.txt
          • hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-trunk-Commit #7136 (See https://builds.apache.org/job/Hadoop-trunk-Commit/7136/ ) MAPREDUCE-6234 . TestHighRamJob fails due to the change in MAPREDUCE-5785 . (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0) hadoop-mapreduce-project/CHANGES.txt hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Yarn-trunk #842 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/842/)
          MAPREDUCE-6234. TestHighRamJob fails due to the change in MAPREDUCE-5785. (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0)

          • hadoop-mapreduce-project/CHANGES.txt
          • hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Yarn-trunk #842 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/842/ ) MAPREDUCE-6234 . TestHighRamJob fails due to the change in MAPREDUCE-5785 . (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0) hadoop-mapreduce-project/CHANGES.txt hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #108 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/108/)
          MAPREDUCE-6234. TestHighRamJob fails due to the change in MAPREDUCE-5785. (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0)

          • hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          • hadoop-mapreduce-project/CHANGES.txt
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #108 (See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/108/ ) MAPREDUCE-6234 . TestHighRamJob fails due to the change in MAPREDUCE-5785 . (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0) hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java hadoop-mapreduce-project/CHANGES.txt
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #99 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/99/)
          MAPREDUCE-6234. TestHighRamJob fails due to the change in MAPREDUCE-5785. (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0)

          • hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          • hadoop-mapreduce-project/CHANGES.txt
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #99 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/99/ ) MAPREDUCE-6234 . TestHighRamJob fails due to the change in MAPREDUCE-5785 . (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0) hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java hadoop-mapreduce-project/CHANGES.txt
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Hadoop-Hdfs-trunk #2040 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2040/)
          MAPREDUCE-6234. TestHighRamJob fails due to the change in MAPREDUCE-5785. (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0)

          • hadoop-mapreduce-project/CHANGES.txt
          • hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-Hdfs-trunk #2040 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2040/ ) MAPREDUCE-6234 . TestHighRamJob fails due to the change in MAPREDUCE-5785 . (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0) hadoop-mapreduce-project/CHANGES.txt hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #109 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/109/)
          MAPREDUCE-6234. TestHighRamJob fails due to the change in MAPREDUCE-5785. (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0)

          • hadoop-mapreduce-project/CHANGES.txt
          • hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #109 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/109/ ) MAPREDUCE-6234 . TestHighRamJob fails due to the change in MAPREDUCE-5785 . (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0) hadoop-mapreduce-project/CHANGES.txt hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          Hide
          hudson Hudson added a comment -

          FAILURE: Integrated in Hadoop-Mapreduce-trunk #2059 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2059/)
          MAPREDUCE-6234. TestHighRamJob fails due to the change in MAPREDUCE-5785. (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0)

          • hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java
          • hadoop-mapreduce-project/CHANGES.txt
          Show
          hudson Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk #2059 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2059/ ) MAPREDUCE-6234 . TestHighRamJob fails due to the change in MAPREDUCE-5785 . (Masatake Iwasaki via kasha) (kasha: rev 409113d8f97fcfdb96cb028dbb6a20c9a1df81b0) hadoop-tools/hadoop-gridmix/src/test/java/org/apache/hadoop/mapred/gridmix/TestHighRamJob.java hadoop-mapreduce-project/CHANGES.txt
          Hide
          andrew.wang Andrew Wang added a comment -

          Should this change be marked incompatible? Sounds like it's fixing an issue only presented by MAPREDUCE-5785, which is already marked incompatible and only checked into trunk.

          Show
          andrew.wang Andrew Wang added a comment - Should this change be marked incompatible? Sounds like it's fixing an issue only presented by MAPREDUCE-5785 , which is already marked incompatible and only checked into trunk.
          Hide
          ajisakaa Akira Ajisaka added a comment -

          I'm thinking this change should not be marked as incompatible change. Removing the flag.

          Show
          ajisakaa Akira Ajisaka added a comment - I'm thinking this change should not be marked as incompatible change. Removing the flag.

            People

            • Assignee:
              iwasakims Masatake Iwasaki
              Reporter:
              iwasakims Masatake Iwasaki
            • Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development