Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 23 Jun 2017 16:14:02 +0000 (UTC)
From: "John Zhuge (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13082152.1498231099000.93260.1498234442482@Atlassian.JIRA>
In-Reply-To: <JIRA.13082152.1498231099000@Atlassian.JIRA>
References: <JIRA.13082152.1498231099000@Atlassian.JIRA> <JIRA.13082152.1498231099142@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12027) Add KMS API to get service version
 and health check
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 23 Jun 2017 16:14:09 -0000


    [ https://issues.apache.org/jira/browse/HDFS-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061160#comment-16061160 ] 

John Zhuge commented on HDFS-12027:
-----------------------------------

For health check, you may use "GET http://HOST:PORT/kms/v1/keys/names". The response message may get too large if the number of the keys are significant.

KMS version is "v1" and already embedded in the URL.

> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org