[
https://issues.apache.org/jira/browse/YARN-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-4837:
------------------------------------------
Attachment: YARN-4837-20160515.txt
Here's a (longish) patch that addresses some of my proposal above
- This still doesn't solve the other bugs like YARN-4685 that can happen with
the blacklisting logic. There are a bunch of UI bugs too (callers of
BlacklistManager.getBlacklistUpdates() only look at the additions), sigh.
- Renamed the configuration names, but marked all the new configurations
private till we figure the rest of the story with the bugs.
- Removed the user facing APIs and related classes: AMBlackListingRequest,
AMBlackListingRequestPBImpl.java, BlacklistUpdates.java (instead using
ResourceBlacklistRequest directly), AMBlackListingRequestInfo.java
- Removed the references to above from ApplicationSubmissionContext,
yarn_protos.proto, ApplicationSubmissionContextPBImpl.java, RMAppImpl.java,
ApplicationSubmissionContextInfo.java
- The above two essentially revert YARN-4389.
- Changed RMAppAttemptImpl to explicitly encode container exit-statuses in
deciding when to blacklist nodes
- Made a bunch of internal renames to better reflect what they are doing.
> 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
> Priority: Critical
> Attachments: YARN-4837-20160515.txt
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
