You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2013/11/26 01:00:36 UTC
[jira] [Updated] (YARN-1443) blacklist is not propagated from AM to
RM
[ https://issues.apache.org/jira/browse/YARN-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhijie Shen updated YARN-1443:
------------------------------
Priority: Major (was: Minor)
> blacklist is not propagated from AM to RM
> -----------------------------------------
>
> Key: YARN-1443
> URL: https://issues.apache.org/jira/browse/YARN-1443
> Project: Hadoop YARN
> Issue Type: Bug
> Components: api, client
> 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.1#6144)