hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rajeshbabu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6229) AM.assign() should not set table state to ENABLED directly.
Date Mon, 18 Jun 2012 15:16:42 GMT

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

rajeshbabu commented on HBASE-6229:

Attached patch for 94 and trunk. Please review and provide comments/suggestions.
> AM.assign() should not set table state to ENABLED directly.
> -----------------------------------------------------------
>                 Key: HBASE-6229
>                 URL: https://issues.apache.org/jira/browse/HBASE-6229
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.2, 0.94.1
>            Reporter: rajeshbabu
>            Assignee: rajeshbabu
>             Fix For: 0.96.0, 0.94.1, 0.92.3
>         Attachments: HBASE-6229_94.patch, HBASE-6229_trunk.patch
> In case of assign from EnableTableHandler table state is ENABLING. Any how EnableTableHandler
will set ENABLED after assigning all the the table regions. If we try to set to ENABLED directly
then client api may think ENABLE table is completed. When we have a case like all the regions
are added directly into META and we call assignRegion then we need to make the table ENABLED.
 Hence in such case the table will not be in ENABLING or ENABLED state.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message