You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2020/03/11 03:42:00 UTC
[jira] [Updated] (HBASE-21345) [hbck2] Allow version check to
proceed even though master is 'initializing'.
[ https://issues.apache.org/jira/browse/HBASE-21345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guanghao Zhang updated HBASE-21345:
-----------------------------------
Fix Version/s: 2.2.4
> [hbck2] Allow version check to proceed even though master is 'initializing'.
> ----------------------------------------------------------------------------
>
> Key: HBASE-21345
> URL: https://issues.apache.org/jira/browse/HBASE-21345
> Project: HBase
> Issue Type: Bug
> Components: hbck2
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 2.1.1, 2.0.3, 2.2.4
>
> Attachments: 0001-HBASE-21345-hbck2-Allow-version-check-to-proceed-eve.patch, 0001-HBASE-21345-hbck2-Allow-version-check-to-proceed-eve.patch
>
>
> We recently added to hbck2 a check of the cluster version it is to go against. This means a getClusterMetrics call with the option HBASE_VERSION set.
> In testing, trying to fix a failed namespace assign on startup, hbck2 was shut out with a "PleaseHoldException".
> Let the getClusterMetrics call happen even during startup... so tooling can probe Master state externally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)