[
https://issues.apache.org/jira/browse/YARN-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446576#comment-16446576
]
Gour Saha commented on YARN-8122:
---------------------------------
bq. I think we should consider whether or not ComponentHealthThresholdMonitor
should be a service that is added into the AM CompositeService. For example, we
are scheduling the ContainerStatusRetriever in the ServiceScheduler's thread
pool. We could be doing the same thing with the health threshold monitor tasks.
[~billie.rinaldi], very good point. I am uploading patch 005 with this
suggestion. I made one additional change where I am adding 3 secs to the
initial delay to account for time taken to request for containers before the
monitor kicks in. For practical purposes, the additional 3 secs will be
minuscule compared to real usecases like LLAP which uses 400 secs of initial
delay. It is primarily to help the tests where I am using 0 secs delay since I
want them to run as fast as possible.
> Component health threshold monitor
> ----------------------------------
>
> Key: YARN-8122
> URL: https://issues.apache.org/jira/browse/YARN-8122
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Gour Saha
> Assignee: Gour Saha
> Priority: Major
> Attachments: YARN-8122.001.patch, YARN-8122.002.patch,
> YARN-8122.003.patch, YARN-8122.004.patch, YARN-8122.draft.patch
>
>
> Slider supported component health threshold monitoring with SLIDER-1246. It
> would be good to have this feature for YARN Service too.
--
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
