[
https://issues.apache.org/jira/browse/KUDU-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Bukor updated KUDU-3519:
-------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
Status: Resolved (was: In Review)
> list of masters in "/dump-entites" endpoint
> -------------------------------------------
>
> Key: KUDU-3519
> URL: https://issues.apache.org/jira/browse/KUDU-3519
> Project: Kudu
> Issue Type: Improvement
> Reporter: Gabor Zele
> Assignee: Attila Bukor
> Priority: Major
> Fix For: 1.18.0
>
>
> I'm gathering all kudu metrics for analytics by using the "/metrics" endpoins
> on all master/tablet servers. I'm getting the list of tablet-servers by
> querying "/dump-entites" on a master server.
> "/dump-entites" has top level key for "tablet_servers", but it doesn't
> contain any information about the other masters. For this, I have to maintain
> a list of master http adresses and server UUIDs in my solution, and update it
> there are changes to the masters.
> If the information would be available here, knowing the http address of any
> working master would give me the list of configured masters, which I could
> contact for metrics and save for future use.
> (https://github.com/apache/kudu/blob/master/src/kudu/master/master_path_handlers.cc#L777)
> This Jira is a request to add a key like "master_servers" to the
> "/dump-entites" endpoint with the information about the other masters, like
> we have now in "tablet_servers" for the tablet servers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
