You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (Jira)" <ji...@apache.org> on 2021/02/20 07:02:00 UTC
[jira] [Updated] (HBASE-21369) [hbase-operator-tools] Create a tool
that will write the versions file
[ https://issues.apache.org/jira/browse/HBASE-21369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey updated HBASE-21369:
--------------------------------
Fix Version/s: (was: hbase-operator-tools-1.1.0)
hbase-operator-tools-1.2.0
> [hbase-operator-tools] Create a tool that will write the versions file
> ----------------------------------------------------------------------
>
> Key: HBASE-21369
> URL: https://issues.apache.org/jira/browse/HBASE-21369
> Project: HBase
> Issue Type: Task
> Components: hbase-operator-tools
> Reporter: Michael Stack
> Priority: Major
> Fix For: hbase-operator-tools-1.2.0
>
>
> hbck1 has the facility for restoring the hbase.version file under /hbase if it goes missing. This issue is about building a dedicated tool to do this in hbase-operator-tools or making use of hbck1 as is to do it and document how in refguide.
> For description, see http://hbase.apache.org/book.html#_special_cases_hbase_version_file_is_missing
> As is, we have a regression in our fixup tooling.
> Perhaps we create general fs fixup tool? It would do the above and then some.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)