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

stack commented on HBASE-13895:
-------------------------------

+1 I was thinking that a possible intent of yours in your master addendum. 
Makes sense... hang around till server dies for sure.

Let me do in subissue. I've made a mess of this issue.

> DATALOSS: Region assigned before WAL replay when abort
> ------------------------------------------------------
>
>                 Key: HBASE-13895
>                 URL: https://issues.apache.org/jira/browse/HBASE-13895
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0, 1.2.0, 1.1.2, 1.3.0
>
>         Attachments: 13895.branch-1.2.txt, 13895.master.addendum2.txt, 
> 13895.master.patch, hbase-13895_addendum-master.patch, 
> hbase-13895_addendum.patch, hbase-13895_addendum3-branch-1.1.patch, 
> hbase-13895_addendum3-branch-1.patch, hbase-13895_addendum3-master.patch, 
> hbase-13895_v1-branch-1.1.patch
>
>
> Opening a place holder till finish analysis.
> I have dataloss running ITBLL at 3B (testing HBASE-13877). Most obvious 
> culprit is the double-assignment that I can see.



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

Reply via email to