hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-3713) Hmaster had crashed as disabling table
Date Fri, 01 Apr 2011 16:10:05 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-3713:
-------------------------

    Fix Version/s: 0.92.0

Thank you for digging in.  While I see the sequence described as being relatively 'rare' in
operation, it does expose a 'hole' that others might fall in to doing other than the above
described sequence.

> Hmaster had crashed as disabling table
> --------------------------------------
>
>                 Key: HBASE-3713
>                 URL: https://issues.apache.org/jira/browse/HBASE-3713
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.90.1
>         Environment: startup cluster with HA master and 5 datanode.
>            Reporter: gaojinchao
>             Fix For: 0.92.0
>
>
> Operation step:
> 1, startup cluster with HA master
> 2, the active master crashed while it is creating table with region 
> 3, backup master become active.
> 4, I want to drop the table
> 5, the active master crashed
> So the issue is that if a region was closed and disabled when the first master was running,
it won't be assigned anywhere and won't be in transition either (it's called being in RIT
in the code). When the new master comes around, and disable is called, it does a check to
see if the region is in RIT but not if it was already disabled, and fails on NPE because it's
not assigned to anyone.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message