[
https://issues.apache.org/jira/browse/MAPREDUCE-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957499#comment-15957499
]
Haibo Chen commented on MAPREDUCE-6871:
---------------------------------------
Thanks [~rkanter] for the patch! A few comments
1) Do you think having regular expression for the configuration is more robust?
rack1/node2 will be treated as a node name with current implementation. If this
will cause application failure later, better we catch it early before
submission.
2) Maybe rename mapreduce.job.am.resource-request.strict.locality to
mapreduce.job.am.resource-request-strict-locality ?
3) The different test cases can be broken into different test methods
individually, so that one test case failure won't disguise failures in
following test cases.
> Allow users to specify racks and nodes for strict locality for AMs
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-6871
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6871
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: client
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: MAPREDUCE-6871.001.patch
>
>
> YARN-6050 fixed the YARN API to allow multiple {{ResourceRequest}}'s when
> submitting an AM so that you can actually do rack or node locality. We
> should allow MapReduce users to take advantage of this by exposing this
> functionality in some way. The raw YARN API allows for a lot of flexibility
> (e.g. different resources per request, etc), but we don't necessarily want to
> allow the user to do too much here so they don't shoot themselves in the foot
> and we don't make this overly complicated.
> I propose we allow users to specify racks and nodes for strict locality.
> This would allow users to restrict an MR AM to specific racks and/or nodes.
> We could add a new property,
> {{mapreduce.job.am.resource-request.strict.locality}}, which takes a
> comma-separated list of entries like:
> - {{/<rack>}}
> - {{/<rack>/<node>}}
> - {{<node>}} (assumes /default-rack)
> MapReduce would then use this information to create the corresponding
> {{ResourceRequest}}'s.
> For example,
> {{mapreduce.job.am.resource-request.strict.locality=/rack1/node1}} would
> create the following {{ResourceRequest}}'s:
> - resourceName=ANY, relaxLocality=false, capability=<X,Y>
> - resourceName=/rack1, relaxLocality=false, capability=<X,Y>
> - resourceName=node1, relaxLocality=true, capability=<X,Y>
> By default, the property would be unset, and you'd get the normal {{ANY}}
> {{ResourceRequest}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
