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

stack updated HBASE-21369:
--------------------------
    Description: 
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.

  was:
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.


> [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: stack
>            Priority: Major
>
> 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
(v7.6.3#76005)

Reply via email to