[
https://issues.apache.org/jira/browse/HDFS-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061240#comment-16061240
]
Xiao Chen commented on HDFS-12027:
----------------------------------
CNF sounds familiar, seems there was HADOOP-13872, but supposedly fixed by the
tomcat -> jetty change HADOOP-13597 (for 3.0+). The security of that depends on
HttpServer2 then, I asked the same before and here's [John's
answer|https://issues.apache.org/jira/browse/HDFS-10860?focusedCommentId=15847657&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15847657].
:)
Not sure about branch-2 though, haven't had a chance to look there.
HADOOP-13872 seems to indicate it only happens 3.0.0-alpha2+.
> 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: [email protected]
For additional commands, e-mail: [email protected]
