hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14257) Periodic flusher only handles hbase:meta, not other system tables
Date Thu, 20 Aug 2015 20:19:48 GMT

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

Hadoop QA commented on HBASE-14257:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against master branch at commit 720f2a88154653a13892b36997129d3f77fc9702.
  ATTACHMENT ID: 12751423

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of
protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

    {color:red}-1 site{color}.  The patch appears to cause mvn post-site goal to fail.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:

     {color:red}-1 core zombie tests{color}.  There are 17 zombie test(s): 	at org.apache.hadoop.hbase.replication.regionserver.TestReplicationWALReaderManager.test(TestReplicationWALReaderManager.java:186)
	at org.apache.hadoop.hbase.client.TestHCM.testOperationTimeout(TestHCM.java:306)
	at org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer.testWithCluster(TestStochasticLoadBalancer.java:656)
	at org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer.testRegionReplicationOnMidClusterSameHosts(TestStochasticLoadBalancer.java:583)
	at org.apache.hadoop.hbase.replication.TestReplicationDisableInactivePeer.testDisableInactivePeer(TestReplicationDisableInactivePeer.java:79)

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15195//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15195//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15195//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15195//console

This message is automatically generated.

> Periodic flusher only handles hbase:meta, not other system tables
> -----------------------------------------------------------------
>                 Key: HBASE-14257
>                 URL: https://issues.apache.org/jira/browse/HBASE-14257
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 2.0.0, 1.2.0
>            Reporter: Lars George
>            Assignee: Abhishek Singh Chouhan
>              Labels: beginner
>         Attachments: HBASE-14257.patch
> In {{HRegion.shouldFlush}} we have
> {code}
>     long modifiedFlushCheckInterval = flushCheckInterval;
>     if (getRegionInfo().isMetaRegion() &&
>         getRegionInfo().getReplicaId() == HRegionInfo.DEFAULT_REPLICA_ID) {
>       modifiedFlushCheckInterval = META_CACHE_FLUSH_INTERVAL;
>     }
> {code}
> That method is called by the {{PeriodicMemstoreFlusher}} thread, and prefers the {{hbase:meta}}
only for faster flushing. It should be doing the same for other system tables. I suggest to
use {{HRI.isSystemTable()}}.

This message was sent by Atlassian JIRA

View raw message