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

Disable mem monitoring by default in MiniMRYarnCluster

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.3-alpha
    • Fix Version/s: 2.0.4-alpha
    • Component/s: None
    • Labels:
      None

      Description

      YARN-449. Some hbase tests were failing since containers were getting killed.
      I believe these checks are disabled by default on the branch-1 MiniMRCluster.

      1. MAPREDUCE-5094.txt
        3 kB
        Siddharth Seth
      2. MAPREDUCE-5094.txt
        3 kB
        Siddharth Seth
      3. MAPREDUCE-5094.txt
        3 kB
        Siddharth Seth

        Activity

        Hide
        stack added a comment -

        They are getting killed because they are using too much memory? So we would disable the check for too much memory use?

        Show
        stack added a comment - They are getting killed because they are using too much memory? So we would disable the check for too much memory use?
        Hide
        Siddharth Seth added a comment -

        Killed for exceeding vmem. PMEM is <300MB iirc, vmem going over 6GB - ideally, this should be investigated further.

        For now, proposing changing behaviour for MiniMRCluster memory monitoring back to what it was in 1.x (my guess is enabling the mem checks in 1.x would cause the same behaviour).

        Show
        Siddharth Seth added a comment - Killed for exceeding vmem. PMEM is <300MB iirc, vmem going over 6GB - ideally, this should be investigated further. For now, proposing changing behaviour for MiniMRCluster memory monitoring back to what it was in 1.x (my guess is enabling the mem checks in 1.x would cause the same behaviour).
        Hide
        Karthik Kambatla added a comment -

        Sid - can you share a sample test output? We might have seen something similar (not HBase), but it would be nice to confirm.

        Show
        Karthik Kambatla added a comment - Sid - can you share a sample test output? We might have seen something similar (not HBase), but it would be nice to confirm.
        Hide
        Siddharth Seth added a comment -

        https://issues.apache.org/jira/browse/YARN-449?focusedCommentId=13600632&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13600632
        Could you mention the environment - is this a running cluster, a system using MiniMRYarnCluster, etc ?

        The vmem values can vary depending on the env (configure vMemToPMemRatio accordingly). compressedoops, which I believe is enabled by default after a certain jvm version helps for 64bit JVMs.

        I'm not super happy about disabling mem checks either, one option would be to disable the VMEM check only. Downstream projects can enable these via the input conf if they really want to.
        Thoughts ?

        Show
        Siddharth Seth added a comment - https://issues.apache.org/jira/browse/YARN-449?focusedCommentId=13600632&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13600632 Could you mention the environment - is this a running cluster, a system using MiniMRYarnCluster, etc ? The vmem values can vary depending on the env (configure vMemToPMemRatio accordingly). compressedoops, which I believe is enabled by default after a certain jvm version helps for 64bit JVMs. I'm not super happy about disabling mem checks either, one option would be to disable the VMEM check only. Downstream projects can enable these via the input conf if they really want to. Thoughts ?
        Hide
        Karthik Kambatla added a comment -

        Thanks Sid. The failing tests use MiniMRCluster. At this point, it could very well be an issue with the test itself. The failures don't look the same. Will report when I have something concrete.

        Show
        Karthik Kambatla added a comment - Thanks Sid. The failing tests use MiniMRCluster. At this point, it could very well be an issue with the test itself. The failures don't look the same. Will report when I have something concrete.
        Hide
        stack added a comment -

        Can I configure the allowable vmem max allowed in my downstream project?

        Show
        stack added a comment - Can I configure the allowable vmem max allowed in my downstream project?
        Hide
        Hitesh Shah added a comment -

        @Stack, only max pmem is configurable directly but max vmem can be configured indirectly via the vmem-pmem ratio ( default ratio is 2.1 ).

        Show
        Hitesh Shah added a comment - @Stack, only max pmem is configurable directly but max vmem can be configured indirectly via the vmem-pmem ratio ( default ratio is 2.1 ).
        Hide
        Siddharth Seth added a comment -

        Patch disables VMEM monitoring by default. PMEM monitoring is enabled.

        Setting the parameters explicitly in conf is not enough - since the source of the configuration is not known (user or default). Controlling these values requires another parameter to be set.

        Show
        Siddharth Seth added a comment - Patch disables VMEM monitoring by default. PMEM monitoring is enabled. Setting the parameters explicitly in conf is not enough - since the source of the configuration is not known (user or default). Controlling these values requires another parameter to be set.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12577060/MAPREDUCE-5094.txt
        against trunk revision .

        +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. The javadoc tool did not generate any warning messages.

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

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

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

        -1 core tests. The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:

        org.apache.hadoop.mapred.TestMiniMRClientCluster

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3495//testReport/
        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3495//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12577060/MAPREDUCE-5094.txt against trunk revision . +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 . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. -1 core tests . The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient: org.apache.hadoop.mapred.TestMiniMRClientCluster +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3495//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3495//console This message is automatically generated.
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12577060/MAPREDUCE-5094.txt
        against trunk revision .

        +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. The javadoc tool did not generate any warning messages.

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

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3499//testReport/
        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3499//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12577060/MAPREDUCE-5094.txt against trunk revision . +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 . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3499//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3499//console This message is automatically generated.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        I believe these checks are disabled by default on the branch-1 MiniMRCluster.

        That is very right.

        Let's also disable pmem, no point in doing it for tests. If we want to validate the monitoring, specific tests should do that.

        Rename mapreduce.minicluster.control-resource-monitoring to mapreduce.minicluster.enable-memory-monitoring?

        Show
        Vinod Kumar Vavilapalli added a comment - I believe these checks are disabled by default on the branch-1 MiniMRCluster. That is very right. Let's also disable pmem, no point in doing it for tests. If we want to validate the monitoring, specific tests should do that. Rename mapreduce.minicluster.control-resource-monitoring to mapreduce.minicluster.enable-memory-monitoring?
        Hide
        Siddharth Seth added a comment -

        Thanks for the quick review.

        Let's also disable pmem, no point in doing it for tests. If we want to validate the monitoring, specific tests should do that.

        Done. I don't have a strong preference on enabling / disabling this by default for the miniMRCluster.

        Rename mapreduce.minicluster.control-resource-monitoring to mapreduce.minicluster.enable-memory-monitoring?

        I prefer the old name - since that applies to resoueces in general, and lets users control what they want (instead of an enable all).

        Show
        Siddharth Seth added a comment - Thanks for the quick review. Let's also disable pmem, no point in doing it for tests. If we want to validate the monitoring, specific tests should do that. Done. I don't have a strong preference on enabling / disabling this by default for the miniMRCluster. Rename mapreduce.minicluster.control-resource-monitoring to mapreduce.minicluster.enable-memory-monitoring? I prefer the old name - since that applies to resoueces in general, and lets users control what they want (instead of an enable all).
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12577118/MAPREDUCE-5094.txt
        against trunk revision .

        +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. The javadoc tool did not generate any warning messages.

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

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3502//testReport/
        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3502//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12577118/MAPREDUCE-5094.txt against trunk revision . +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 . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3502//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3502//console This message is automatically generated.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        Looks like this is the same patch the previous one, can you post an updated patch addressing my comment?

        Show
        Vinod Kumar Vavilapalli added a comment - Looks like this is the same patch the previous one, can you post an updated patch addressing my comment?
        Hide
        Siddharth Seth added a comment -

        Oops, looks like i uploaded the wrong file last time.
        Correct patch this time with the pmem check disabled.

        Show
        Siddharth Seth added a comment - Oops, looks like i uploaded the wrong file last time. Correct patch this time with the pmem check disabled.
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12578146/MAPREDUCE-5094.txt
        against trunk revision .

        +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. The javadoc tool did not generate any warning messages.

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

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3517//testReport/
        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3517//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12578146/MAPREDUCE-5094.txt against trunk revision . +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 . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3517//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3517//console This message is automatically generated.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        +1, this looks good. Checking it in.

        Show
        Vinod Kumar Vavilapalli added a comment - +1, this looks good. Checking it in.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        I just committed this to trunk, branch-2 and branch-2.0.4-alpha. Thanks Sid!

        Show
        Vinod Kumar Vavilapalli added a comment - I just committed this to trunk, branch-2 and branch-2.0.4-alpha. Thanks Sid!
        Hide
        Hudson added a comment -

        Integrated in Hadoop-trunk-Commit #3602 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3602/)
        MAPREDUCE-5094. Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124)

        Result = SUCCESS
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124
        Files :

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
        Show
        Hudson added a comment - Integrated in Hadoop-trunk-Commit #3602 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3602/ ) MAPREDUCE-5094 . Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Yarn-trunk #181 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/181/)
        MAPREDUCE-5094. Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124)

        Result = SUCCESS
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124
        Files :

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
        Show
        Hudson added a comment - Integrated in Hadoop-Yarn-trunk #181 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/181/ ) MAPREDUCE-5094 . Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-trunk #1370 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1370/)
        MAPREDUCE-5094. Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124)

        Result = FAILURE
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124
        Files :

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #1370 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1370/ ) MAPREDUCE-5094 . Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124) Result = FAILURE vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Mapreduce-trunk #1397 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1397/)
        MAPREDUCE-5094. Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124)

        Result = SUCCESS
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124
        Files :

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
        Show
        Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk #1397 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1397/ ) MAPREDUCE-5094 . Disabled memory monitoring by default in MiniMRYarnCluster to avoid some downstream tests failing. Contributed by Siddharth Seth. (Revision 1467124) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1467124 Files : /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRConfig.java /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java

          People

          • Assignee:
            Siddharth Seth
            Reporter:
            Siddharth Seth
          • Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development