[jira] [Updated] (HBASE-18401) Region Replica shows up in meta table after split in branch-1
[ https://issues.apache.org/jira/browse/HBASE-18401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18401: Summary: Region Replica shows up in meta table after split in branch-1 (was: Region Replica broken in branch-1) > Region Replica shows up in meta table after split in branch-1 > - > > Key: HBASE-18401 > URL: https://issues.apache.org/jira/browse/HBASE-18401 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 1.3.1, 1.2.6 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18401-branch-1.2-v001.patch, > HBASE-18401-branch-1.2-v002.patch > > > Read replica is broken in branch-1, after the region split, we saw replica > region as content in hbase:meta, while the previous behavior is that replica > region should not show up in info:regioninfo. > {code} > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:regioninfo, > timestamp=1500340472406, value={ENCODED => d8faa669dde775c323f6e55fd5aa36e0, > NAME => 't1,r2111,1500340472229_0001.d8faa669dde7 > e73ca. 75c323f6e55fd5aa36e0.', > STARTKEY => 'r2111', ENDKEY => 'r2', REPLICA_ID => 1} > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen, timestamp=1500340472379, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen_0001, timestamp=1500340472406, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server, > timestamp=1500340472379, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server_0001, > timestamp=1500340472406, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode, timestamp=1500340472379, value=1500340443589 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode_0001, timestamp=1500340472406, > value=\x00\x00\x01]SBY\xC5 > {code} > This was introduced by > https://github.com/apache/hbase/blame/branch-1-HBASE-18147/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L1464 > It does not consider that case that regionInfo could come from a replica > region. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18401) Region Replica shows up in meta table after split in branch-1
[ https://issues.apache.org/jira/browse/HBASE-18401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18401: Component/s: regionserver > Region Replica shows up in meta table after split in branch-1 > - > > Key: HBASE-18401 > URL: https://issues.apache.org/jira/browse/HBASE-18401 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 1.3.1, 1.2.6 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18401-branch-1.2-v001.patch, > HBASE-18401-branch-1.2-v002.patch > > > Read replica is broken in branch-1, after the region split, we saw replica > region as content in hbase:meta, while the previous behavior is that replica > region should not show up in info:regioninfo. > {code} > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:regioninfo, > timestamp=1500340472406, value={ENCODED => d8faa669dde775c323f6e55fd5aa36e0, > NAME => 't1,r2111,1500340472229_0001.d8faa669dde7 > e73ca. 75c323f6e55fd5aa36e0.', > STARTKEY => 'r2111', ENDKEY => 'r2', REPLICA_ID => 1} > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen, timestamp=1500340472379, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen_0001, timestamp=1500340472406, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server, > timestamp=1500340472379, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server_0001, > timestamp=1500340472406, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode, timestamp=1500340472379, value=1500340443589 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode_0001, timestamp=1500340472406, > value=\x00\x00\x01]SBY\xC5 > {code} > This was introduced by > https://github.com/apache/hbase/blame/branch-1-HBASE-18147/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L1464 > It does not consider that case that regionInfo could come from a replica > region. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18401) Region Replica shows up in meta table after split in branch-1
[ https://issues.apache.org/jira/browse/HBASE-18401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18401: Fix Version/s: 1.2.7 1.3.2 1.4.0 > Region Replica shows up in meta table after split in branch-1 > - > > Key: HBASE-18401 > URL: https://issues.apache.org/jira/browse/HBASE-18401 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 1.3.1, 1.2.6 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18401-branch-1.2-v001.patch, > HBASE-18401-branch-1.2-v002.patch > > > Read replica is broken in branch-1, after the region split, we saw replica > region as content in hbase:meta, while the previous behavior is that replica > region should not show up in info:regioninfo. > {code} > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:regioninfo, > timestamp=1500340472406, value={ENCODED => d8faa669dde775c323f6e55fd5aa36e0, > NAME => 't1,r2111,1500340472229_0001.d8faa669dde7 > e73ca. 75c323f6e55fd5aa36e0.', > STARTKEY => 'r2111', ENDKEY => 'r2', REPLICA_ID => 1} > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen, timestamp=1500340472379, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen_0001, timestamp=1500340472406, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server, > timestamp=1500340472379, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server_0001, > timestamp=1500340472406, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode, timestamp=1500340472379, value=1500340443589 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode_0001, timestamp=1500340472406, > value=\x00\x00\x01]SBY\xC5 > {code} > This was introduced by > https://github.com/apache/hbase/blame/branch-1-HBASE-18147/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L1464 > It does not consider that case that regionInfo could come from a replica > region. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18401) Region Replica shows up in meta table after split in branch-1
[ https://issues.apache.org/jira/browse/HBASE-18401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-18401: - Affects Version/s: 2.0.0-alpha-1 > Region Replica shows up in meta table after split in branch-1 > - > > Key: HBASE-18401 > URL: https://issues.apache.org/jira/browse/HBASE-18401 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 1.3.1, 1.2.6, 2.0.0-alpha-1 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18401-branch-1.2-v001.patch, > HBASE-18401-branch-1.2-v002.patch > > > Read replica is broken in branch-1, after the region split, we saw replica > region as content in hbase:meta, while the previous behavior is that replica > region should not show up in info:regioninfo. > {code} > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:regioninfo, > timestamp=1500340472406, value={ENCODED => d8faa669dde775c323f6e55fd5aa36e0, > NAME => 't1,r2111,1500340472229_0001.d8faa669dde7 > e73ca. 75c323f6e55fd5aa36e0.', > STARTKEY => 'r2111', ENDKEY => 'r2', REPLICA_ID => 1} > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen, timestamp=1500340472379, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen_0001, timestamp=1500340472406, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server, > timestamp=1500340472379, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server_0001, > timestamp=1500340472406, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode, timestamp=1500340472379, value=1500340443589 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode_0001, timestamp=1500340472406, > value=\x00\x00\x01]SBY\xC5 > {code} > This was introduced by > https://github.com/apache/hbase/blame/branch-1-HBASE-18147/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L1464 > It does not consider that case that regionInfo could come from a replica > region. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18401) Region Replica shows up in meta table after split in branch-1
[ https://issues.apache.org/jira/browse/HBASE-18401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-18401: - Attachment: HBASE-18401-branch-1.2-v003.patch Upload a new patch for white space warning. Checked the failed unittest, it run successfully for me locally. I will upload a patch for 2.0.0 and branch-1 shortly. > Region Replica shows up in meta table after split in branch-1 > - > > Key: HBASE-18401 > URL: https://issues.apache.org/jira/browse/HBASE-18401 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 1.3.1, 1.2.6, 2.0.0-alpha-1 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Critical > Fix For: 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18401-branch-1.2-v001.patch, > HBASE-18401-branch-1.2-v002.patch, HBASE-18401-branch-1.2-v003.patch > > > Read replica is broken in branch-1, after the region split, we saw replica > region as content in hbase:meta, while the previous behavior is that replica > region should not show up in info:regioninfo. > {code} > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:regioninfo, > timestamp=1500340472406, value={ENCODED => d8faa669dde775c323f6e55fd5aa36e0, > NAME => 't1,r2111,1500340472229_0001.d8faa669dde7 > e73ca. 75c323f6e55fd5aa36e0.', > STARTKEY => 'r2111', ENDKEY => 'r2', REPLICA_ID => 1} > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen, timestamp=1500340472379, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:seqnumDuringOpen_0001, timestamp=1500340472406, > value=\x00\x00\x00\x00\x00\x00\x00\x02 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server, > timestamp=1500340472379, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 column=info:server_0001, > timestamp=1500340472406, value=dhcp-172-16-1-203.pa.cloudera.com:59105 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode, timestamp=1500340472379, value=1500340443589 > > e73ca. > > > t1,r2111,1500340472229.814f68c2d6e92dd8acb82a55706 > column=info:serverstartcode_0001, timestamp=1500340472406, > value=\x00\x00\x01]SBY\xC5 > {code} > This was introduced by > https://github.com/apache/hbase/blame/branch-1-HBASE-18147/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L1464 > It does not consider that case that regionInfo could come from a replica > region. -- This message was sent by Atlassian JIRA (v6.4.14#64029)