You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Szabolcs Bukros (Jira)" <ji...@apache.org> on 2020/04/15 16:32:00 UTC

[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId

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

Szabolcs Bukros commented on HBASE-24186:
-----------------------------------------

Correction:

This does not prevent the moving of the region, the result of getServerNameForRegion() is only used in the validation of the move, so it only forces the move to try to repeat itself because it does not realize the move already happened. So it just slows down the process but not break it.

> RegionMover ignores replicationId
> ---------------------------------
>
>                 Key: HBASE-24186
>                 URL: https://issues.apache.org/jira/browse/HBASE-24186
>             Project: HBase
>          Issue Type: Bug
>          Components: read replicas
>    Affects Versions: master
>            Reporter: Szabolcs Bukros
>            Assignee: Szabolcs Bukros
>            Priority: Minor
>
> When RegionMover looks up which rs hosts a region, it does this based on startRowKey. When read replication is enabled this might not return the expected region's data and this can prevent the moving of these regions.



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