[jira] [Commented] (HBASE-23328) info:regioninfo goes wrong when region replicas enabled
[
https://issues.apache.org/jira/browse/HBASE-23328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980659#comment-16980659
]
Hudson commented on HBASE-23328:
Results for branch branch-2.1
[build #1718 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1718/]:
(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.1/1718//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1718//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/1718//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> info:regioninfo goes wrong when region replicas enabled
> ---
>
> Key: HBASE-23328
> URL: https://issues.apache.org/jira/browse/HBASE-23328
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
>
> Noticed that the info:regioninfo content in hbase:meta can become that of a
> serialized replica. I think it mostly harmless but accounting especially
> debugging is frustrated because hbase:meta row name does not match the
> info:regioninfo.
> Here is an example:
> {code}
> t1,c6e977ef,1572669121340.0b455b2d57f91c153d5088533205c268.
> column=info:regioninfo, timestamp=1574367093772, value={ENCODED =>
> 5199f7826c340ba944517e97c6ebaf04, NAME =>
> 't1,c6e977ef,1572669121340_0001.5199f7826c340ba944517e97c6ebaf04.', STARTKEY
> => 'c6e977ef', ENDKEY => 'c72b0126', REPLICA_ID => 1}
> {code}
> Notice how hbase:meta row name is like that of the info:regioninfo content
> only we are listing REPLICA_ID content and the encoded name is different (as
> it factors replicaid).
> The original Region Replica design describes how the info:regioninfo is
> supposed to have the default HRI serialized only. See comment on HRI changes
> in
> https://issues.apache.org/jira/secure/attachment/12627276/hbase-10347_redo_v8.patch
> -Going back over history, this may have been a bug since Region Replicas came
> in.- <= No. Looking at an old cluster w/ region replicas, it doesn't have
> this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23328) info:regioninfo goes wrong when region replicas enabled
[
https://issues.apache.org/jira/browse/HBASE-23328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980632#comment-16980632
]
Hudson commented on HBASE-23328:
Results for branch branch-2
[build #2362 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2362/]:
(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/2362//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/2362//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/2362//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> info:regioninfo goes wrong when region replicas enabled
> ---
>
> Key: HBASE-23328
> URL: https://issues.apache.org/jira/browse/HBASE-23328
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
>
> Noticed that the info:regioninfo content in hbase:meta can become that of a
> serialized replica. I think it mostly harmless but accounting especially
> debugging is frustrated because hbase:meta row name does not match the
> info:regioninfo.
> Here is an example:
> {code}
> t1,c6e977ef,1572669121340.0b455b2d57f91c153d5088533205c268.
> column=info:regioninfo, timestamp=1574367093772, value={ENCODED =>
> 5199f7826c340ba944517e97c6ebaf04, NAME =>
> 't1,c6e977ef,1572669121340_0001.5199f7826c340ba944517e97c6ebaf04.', STARTKEY
> => 'c6e977ef', ENDKEY => 'c72b0126', REPLICA_ID => 1}
> {code}
> Notice how hbase:meta row name is like that of the info:regioninfo content
> only we are listing REPLICA_ID content and the encoded name is different (as
> it factors replicaid).
> The original Region Replica design describes how the info:regioninfo is
> supposed to have the default HRI serialized only. See comment on HRI changes
> in
> https://issues.apache.org/jira/secure/attachment/12627276/hbase-10347_redo_v8.patch
> -Going back over history, this may have been a bug since Region Replicas came
> in.- <= No. Looking at an old cluster w/ region replicas, it doesn't have
> this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23328) info:regioninfo goes wrong when region replicas enabled
[
https://issues.apache.org/jira/browse/HBASE-23328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980569#comment-16980569
]
Hudson commented on HBASE-23328:
Results for branch branch-2.2
[build #701 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/701/]:
(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/701//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/701//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/701//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> info:regioninfo goes wrong when region replicas enabled
> ---
>
> Key: HBASE-23328
> URL: https://issues.apache.org/jira/browse/HBASE-23328
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
>
> Noticed that the info:regioninfo content in hbase:meta can become that of a
> serialized replica. I think it mostly harmless but accounting especially
> debugging is frustrated because hbase:meta row name does not match the
> info:regioninfo.
> Here is an example:
> {code}
> t1,c6e977ef,1572669121340.0b455b2d57f91c153d5088533205c268.
> column=info:regioninfo, timestamp=1574367093772, value={ENCODED =>
> 5199f7826c340ba944517e97c6ebaf04, NAME =>
> 't1,c6e977ef,1572669121340_0001.5199f7826c340ba944517e97c6ebaf04.', STARTKEY
> => 'c6e977ef', ENDKEY => 'c72b0126', REPLICA_ID => 1}
> {code}
> Notice how hbase:meta row name is like that of the info:regioninfo content
> only we are listing REPLICA_ID content and the encoded name is different (as
> it factors replicaid).
> The original Region Replica design describes how the info:regioninfo is
> supposed to have the default HRI serialized only. See comment on HRI changes
> in
> https://issues.apache.org/jira/secure/attachment/12627276/hbase-10347_redo_v8.patch
> -Going back over history, this may have been a bug since Region Replicas came
> in.- <= No. Looking at an old cluster w/ region replicas, it doesn't have
> this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23328) info:regioninfo goes wrong when region replicas enabled
[
https://issues.apache.org/jira/browse/HBASE-23328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980171#comment-16980171
]
Hudson commented on HBASE-23328:
Results for branch master
[build #1544 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1544/]: (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/1544//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/master/1544//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/master/1544//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> info:regioninfo goes wrong when region replicas enabled
> ---
>
> Key: HBASE-23328
> URL: https://issues.apache.org/jira/browse/HBASE-23328
> Project: HBase
> Issue Type: Bug
> Components: read replicas
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
>
> Noticed that the info:regioninfo content in hbase:meta can become that of a
> serialized replica. I think it mostly harmless but accounting especially
> debugging is frustrated because hbase:meta row name does not match the
> info:regioninfo.
> Here is an example:
> {code}
> t1,c6e977ef,1572669121340.0b455b2d57f91c153d5088533205c268.
> column=info:regioninfo, timestamp=1574367093772, value={ENCODED =>
> 5199f7826c340ba944517e97c6ebaf04, NAME =>
> 't1,c6e977ef,1572669121340_0001.5199f7826c340ba944517e97c6ebaf04.', STARTKEY
> => 'c6e977ef', ENDKEY => 'c72b0126', REPLICA_ID => 1}
> {code}
> Notice how hbase:meta row name is like that of the info:regioninfo content
> only we are listing REPLICA_ID content and the encoded name is different (as
> it factors replicaid).
> The original Region Replica design describes how the info:regioninfo is
> supposed to have the default HRI serialized only. See comment on HRI changes
> in
> https://issues.apache.org/jira/secure/attachment/12627276/hbase-10347_redo_v8.patch
> -Going back over history, this may have been a bug since Region Replicas came
> in.- <= No. Looking at an old cluster w/ region replicas, it doesn't have
> this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
