[
https://issues.apache.org/jira/browse/HBASE-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-9740:
---------------------------------
Fix Version/s: (was: 0.94.19)
0.94.20
I am going to push this one more (last hopefully) time.
The issue is that as long as we have the region in transition we know we have
something to do. With this we no longer have that after a while and that would
be a behavior change in 0.94.
Not saying it's wrong, but I would like to discuss this aspect.
> A corrupt HFile could cause endless attempts to assign the region without a
> chance of success
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-9740
> URL: https://issues.apache.org/jira/browse/HBASE-9740
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.16
> Reporter: Aditya Kishore
> Assignee: Ping
> Fix For: 0.94.20
>
> Attachments: HBase-9740_0.94_v4.patch, HBase-9749_0.94_v2.patch,
> HBase-9749_0.94_v3.patch, patch-9740_0.94.txt
>
>
> As described in HBASE-9737, a corrupt HFile in a region could lead to an
> assignment storm in the cluster since the Master will keep trying to assign
> the region to each region server one after another and obviously none will
> succeed.
> The region server, upon detecting such a scenario should mark the region as
> "RS_ZK_REGION_FAILED_ERROR" (or something to the effect) in the Zookeeper
> which should indicate the Master to stop assigning the region until the error
> has been resolved (via an HBase shell command, probably "assign"?)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
