hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9645) Regionserver halt because of HLog's "Logic Error Snapshot seq id from earlier flush still present!"
Date Thu, 24 Oct 2013 10:30:04 GMT

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

Hudson commented on HBASE-9645:
-------------------------------

SUCCESS: Integrated in HBase-TRUNK #4642 (See [https://builds.apache.org/job/HBase-TRUNK/4642/])
HBASE-9645 Regionserver halt because of HLogs "Logic Error Snapshot seq id from earlier flush
still present" (stack: rev 1535288)
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java


> 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
>             Fix For: 0.98.0
>
>         Attachments: 9645v2.txt, 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)

Mime
View raw message