[
https://issues.apache.org/jira/browse/HBASE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775196#comment-16775196
]
Hudson commented on HBASE-21938:
--------------------------------
Results for branch branch-2
[build #1702 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1702/]:
(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/1702//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/1702//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/1702//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Add a new ClusterMetrics.Option SERVERS_NAME to only return the live region
> servers's name without metrics
> ----------------------------------------------------------------------------------------------------------
>
> Key: HBASE-21938
> URL: https://issues.apache.org/jira/browse/HBASE-21938
> Project: HBase
> Issue Type: Bug
> Reporter: Guanghao Zhang
> Assignee: Yi Mei
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
> Attachments: HBASE-21938.master.001.patch,
> HBASE-21938.master.002.patch
>
>
> One of our production cluster ( which has 200000 regions) meet one protobuf
> exception when getClusterStatus.
>
> {code:java}
> com.google.protobuf.InvalidProtocolBufferException: Protocol message was too
> large. May be malicious. Use CodedInputStream.setSizeLimit() to increase
> the size limit.
> {code}
> And there are some client methods which call getClusterStatus but only need
> server names. Plan to add a new option which only to return server name. So
> we can reduce the influence scope even we meet this problem.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
