hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Huang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5631) hbck should handle case where .tableinfo file is missing.
Date Thu, 06 Sep 2012 01:50:07 GMT

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

Jie Huang commented on HBASE-5631:

Thanks Jonathan.

bq. Have you tried shutting down the cluster and then restarting it? I have a suspicion that
this may not work if the HTD isn't cached. 

Yes. you are right. This proposal only fixes .tableinfo files which have been already cached.
From my understanding,  we have no way to figure out the entire table information without
cache.  Another thought is that we can try to recover parts of the information(like. table
name, column-family name with some default properties). Meanwhile some warnings are printed
out since part of the information(what we guessed) may not be as accurate as before. Is there
any other suggestion? Please let me know.

bq. I wasn't consistent with error.print vs log. I think I prefer log. Any reason you picked
this vs the other?
I have hesitated between log and error.print before. I will change that in the next version.

> hbck should handle case where .tableinfo file is missing.
> ---------------------------------------------------------
>                 Key: HBASE-5631
>                 URL: https://issues.apache.org/jira/browse/HBASE-5631
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck
>    Affects Versions: 0.92.2, 0.94.0, 0.96.0
>            Reporter: Jonathan Hsieh
>            Assignee: Jie Huang
>         Attachments: hbase-5631.patch
> 0.92+ branches have a .tableinfo file which could be missing from hdfs.  hbck should
be able to detect and repair this properly.

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