You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/01/22 03:18:00 UTC

[jira] [Commented] (HBASE-20279) [tooling] check for incompatible environment for HBase 2.0 upgrade

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

Michael Stack commented on HBASE-20279:
---------------------------------------

Moved unaddressed issue from subtask to standalone, unscheduled issue.

> [tooling] check for incompatible environment for HBase 2.0 upgrade
> ------------------------------------------------------------------
>
>                 Key: HBASE-20279
>                 URL: https://issues.apache.org/jira/browse/HBASE-20279
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation, tooling
>    Affects Versions: 2.0.0
>            Reporter: Sean Busbey
>            Priority: Critical
>
> from [~stack] on HBASE-19158:
> {quote}
> bq. Server failure. HBase can still read HFiles written in the older version 2 format.
> Need a script that user can run pre-upgrade.
> {quote}
> Additional commentary from [~busbey]
> In addition to the config check stack mentions, such a tool could check
> * other problematic configs, like those for master-hosts-regions
> * inconsistent configs due to changed defaults (I think we should have some smell-tests around the change in default for hbase.security.authorization)
> * (optionally) check for unreadable WALs
> * (optionally) check for unreadable hfiles



--
This message was sent by Atlassian Jira
(v8.3.4#803005)