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-11109) flush region sequence id may not be larger than all edits flushed
Date Mon, 05 May 2014 00:20:15 GMT

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

Hadoop QA commented on HBASE-11109:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12643243/11109v2.txt
  against trunk revision .
  ATTACHMENT ID: 12643243

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

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

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

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

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) 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:green}+1 site{color}.  The mvn site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.regionserver.wal.TestLogRolling

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/9458//console

This message is automatically generated.

> flush region sequence id may not be larger than all edits flushed
> -----------------------------------------------------------------
>
>                 Key: HBASE-11109
>                 URL: https://issues.apache.org/jira/browse/HBASE-11109
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>    Affects Versions: 0.99.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.99.0
>
>         Attachments: 11109.txt, 11109v2.txt, 11109v2.txt
>
>
> This was found by [~jeffreyz]  See parent issue.  We have this issue since we put the
ring buffer/disrupter into the WAL (HBASE-10156).
> An edits region sequence id is set only after the edit has traversed the ring buffer.
 Flushing, we just up whatever the current region sequence id is.  Crossing the ring buffer
may take some time and is done by background threads.  The flusher may be taking the region
sequence id though edits have not yet made it across the ringbuffer: i.e. edits that are actually
scoped by the flush may have region sequence ids in excess of that of the flush sequence id
reported.
> The consequences are not exactly clear.  Would rather not have to find out so lets fix
this here.



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

Mime
View raw message