[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553671#comment-17553671
]
Sean Busbey commented on HBASE-21771:
-
Sakthi hasn't been around in quite some time, but I could take a stab at
getting this turned into a PR sure.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0-alpha-1, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Priority: Major
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553647#comment-17553647
]
Andrew Kyle Purtell commented on HBASE-21771:
-
[~busbey] Can this be made into a PR? We can then merge and resolve this.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0-alpha-1, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Priority: Major
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955349#comment-16955349
]
HBase QA commented on HBASE-21771:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m
20s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}
0m 0s{color} | {color:orange} The patch doesn't appear to include any new or
modified tests. Please justify why no new tests are needed for this patch. Also
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
38s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}298m 59s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
35s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}313m 45s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas |
| | hadoop.hbase.client.TestAsyncTableAdminApi |
| | hadoop.hbase.client.TestSnapshotTemporaryDirectory |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.4 Server=19.03.4 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/968/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-21771 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12956273/hbase-21771.master.002.patch
|
| Optional Tests | dupname asflicense javac javadoc unit |
| uname | Linux 578e10d24e0e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6
11:12:41 UTC 2019 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/hbase-personality.sh |
| git revision | master / 4d414020bb |
| Default Java | 1.8.0_181 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/968/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/968/testReport/ |
| Max. process+thread count | 5169 (vs. ulimit of 1) |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/968/console |
| versions | git=2.11.0 maven=2018-06-17T18:33:14Z) |
| Powered by | Apache Yetus 0.11.0 https://yetus.apache.org |
This message was automatically generated.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1',
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955265#comment-16955265
]
Wellington Chevreuil commented on HBASE-21771:
--
I'm not an UI expert, but the formatting looks good, and this would be really
helpful for setting replication, so +1, let's have it committed.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764074#comment-16764074
]
Sakthi commented on HBASE-21771:
Without table-layout: fixed, the cells are tending to stretch nevertheless.
Even if max-width is tried on the cell. I did some reading, in most places -
using table-layout: fixed, when one of the cells will tend to overflow, is
suggested/advised. I would be be happy to learn any other technique. :)
Suggestions from any UI enthusiast would be highly appreciated here! :)
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762564#comment-16762564
]
Peter Somogyi commented on HBASE-21771:
---
The {{table-layout: fixed}} causes all columns to have equal width. Check
Attribute Name column on the screenshot. Could you make something with that?
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755401#comment-16755401
]
Sakthi commented on HBASE-21771:
[~apurtell] , [~busbey], how does the patch look to you guys?
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752693#comment-16752693
]
Sakthi commented on HBASE-21771:
Thanks [~nihaljain.cs] and [~wchevreuil] for testing out.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752656#comment-16752656
]
Wellington Chevreuil commented on HBASE-21771:
--
lgtm. Tested on branch-2, both single and multiple servers ZK quorum.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752589#comment-16752589
]
Nihal Jain commented on HBASE-21771:
BTW, what does the following change do?
{code:java}
-
+
{code}
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752588#comment-16752588
]
Nihal Jain commented on HBASE-21771:
Checked on standalone mode, case where we have only one node. Cluster key is as
expected. Code changes look fine.
+1 (non-binding)
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752592#comment-16752592
]
Sakthi commented on HBASE-21771:
It's for wrapping long lines. Or else, it'll be like issue HBASE-21780
where the columns are wider than expected because of lengthy cells.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752506#comment-16752506
]
Sakthi commented on HBASE-21771:
The test failure looks unrelated.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751948#comment-16751948
]
Hadoop QA commented on HBASE-21771:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
12s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}
0m 0s{color} | {color:orange} The patch doesn't appear to include any new or
modified tests. Please justify why no new tests are needed for this patch. Also
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
30s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}132m 49s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}143m 58s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestAsyncTableGetMultiThreaded |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-21771 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12956273/hbase-21771.master.002.patch
|
| Optional Tests | dupname asflicense javac javadoc unit |
| uname | Linux d957ef8b9caa 4.4.0-139-generic #165~14.04.1-Ubuntu SMP Wed Oct
31 10:55:11 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 91dffb043a |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/15731/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/15731/testReport/ |
| Max. process+thread count | 5130 (vs. ulimit of 1) |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/15731/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" =>
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751882#comment-16751882
]
Sakthi commented on HBASE-21771:
I think a rebase was required. Have uploaded a new patch.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch,
> hbase-21771.master.002.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751872#comment-16751872
]
Sakthi commented on HBASE-21771:
Weird. The patch applies cleanly on my master branch though.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 3.0.0, 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751857#comment-16751857
]
Hadoop QA commented on HBASE-21771:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} HBASE-21771 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-21771 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/15729/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 3.0.0, 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 3.0.0, 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751854#comment-16751854
]
Sakthi commented on HBASE-21771:
Have attached a screenshot of how the UI looks now. Also the copy/paste of the
cluster-key worked while trying to add peer. [~busbey], let me know your
thoughts :)
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: ClusterKey_afterPatch.png, hbase-21771.master.001.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21771) Cluster key in Master UI is incorrect
[
https://issues.apache.org/jira/browse/HBASE-21771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751852#comment-16751852
]
Sakthi commented on HBASE-21771:
The issue prevails in master as well. Here's a patch for the master
> Cluster key in Master UI is incorrect
> -
>
> Key: HBASE-21771
> URL: https://issues.apache.org/jira/browse/HBASE-21771
> Project: HBase
> Issue Type: Bug
> Components: Replication, UI, Usability
>Affects Versions: 2.1.0, 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.3
>
> Attachments: hbase-21771.master.001.patch
>
>
> The master UI is supposed to give us a cluster key we can copy/paste to add a
> replication peer in the hbase shell. the shell explains that it should look
> like this:
> {quote}
> {code}
> For a HBase cluster peer, a cluster key must be provided and is composed like
> this:
> hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent
> This gives a full path for HBase to connect to another HBase cluster.
> ...
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "ENABLED"
> hbase> add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase", STATE =>
> "DISABLED"
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> TABLE_CFS => { "table1" => [], "table2" => ["cf1"], "table3" => ["cf1",
> "cf2"] }
> hbase> add_peer '2', CLUSTER_KEY => "zk1,zk2,zk3:2182:/hbase-prod",
> NAMESPACES => ["ns1", "ns2", "ns3"]
> {code}
> {quote}
> However, on my example cluster with ZK quorum with 3 servers, the master ui
> gives this:
> {quote}
> {code}
> Cluster Key busbey-training-1.gce.cloudera.com:2181
> busbey-training-2.gce.cloudera.com:2181
> busbey-training-3.gce.cloudera.com:2181:/hbaseKey to add this cluster
> as a peer for replication. Use 'help "add_peer"' in the shell for details.
> {code}
> {quote}
> Note that the quorum members are newline separated instead of comma and that
> the port appears on each member instead of after the set of host names.
> Workaround is to manually construct the cluster key from the details in the
> field. :(
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
