[
https://issues.apache.org/jira/browse/HDFS-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802596#comment-17802596
]
Shilun Fan commented on HDFS-16940:
-----------------------------------
Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a
blocker. Retarget 3.5.0.
> Provide HTTP API health endpoints to simplify monitoring
> --------------------------------------------------------
>
> Key: HDFS-16940
> URL: https://issues.apache.org/jira/browse/HDFS-16940
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.4.0, 3.3.9
> Reporter: Steve Vaughan
> Assignee: Steve Vaughan
> Priority: Major
>
> Provide HTTP endpoints that report the current status of the API server when
> running in dynamic environments. Using Kubernetes as an example, this would
> include `/livez` and `/readyz` endpoints. These endpoints would be distinct,
> covering specific cases:
> * `livez` would indicate if the server is up and running. A service can be
> up but not ready to to cover it's assigned duties. As an example, a
> JournalNode could be up, but unformatted or unsynchronized.
> * `readyz` would indicate that the server ready. Following the same
> example, once a JournalNode is synchronized it can act as part of the
> JournalNode quorum, supporting other services.
> This type of service would increase stability by enabling rolling updates
> that maintain a quorum of ready participating service instances.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
