hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13895) DATALOSS: Double-assignment ITBLL'ing
Date Wed, 01 Jul 2015 23:16:05 GMT

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

Enis Soztutar commented on HBASE-13895:

bq. What you thinking on this one Enis Soztutar? Thanks.
Let's get this in. Let me update the patch because even in regular RS shutdown, it can happen
that the master tries to close the region, does an RPC, and the RPC throws RegionServerStoppedException.
AM continues to assign the region although there is no guarantee that the RS has actually
closed the region (thus everything is flushed). We start throwing RSSE while region server
is closing. There is no ordering guarantee for the regions to be actually closed. 

> DATALOSS: Double-assignment ITBLL'ing
> -------------------------------------
>                 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.1.2, 1.3.0, 1.2.1
>         Attachments: 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

View raw message