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 2017/10/30 18:29:00 UTC

[jira] [Commented] (HBASE-19121) HBCK for AMv2

    [ https://issues.apache.org/jira/browse/HBASE-19121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225496#comment-16225496 ] 

Sean Busbey commented on HBASE-19121:
-------------------------------------

I was idly thinking about how to stop HBase v1 HBCK. Thanks to HBASE-11405, we know that all HBase 1.y.z hbck instances should refuse to run if there's a lock file at '/hbase/hbase-hbck.lock' (given defaults). How about HBase v2 places that file permanently in place and replace the contents (usually just an IP address) with a note about how you must not run HBase v1 HBCK against the cluster?

We could pick another location for locking on HBase version 2 and start building in a version check of some kind?

> HBCK for AMv2
> -------------
>
>                 Key: HBASE-19121
>                 URL: https://issues.apache.org/jira/browse/HBASE-19121
>             Project: HBase
>          Issue Type: Sub-task
>          Components: hbck
>            Reporter: stack
>             Fix For: 2.0.0-beta-1
>
>
> 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
(v6.4.14#64029)