[
https://issues.apache.org/jira/browse/HBASE-20242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430826#comment-16430826
]
Hudson commented on HBASE-20242:
--------------------------------
Results for branch branch-2
[build #590 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/590/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/590//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/590//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/590//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> The open sequence number will grow if we fail to open a region after writing
> the max sequence id file
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-20242
> URL: https://issues.apache.org/jira/browse/HBASE-20242
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20242.patch
>
>
> We write the current max sequence id plus one as the new max sequence id so
> if we fail before report RIT to master, when assign next time the open
> sequence number will increase by one.
> But it is possible that we fail before writing the open region marker so
> there will no actual WAL with the sequence id which is the open sequence
> number minus one. This will cause the serial replication to be stuck.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
