[
https://issues.apache.org/jira/browse/YARN-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832075#comment-13832075
]
Robert Grandl commented on YARN-1443:
-------------------------------------
This happened in MR App master. However, it is not clear if the bug is due to
MR implementation or Yarn API. From my side, the blacklist is NOT propagated
from MR AM to RM. But as far as I did the tracing, it goes correctly to
YARN-API.
If this may need to be moved to MAPREDUCE project, can you take care of that ?
Thanks.
> 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
> Priority: Minor
>
> 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)
