You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/03/05 08:54:33 UTC
[jira] [Commented] (HBASE-7867) setPreallocSize is different with
COMMENT in setupTestEnv in MiniZooKeeperCluster.java
[ https://issues.apache.org/jira/browse/HBASE-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593191#comment-13593191 ]
Hudson commented on HBASE-7867:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #12 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/12/])
HBASE-7867 setPreallocSize is different with COMMENT in setupTestEnv in MiniZooKeeperCluster.java (DaeMyung Kang) (Revision 1447105)
Result = FAILURE
larsh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/zookeeper/MiniZooKeeperCluster.java
> setPreallocSize is different with COMMENT in setupTestEnv in MiniZooKeeperCluster.java
> --------------------------------------------------------------------------------------
>
> Key: HBASE-7867
> URL: https://issues.apache.org/jira/browse/HBASE-7867
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.0, 0.94.6
> Reporter: DaeMyung Kang
> Assignee: DaeMyung Kang
> Priority: Trivial
> Fix For: 0.95.0, 0.94.6
>
> Attachments: hbase-7867.patch, hbase-7867.patch
>
>
> setupTestEnv() just sets 100 bytes not 100k bytes
> {code}
> private static void setupTestEnv() {
> // / XXX: From o.a.zk.t.ClientBaseprivate static void setupTestEnv() {
> // during the tests we run with 100K prealloc in the logs.
> // on windows systems prealloc of 64M was seen to take ~15seconds
> // resulting in test failure (client timeout on first session).
> // set env and directly in order to handle static init/gc issues
> System.setProperty("zookeeper.preAllocSize", "100");
> FileTxnLog.setPreallocSize(100);
> }
> {code}
> to reduce too many call padLogFile(), I think 100k is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira