hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wellington Chevreuil (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-25297) [HBCK2] Regenerate missing table descriptors by hbck2
Date Mon, 21 Dec 2020 12:53:01 GMT

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

Wellington Chevreuil resolved HBASE-25297.
------------------------------------------
    Resolution: Fixed

Merged into master. Thanks for the contribution, [~symat]!

> [HBCK2] Regenerate missing table descriptors by hbck2
> -----------------------------------------------------
>
>                 Key: HBASE-25297
>                 URL: https://issues.apache.org/jira/browse/HBASE-25297
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbase-operator-tools, hbck2
>    Affects Versions: hbase-operator-tools-1.0.0
>            Reporter: Mate Szalay-Beko
>            Assignee: Mate Szalay-Beko
>            Priority: Major
>             Fix For: hbase-operator-tools-1.1.0
>
>
> We just have been in a situation, when we saw many ServerCrashProcedure to be blocked,
because of the AssignProcedure is blocked because of the missing .tabledesc files.
> {code:java}
> java.io.IOException: Missing table descriptor for dd0676f57bdbff5d04ab735b7daf5e9b
> {code}
>  
> In our case it was OK for us to get rid of these tables and we were able to use {{setRegionState}}
to move all these regions to {{FAILED_OPEN}} state, then disable and drop the tables. But
this took a lot of time and we might not always have the option to drop these tables.
> HBCK 1 had a functionality (\{{fixTableOrphans}}) to regenerate the table descriptors
"according to the memory cache or hdfs table directory structure". We should investigate if
we can implement something like this with hbck2. We might not always be able to reproduce
the table configurations, but we can probably make a "basic" one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message