[jira] Updated: (HBASE-2522) Disabling a table during a split (tricky) can leave the daughter regions assigned and marked offline in .META.

["stack (JIRA)" <ji...@apache.org>]

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

stack updated HBASE-2522:
-------------------------

         Priority: Major  (was: Blocker)
    Fix Version/s:     (was: 0.90.0)

Downgrading priority and moving out of 0.90.0.  HBASE-3112 changed the way disable worked; e.g. we don't set 'offline' in meta any more when disabling a table. Also  we'll cycle until all regions of a table are disabled.  If a split while disabling, the second time around our disabling loop, we should pick up the daughters and give them the disable treatment.   One thing we could add is check of table state before opening daughters on split.  If is disabling or is disabled, that would prevent daughters being opened (Should be after they have added themselves to .META.).

Leaving this issue open since could do w/ unit test and we could implement the latter suggestion in the above.

> Disabling a table during a split (tricky) can leave the daughter regions assigned and marked offline in .META.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2522
>                 URL: https://issues.apache.org/jira/browse/HBASE-2522
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>
> If for any reason the master takes too much time to process a MSG_REPORT_SPLIT_INCLUDES_DAUGHTERS, and that a user successfully disables the table, then the daughter regions will still be assigned and marked as offline in .META.
> A test case I'm uploading to HBASE-2515 shows the issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.