[
https://issues.apache.org/jira/browse/HBASE-19121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628323#comment-16628323
]
Duo Zhang commented on HBASE-19121:
-----------------------------------
{quote}
At least for some basic operations, higher hbase version should be compatible
with lower HBCK2 version.
{quote}
[~allan163], the problem here is not higher HBase version with lower HBCK2
version, but higher HBCK2 version with lower HBase version. As the recovery
code are mainly placed in HBase, when we introduce new features in HBCK2, it
usually means that an old version of HBase can not support this feature, since
it does not have the new recovery code.
And I do not think it is a good idea to leave branch-2.0 and branch-2.1 there
without HBCK2 support. The users who are currently using these two minor
releases are good seed users, as usually the new major releases are not very
stable and they help testing them and make them stable. The decision of only
supporting HBCK2 on 2.2+ is not a good news to them, it seems that we just
throw them away...
And as I described above, what if later we add new methods to HbckService? We
immediately release 2.3 and drop 2.2? It does not make sense... The rule for a
patch release is not everything, at least for HBCK2 we should have something
different.
Thanks.
> HBCK for AMv2 (A.K.A HBCK2)
> ---------------------------
>
> Key: HBASE-19121
> URL: https://issues.apache.org/jira/browse/HBASE-19121
> Project: HBase
> Issue Type: Bug
> Components: hbck
> Reporter: stack
> Assignee: Umesh Agashe
> Priority: Major
> Attachments: hbase-19121.master.001.patch
>
>
> We don't have an hbck for the new AM. Old hbck may actually do damage going
> against AMv2.
> Fix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
