[
https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559201#comment-16559201
]
stack commented on HBASE-20893:
-------------------------------
So, Split does not support rollback at the
SPLIT_TABLE_REGIONS_CHECK_CLOSED_REGIONS stage. Rollback looks for
subprocedures, finds the unassign that just completed and tries to roll it back
(though it successfully closed the parent). This fails. You can't rollback a
successful unassign ... (the message is wrong.. it says assign)... at least not
currently. Let me try and fix or figure another soln here. The test that came
in with this patch is really helpful here. It indeed manufactures the problem
case of unaccounted Recovered.edits.... but it also (thankfully) manufactures
the failed rollback/CODE-BUG. Will be back.
> Data loss if splitting region while ServerCrashProcedure executing
> ------------------------------------------------------------------
>
> Key: HBASE-20893
> URL: https://issues.apache.org/jira/browse/HBASE-20893
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 3.0.0, 2.1.0, 2.0.1
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
> Fix For: 3.0.0, 2.0.2, 2.2.0, 2.1.1
>
> Attachments: HBASE-20893.branch-2.0.001.patch,
> HBASE-20893.branch-2.0.002.patch, HBASE-20893.branch-2.0.003.patch,
> HBASE-20893.branch-2.0.004.patch, HBASE-20893.branch-2.0.005.patch
>
>
> Similar case as HBASE-20878.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
