[
https://issues.apache.org/jira/browse/HBASE-20278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-20278.
-----------------------------------
Fix Version/s: 2.3.0
Assignee: Michael Stack (was: Umesh Agashe)
Resolution: Implemented
Resolving as implemented over in hbase-operator-tools in the hbck2 README:
https://github.com/apache/hbase-operator-tools/tree/master/hbase-hbck2
> [DOC] include ref guide updates for HBase 2.0 HBCK
> --------------------------------------------------
>
> Key: HBASE-20278
> URL: https://issues.apache.org/jira/browse/HBASE-20278
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, hbck
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Assignee: Michael Stack
> Priority: Critical
> Fix For: 2.3.0
>
>
> Called out by [~stack] in HBASE-19158
> {quote}
> bq. HBCK tool from an earlier release against an HBase 2.0+ cluster will
> destructively alter said cluster in unrecoverable ways.
> Footnote or callout that says something like "Unfortunately we are unable to
> distinguish an HBCK client so cannot put in place guards against destructive
> HBCK changes....." .... probably too much for this startup section on reread
> of what I've written here.
> bq. As of HBase 2.0, HBCK is a read-only tool that can report the status of
> some non-public system internals. You should not rely on the format nor
> content of these internals to remain consistent across HBase releases.
> Ugh. We need HBCK2 and a pointer here to it. Will do in a follow-on.
> {quote}
> then update the upgrade section to point to the docs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
