Bibin A Chundatt commented on YARN-8104:


Got confused with {{NodeAttributesManagerImpl#getNodeToAttributes}}. IIUC you 
are focusing on {{YarnClient#getNodeToAttributes}}.

 It does make sense from user's perspective since all other api to him are 
NodeID. But if user adds two nodemanagers in same machine.
 (How valid is the deployment scenarios i am also not sure.) this API might 
create additional confusion rt ??
 In distributed mode one Nodemanager can change attributes of second NM on same 

IMHO need further discussion on this point. Thoughts on having follow up jira 
after discussion for Node ID related clarifications ?.

*Regarding test timeout*

{{org.apache.hadoop.mapred.pipes.TestPipeApplication}} is getting timeout in 
trunk too .

> Add API to fetch node to attribute mapping
> ------------------------------------------
>                 Key: YARN-8104
>                 URL: https://issues.apache.org/jira/browse/YARN-8104
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>            Priority: Major
>         Attachments: YARN-8104-YARN-3409.001.patch, 
> YARN-8104-YARN-3409.002.patch, YARN-8104-YARN-3409.003.patch, 
> YARN-8104-YARN-3409.004.patch, YARN-8104-YARN-3409.005.patch
> Add node/host to attribute mapping in yarn client API.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to