hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Bertozzi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9233) isTableAvailable() may be stuck if an offline parent was never assigned
Date Thu, 15 Aug 2013 21:06:59 GMT

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

Matteo Bertozzi commented on HBASE-9233:

{quote}For the trunk one, there is another place (isTableAvailable w/ splitKeys) to fix?{quote}
Yeah, as it is used it should be fine, since is just checking if the table was created with
the specified number of region/splits...

but if you use it in a generic way and you have parent regions and you don't exclude them
(aside from the available that will be false) how can you ever met the condition: (regionCount.get()
== splitKeys.length + 1)
> isTableAvailable() may be stuck if an offline parent was never assigned
> -----------------------------------------------------------------------
>                 Key: HBASE-9233
>                 URL: https://issues.apache.org/jira/browse/HBASE-9233
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, Region Assignment
>    Affects Versions: 0.98.0, 0.95.1, 0.94.10
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Critical
>             Fix For: 0.98.0, 0.94.12, 0.96.0
>         Attachments: HBASE-9233-0.94-v0.patch, HBASE-9233-trunk-v0.patch
> HConnectionManager.isTableAvailable() the SERVER_QUALIFIER for each region, including
the offline split parent.
> In case of hbck META recovery or snapshots clone/restore an offline parent will never
be assigned (since should stay offline). In this case HBaseAdmin.waitUntilTableIsEnabled()
used by enable() and cloneSnapshot() will wait until the timeout is expired.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message