[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[ https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17226293#comment-17226293 ] Michael Stack commented on HBASE-24186: --- Not important but just a note to say I reverted this patch from branch-2.0 too... It broke its build (I'm testing migration so was trying to build branch-2.0 and found this). This matches the observation above by [~ram_krish] > RegionMover ignores replicationId > - > > Key: HBASE-24186 > URL: https://issues.apache.org/jira/browse/HBASE-24186 > Project: HBase > Issue Type: Bug > Components: read replicas >Reporter: Szabolcs Bukros >Assignee: Szabolcs Bukros >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.5 > > > 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[ https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110949#comment-17110949 ] Szabolcs Bukros commented on HBASE-24186: - My change relies on HBASE-21753 and it was not backported to branch-2.1 . Thanks [~ram_krish] for the revert. > RegionMover ignores replicationId > - > > Key: HBASE-24186 > URL: https://issues.apache.org/jira/browse/HBASE-24186 > Project: HBase > Issue Type: Bug > Components: read replicas >Reporter: Szabolcs Bukros >Assignee: Szabolcs Bukros >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.5 > > > 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[ https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110131#comment-17110131 ] ramkrishna.s.vasudevan commented on HBASE-24186: [~vjasani] and [~bszabolcs] I have reverted this from branch-2.1. Pls raise a new JIRA or backport to fix this. FYI. > RegionMover ignores replicationId > - > > Key: HBASE-24186 > URL: https://issues.apache.org/jira/browse/HBASE-24186 > Project: HBase > Issue Type: Bug > Components: read replicas >Reporter: Szabolcs Bukros >Assignee: Szabolcs Bukros >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.1.10, 2.2.5 > > > 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[ https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110129#comment-17110129 ] ramkrishna.s.vasudevan commented on HBASE-24186: This seems to have broken the branch-2.1. Should be reverted from branch-2.1. > RegionMover ignores replicationId > - > > Key: HBASE-24186 > URL: https://issues.apache.org/jira/browse/HBASE-24186 > Project: HBase > Issue Type: Bug > Components: read replicas >Reporter: Szabolcs Bukros >Assignee: Szabolcs Bukros >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.1.10, 2.2.5 > > > 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[
https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085335#comment-17085335
]
Hudson commented on HBASE-24186:
Results for branch branch-2.2
[build #839 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/839/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/839//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/839//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/839//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> RegionMover ignores replicationId
> -
>
> Key: HBASE-24186
> URL: https://issues.apache.org/jira/browse/HBASE-24186
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Szabolcs Bukros
>Assignee: Szabolcs Bukros
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.1.10, 2.2.5
>
>
> 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[
https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085327#comment-17085327
]
Hudson commented on HBASE-24186:
Results for branch branch-2.1
[build #1853 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1853/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1853//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1853//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1853//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1853//console].
> RegionMover ignores replicationId
> -
>
> Key: HBASE-24186
> URL: https://issues.apache.org/jira/browse/HBASE-24186
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Szabolcs Bukros
>Assignee: Szabolcs Bukros
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.1.10, 2.2.5
>
>
> 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[
https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085266#comment-17085266
]
Hudson commented on HBASE-24186:
Results for branch master
[build #1701 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1701/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1701/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1701/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1701/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1701/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> RegionMover ignores replicationId
> -
>
> Key: HBASE-24186
> URL: https://issues.apache.org/jira/browse/HBASE-24186
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Szabolcs Bukros
>Assignee: Szabolcs Bukros
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.1.10, 2.2.5
>
>
> 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[
https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085226#comment-17085226
]
Hudson commented on HBASE-24186:
Results for branch branch-2.3
[build #37 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/37/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/37/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/37/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/37/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/37/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> RegionMover ignores replicationId
> -
>
> Key: HBASE-24186
> URL: https://issues.apache.org/jira/browse/HBASE-24186
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Szabolcs Bukros
>Assignee: Szabolcs Bukros
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.1.10, 2.2.5
>
>
> 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[
https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085213#comment-17085213
]
Hudson commented on HBASE-24186:
Results for branch branch-2
[build #2611 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2611/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2611/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2611/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2611/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2611/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> RegionMover ignores replicationId
> -
>
> Key: HBASE-24186
> URL: https://issues.apache.org/jira/browse/HBASE-24186
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Szabolcs Bukros
>Assignee: Szabolcs Bukros
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.1.10, 2.2.5
>
>
> 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)
[jira] [Commented] (HBASE-24186) RegionMover ignores replicationId
[ https://issues.apache.org/jira/browse/HBASE-24186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
