You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jimmy Xiang (JIRA)" <ji...@apache.org> on 2012/08/03 22:27:02 UTC

[jira] [Comment Edited] (HBASE-6507) [hbck] TestHBaseFsck ran into TableNotEnabledException

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

Jimmy Xiang edited comment on HBASE-6507 at 8/3/12 8:25 PM:
------------------------------------------------------------

setupTable pairs with deleteTable. The wait in setupTable should be minimal. The chance to hang in deleteTable could be higher. I thought about the timeout, but not sure what's a good number. We can start with 60s for small tests, 120s for big tests, if you agree.
                
      was (Author: jxiang):
    setupTable pairs with deleteTable. The wait in setupTable should be minimal. The chance to hang is deleteTable could be higher. I thought about the timeout, but sure what's a good number. We can start with 60s for small tests, 120s for big tests, if you agree.
                  
> [hbck] TestHBaseFsck ran into TableNotEnabledException
> ------------------------------------------------------
>
>                 Key: HBASE-6507
>                 URL: https://issues.apache.org/jira/browse/HBASE-6507
>             Project: HBase
>          Issue Type: Test
>          Components: hbck
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>         Attachments: trunk-6507.patch
>
>
> Here is one sample exception:
> {noformat}
> org.apache.hadoop.hbase.TableNotEnabledException: org.apache.hadoop.hbase.TableNotEnabledException: tableHDFSRegioininfoMissing
> 	at org.apache.hadoop.hbase.master.handler.DisableTableHandler.<init>(DisableTableHandler.java:75)
> 	at org.apache.hadoop.hbase.master.HMaster.disableTable(HMaster.java:1154)
> {noformat}

--
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