[
https://issues.apache.org/jira/browse/YARN-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201373#comment-15201373
]
Junping Du commented on YARN-4636:
----------------------------------
bq. -1 for something like this without understanding the use-cases.
We should ask for user cases first before making -1 decision.
bq. IMO, the "AM blacklisting" doesn't even need to be user-visible (YARN-4837)
let alone be pluggable.
Pluggable blacklist policy is necessary because application's requirement for
AM robust is different. Some app can tolerant AM failure (small and
short-running job) but some apps don't want any risk (like a large MR job with
long running reducer jobs - AM restart will kill reducer tasks no mater how
long it is already running). IMO, Allowing various blacklist policies is a good
thing for YARN to show the extension capability to address different
application's requirement especially for a cluster form of heterogeneous nodes.
Any comments from guys in watching list?
> Make blacklist tracking policy pluggable for more extensions.
> -------------------------------------------------------------
>
> Key: YARN-4636
> URL: https://issues.apache.org/jira/browse/YARN-4636
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Junping Du
> Assignee: Sunil G
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
