hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Babak Behzad (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-6592) MR ApplicationMaster is not supposed to resolve rack locality! It should ask RM or NN about the topology
Date Mon, 28 Dec 2015 22:45:49 GMT
Babak Behzad created MAPREDUCE-6592:
---------------------------------------

             Summary: MR ApplicationMaster is not supposed to resolve rack locality! It should
ask RM or NN about the topology
                 Key: MAPREDUCE-6592
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6592
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
            Reporter: Babak Behzad
            Priority: Minor


While working on configuring Rack Awareness (following [HDP Documentation|http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1.5/bk_system-admin-guide/content/admin_configure_rack_awareness.html]),
we realized that this does not work for MR applications, unless the rack topology resolution
script is installed on the node managers where the application masters reside. Otherwise,
the AM will thrown an {{IOException: Cannot run program "/etc/hadoop/conf/rack_topology.sh"}}.


This is contradictory to the documentations which states it makes sense to have the scripts
that resolve the rack and node names on the Resource Manager and Name Node. 

It is clearly not scalable to require to install these scripts on all the node managers!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message