[jira] [Updated] (HBASE-21938) Add a new ClusterMetrics.Option SERVERS_NAME to only return the live region servers's name without metrics
[
https://issues.apache.org/jira/browse/HBASE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-21938:
---
Resolution: Fixed
Fix Version/s: 2.3.0
2.2.0
3.0.0
Status: Resolved (was: Patch Available)
Pushed to branch-2.2+. Thanks [~Yi Mei] for contributing.
> 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 20 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)
[jira] [Updated] (HBASE-21938) Add a new ClusterMetrics.Option SERVERS_NAME to only return the live region servers's name without metrics
[
https://issues.apache.org/jira/browse/HBASE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Mei updated HBASE-21938:
---
Status: Patch Available (was: Open)
> 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
> Attachments: HBASE-21938.master.001.patch,
> HBASE-21938.master.002.patch
>
>
> One of our production cluster ( which has 20 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)
[jira] [Updated] (HBASE-21938) Add a new ClusterMetrics.Option SERVERS_NAME to only return the live region servers's name without metrics
[
https://issues.apache.org/jira/browse/HBASE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Mei updated HBASE-21938:
---
Attachment: HBASE-21938.master.002.patch
> 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
> Attachments: HBASE-21938.master.001.patch,
> HBASE-21938.master.002.patch
>
>
> One of our production cluster ( which has 20 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)
[jira] [Updated] (HBASE-21938) Add a new ClusterMetrics.Option SERVERS_NAME to only return the live region servers's name without metrics
[
https://issues.apache.org/jira/browse/HBASE-21938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Mei updated HBASE-21938:
---
Attachment: HBASE-21938.master.001.patch
> 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
> Attachments: HBASE-21938.master.001.patch
>
>
> One of our production cluster ( which has 20 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)
