[
https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466664#comment-15466664
]
Rohith Sharma K S commented on YARN-4205:
-----------------------------------------
bq. can you clarify the definition of lifetime in the API
Lifetime of an application is nothing but overall time at which application has
run. It includes sum of *RMStateStore(connection time + retry time + ... )+
Scheduler allocation delay + container run time*. In other words it is
execution_lifetime as Vinod mentioned.
bq. But some apps will need to distinguish {{queue_timeout}} from
{{execution_lifetime}}. Can we distinguish those?
In general case, RMStateStore time will be very less may be less than seconds.
Most of the time spent on either allocation-delay or container-run-time. I
think this need not to be handle separately.
bq. Obviously one of the followup challenges is to clearly define where queuing
starts/ends & execution starts/ends.
IAC, to go ahead with queue_timeout, then time can be from Attempt
SUBMITTED/SCHEDULED to Attempt_removed_from_scheduler. Thoughts?
> Add a service for monitoring application life time out
> ------------------------------------------------------
>
> Key: YARN-4205
> URL: https://issues.apache.org/jira/browse/YARN-4205
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler
> Reporter: nijel
> Assignee: Rohith Sharma K S
> Attachments: 0001-YARN-4205.patch, 0002-YARN-4205.patch,
> YARN-4205_01.patch, YARN-4205_02.patch, YARN-4205_03.patch
>
>
> This JIRA intend to provide a lifetime monitor service.
> The service will monitor the applications where the life time is configured.
> If the application is running beyond the lifetime, it will be killed.
> The lifetime will be considered from the submit time.
> The thread monitoring interval is configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
