[
https://issues.apache.org/jira/browse/HDFS-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061202#comment-16061202
]
patrick white commented on HDFS-12027:
--------------------------------------
Thanks much for the feedback John.
It would be good to have something a client can use, think 'names' is a
privileged command. This would be to allow non-admins of the KMS instance to be
able to run monitors or status checks on their own, cluster service engineers,
users, so forth.
Right and understood, API version is embedded in the call. Thinking of a
command with return that was specific to the installed KMS build's instance,
something like Oozie's 'version' API.
Just for info, 'keys/names' is currently giving me
UnsupportedOperationException, this is running as the priv user, with other
cmds such as '_metdata' succeeding. I need to follow up though, not sure why
i'm getting this.
> Add KMS API to get service version and health check
> ---------------------------------------------------
>
> Key: HDFS-12027
> URL: https://issues.apache.org/jira/browse/HDFS-12027
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: kms
> Reporter: patrick white
> Priority: Minor
>
> Enhancement request, add an API to the Key Management Server which can be
> used for health monitoring as well as programatic version checks, such as to
> return the service version identifier, suggest this;
> GET http://HOST:PORT/kms/v1/key/kms_version
> This API would be useful for production monitoring tools to quickly do KMS
> instance reporting (dashboards) and basic health checks, as part of overall
> monitoring of a Hadoop stack installation.
> Such an API would also be useful for debugging initial bring-up of a service
> instance, such as validation of the KMS webserver and its interaction with ZK
> before the key manager(s) are necessarily working. Currently i believe a
> valid key needs to be setup and available before calls can return success.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
