hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12485) Maintain SeqId monotonically increasing
Date Sat, 06 Dec 2014 05:54:12 GMT

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

stack commented on HBASE-12485:
-------------------------------

Nice find on bug in code over recovered.edits.

bq. This will cause issue for rollback and during upgrade if a user uses old hbck.

Rollback is not supported.

Is hbck supposed to work during a rolling upgrade?  Would it be too much to expect that an
operator use the newer version of hbck during an upgrade?

Do you mean to write '.sqeid' or do you intend to write '.seqid'?

Just trying to minimize the different ways in which we designate 'special files'





> Maintain SeqId monotonically increasing
> ---------------------------------------
>
>                 Key: HBASE-12485
>                 URL: https://issues.apache.org/jira/browse/HBASE-12485
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 1.0.0, 2.0.0
>
>         Attachments: HBASE-12485.patch
>
>
> We added FLUSH, REGION CLOSE events into WAL, for each those events the region SeqId
is bumped. 
> The issue comes from region close operation. Because when opening a region, we use flushed
SeqId from store files while after store flush during region close we still write COMMIT_FLUSH,
REGION_CLOSE events etc which respectively bump up SeqId. Therefore, the region opening SeqId
is lower than it should be.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message