[ 
https://issues.apache.org/jira/browse/HBASE-10708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931182#comment-13931182
 ] 

Andrew Purtell commented on HBASE-10708:
----------------------------------------

Well I did a diff of 0.94.14 and head of branch-0.94, and this is the only 
change to HTU:
{code}
diff --git src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java 
src/test/java/org/apache/hadoop/hbase/HBas
index de3e132..f56aba1 100644
--- src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
+++ src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
@@ -1453,6 +1453,7 @@ public class HBaseTestingUtility {
     c.set("mapred.job.tracker", mrClusterJobConf.get("mapred.job.tracker"));
     /* this for mrv2 support */
     conf.set("mapreduce.framework.name", "yarn");
+    conf.setBoolean("yarn.is.minicluster", true);
     String rmAdress = mrClusterJobConf.get("yarn.resourcemanager.address");
     if (rmAdress != null) {
       conf.set("yarn.resourcemanager.address", rmAdress);
{code}

Does something OOME? Can you get a heap dump when that happens 
(-XX:-HeapDumpOnOutOfMemoryError)?

> Memory leak in HBaseTestingUtility
> ----------------------------------
>
>                 Key: HBASE-10708
>                 URL: https://issues.apache.org/jira/browse/HBASE-10708
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.94.16
>         Environment: Mac
>            Reporter: James Taylor
>
> I can no longer run the Phoenix unit tests on my Mac (OS X 10.8.5) using 
> Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609). It works 
> fine on HBase 0.94.14 and earlier. However, with later version, it gets 
> slower and slower and eventually dies.
> To repro, get the latest from the 3.0 branch of Phoenix and follow the maven 
> build instructions here: http://phoenix.incubator.apache.org/building.html
> It'll complete on 0.94.14 (in about 1 hr), but fail on later version.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to