accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1172) Increase metadata table split threshold
Date Sat, 16 Mar 2013 00:52:16 GMT

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

Hudson commented on ACCUMULO-1172:
----------------------------------

Integrated in Accumulo-Trunk-Hadoop-2.0 #137 (See [https://builds.apache.org/job/Accumulo-Trunk-Hadoop-2.0/137/])
    #ACCUMULO-1172 increased default metadata table split threshold (Revision 1456984)

     Result = ABORTED
kturner : 
Files : 
* /accumulo/trunk
* /accumulo/trunk/assemble
* /accumulo/trunk/conf/examples/3GB/native-standalone/accumulo-site.xml
* /accumulo/trunk/conf/examples/3GB/standalone/accumulo-site.xml
* /accumulo/trunk/core
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/conf/Property.java
* /accumulo/trunk/examples
* /accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/ZooStore.java
* /accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/zookeeper/ZooSession.java
* /accumulo/trunk/server
* /accumulo/trunk/server/src/main/java/org/apache/accumulo/server/util/Initialize.java
* /accumulo/trunk/src

                
> Increase metadata table split threshold
> ---------------------------------------
>
>                 Key: ACCUMULO-1172
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1172
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> The metadata table split threshold is initialized to 4M.  This is very small and can
cause a system to have alots of metadata table tablets.  This was set small a long time ago
when tablets did not have read parallelism.  That has not been the case for a long time, but
this threshold is still small.  I propose increasing it to 64M or 128M.

--
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

Mime
View raw message