[
https://issues.apache.org/jira/browse/YARN-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202500#comment-15202500
]
Junping Du commented on YARN-4837:
----------------------------------
Hi [~vinodkv], did you see my comments at YARN-4576
(https://issues.apache.org/jira/browse/YARN-4576?focusedCommentId=15201559&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15201559)?
+1 on "explicitly treat known exit-codes" which is exactly the same as previous
proposal in YARN-4576. However, the different is:
"DISKS_FAILED" shouldn't be skipped for the reason I mentioned in YARN-4576.
Also, we cannot simply judge system innocent when hitting memory issues.
Also, hide all AM scheduling info/preference from application doesn't make
sense in long time: AM can ask for resources for its running containers in the
beginning, but application cannot ask how to place its AM even today which is
sad to me.
YARN-4685 is something fixable and much better than the age without blacklist
(we do see AM keep launching on bad nodes repeatedly and get stuck in many
cases). We just need to go ahead to fix YARN-4685.
> User facing aspects of 'AM blacklisting' feature need fixing
> ------------------------------------------------------------
>
> Key: YARN-4837
> URL: https://issues.apache.org/jira/browse/YARN-4837
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> Was reviewing the user-facing aspects that we are releasing as part of 2.8.0.
> Looking at the 'AM blacklisting feature', I see several things to be fixed
> before we release it in 2.8.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
