[jira] [Commented] (MAPREDUCE-5654) blacklist is not propagated from AM to RM

["Gourav Khaneja (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069057#comment-14069057 ] 

Gourav Khaneja commented on MAPREDUCE-5654:
-------------------------------------------

Hi. Just FYI - I've used Blacklist with Yarn RM 2.2 and 2.3 in https://issues.apache.org/jira/browse/TWILL-87 and it seems to work. (i.e. blacklist is propagated from AM to RM).

> blacklist is not propagated from AM to RM
> -----------------------------------------
>
>                 Key: MAPREDUCE-5654
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5654
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster
>            Reporter: Robert Grandl
>
> I was trying to blacklist some nodes. I added a set of hosts as strings into blacklistAdditions list and propagated into RMContainerRequestor#makeRemoteRequest to the RM. 
> However the blacklist is received empty at RM. I logged the path for blacklist in AM and I found that in ApplicationMasterProtocolPBClientImpl#allocate, this list is lost. 
> I print request.getResourceBlacklistRequest().getBlacklistAdditions().toString() at the beginning of ApplicationMasterProtocolPBClientImpl#allocate and the blacklisted additions are there. 
> After AllocateRequestProto requestProto is created based on this request, and I print again requestProto.getBlacklistRequest().getBlacklistAdditionsList().toString(), the blacklist additions is empty now.
> I looked even further and log what happened. At some point in yarn-api, I was lost with my logging as that code was regenerated every time I recompiled yarn-api. 
> Thanks,
> robert



--
This message was sent by Atlassian JIRA
(v6.2#6252)