[
https://issues.apache.org/jira/browse/YARN-9545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839456#comment-16839456
]
Zoltan Siegl commented on YARN-9545:
------------------------------------
Thanks for the thoughts.
Pros: no new endpoint is necessary. Cons: That's a about endpoint, so various
junk data for health check purposes is returned, also if we mean to return non
200 status code for /timeline in case of a reader connection failure, that
would be a breaking API change. Returning a 200 OK and an ERROR json seems like
a bad idea to me. As for the following reasons I'd rather stuck with /health.
[~Prabhu Joseph], [~sunilg] any thoughts on this?
> Create healthcheck REST endpoint for ATSv2
> ------------------------------------------
>
> Key: YARN-9545
> URL: https://issues.apache.org/jira/browse/YARN-9545
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: ATSv2
> Affects Versions: 3.1.2
> Reporter: Zoltan Siegl
> Assignee: Zoltan Siegl
> Priority: Major
>
> RM UI2 and CM needs a health check url for ATSv2 service.
> Create a /health rest endpoint
> * must respond with 200 \{health: ok} if all ok
> * must respond with non 200 if any problem occurs
> * could check reader/writer connection
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
