[
https://issues.apache.org/jira/browse/HBASE-11430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046727#comment-14046727
]
Hudson commented on HBASE-11430:
--------------------------------
SUCCESS: Integrated in HBase-0.98 #363 (See
[https://builds.apache.org/job/HBase-0.98/363/])
HBASE-11430: lastFlushSeqId has been updated wrongly during region open
(jeffreyz: rev a543e39473878030fc0c1edd837c2debad0e0b80)
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> lastFlushSeqId has been updated wrongly during region open
> ----------------------------------------------------------
>
> Key: HBASE-11430
> URL: https://issues.apache.org/jira/browse/HBASE-11430
> Project: HBase
> Issue Type: Bug
> Components: MTTR
> Affects Versions: 0.99.0, 0.98.3
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Fix For: 0.99.0, 0.98.4
>
> Attachments: hbase-11430.patch
>
>
> In HRegion this.lastFlushSeqId is updated when opening a region which is
> wrong and will cause issue in distributedLogReplay recovery mode(not in log
> splitting mode) because its value is bumped up for log replay mode.
> This may cause data loss issue when we recover a region in
> distributedLogReplay mode while no flush for the region because no edits to
> be replayed. Later the region move to another region server and then future
> recovery will have issue because the large flush sequence Id value.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
