You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2019/02/12 02:29:00 UTC
[jira] [Commented] (HBASE-21849) master serving regions version is
not handled correctly
[ https://issues.apache.org/jira/browse/HBASE-21849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765604#comment-16765604 ]
Sergey Shelukhin commented on HBASE-21849:
------------------------------------------
[~stack] this is actually the VersionInfo fix only :) I removed the implication from the title.
Without this fix, the master reports version 0.0.0 to itself, so special logic that tries to move meta off old servers immediately moves it off, after master assigns it to itself.
The other regions are still hosted on master.
By fixing the version the former behavior no longer happens... however that is incidental. It also removes the bogus version warning from UI.
> master serving regions version is not handled correctly
> -------------------------------------------------------
>
> Key: HBASE-21849
> URL: https://issues.apache.org/jira/browse/HBASE-21849
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
> Attachments: HBASE-21849.patch
>
>
> {noformat}
> ...
> master-node,17000,1549396264134 Tue Feb 05 11:51:04 PST 2019 2 s 0.0.0 0 0
> rs-node,17020,1549396262825 Tue Feb 05 11:51:02 PST 2019 2 s 3.0.4-SNAPSHOT 0 50
> Total:NN 1 nodes with inconsistent version
> {noformat}
> This also causes master to never actually host system table regions, even with hbase.balancer.tablesOnMaster.systemTablesOnly=true
> {noformat}
> 2019-02-05 14:15:14,394 INFO [Thread-290] assignment.AssignmentManager: Async MOVE of 1588230740 to newer Server=...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)