[
https://issues.apache.org/jira/browse/HBASE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787435#comment-13787435
]
Hadoop QA commented on HBASE-9645:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12607040/HBASE_9645-0.94.10.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7477//console
This message is automatically generated.
> Regionserver halt because of HLog's "Logic Error Snapshot seq id from earlier
> flush still present!"
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-9645
> URL: https://issues.apache.org/jira/browse/HBASE-9645
> Project: HBase
> Issue Type: Bug
> Components: regionserver, wal
> Affects Versions: 0.94.10
> Environment: Linux 2.6.32-el5.x86_64
> Reporter: Victor Xu
> Priority: Critical
> Attachments: HBASE_9645-0.94.10.patch
>
>
> I upgrade my hbase cluster to 0.94.10 three weeks ago, and this case happened
> several days after that. I change the bug's priority to 'Critical' because
> every time it happens, a regionserver halt down. All of them have the same
> log:
> {noformat}
> ERROR org.apache.hadoop.hbase.regionserver.wal.HLog: Logic Error Snapshot seq
> id from earlier flush still present! for region
> c0d88db4ce3606842fbec9d34c38f707 overwritten oldseq=80114270537with new
> seq=80115066829
> {noformat}
> I check the code finding that it locates at HLog.startCacheFlush method. The
> 'lastSeqWritten' has been locked. Maybe something wrong happened outside the
> HLog that change it by mistake.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
