[
https://issues.apache.org/jira/browse/SAMZA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130162#comment-14130162
]
Chris Riccomini commented on SAMZA-408:
---------------------------------------
bq. Another question: for the case where a container is killed by YARN due to a
node failure (exit code -100), should jobHealthy still be 0 until the container
is re-allocated?
Personally, I think so. As a developer, I care if my containers aren't running,
even if it's just because YARN has killed them due to a node failure. It seems
most intuitive to report the job as unhealthy any time the containers aren't
running.
> Expose a metric for tracking AM availability
> --------------------------------------------
>
> Key: SAMZA-408
> URL: https://issues.apache.org/jira/browse/SAMZA-408
> Project: Samza
> Issue Type: Improvement
> Components: container
> Affects Versions: 0.8.0
> Reporter: Chinmay Soman
> Assignee: David Chen
> Fix For: 0.8.0
>
> Attachments: SAMZA-408.0.patch, SAMZA-408.1.patch
>
>
> We have a metric for tracking number of containers running. But we don't have
> anything to indicate if the job is healthy. This translates to the AM along
> with all the containers must be running.
> Expose a "healthy" metric: It should be 1 if the AM and all containers are
> running. 0 otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
