hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations
Date Sat, 10 Aug 2013 01:07:49 GMT

     [ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Abdelnur updated YARN-1008:
-------------------------------------

    Attachment: YARN-1008.patch

trying again, it apply locally.

in short:

* i've added a new property to NodeId 'nodeName'
* i've added a config to the NMs to set the host or host:port there, default is host (current
behavior)
* i've renamed SchedulerNode.getHostname to getNodeName, and made its implementations to use
NodeId.getNodeName()
* testcase with minicluster that test that node reports have the right value according to
the setting.
* testcase for FS that verify nothing is broken leveraging strict locality test (didn't find
similar tests in capacity and fifo schedulers)
                
> MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-1008
>                 URL: https://issues.apache.org/jira/browse/YARN-1008
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: YARN-1008.patch, YARN-1008.patch
>
>
> While the NMs are keyed using the NodeId, the allocation is done based on the hostname.

> This makes the different nodes indistinguishable to the scheduler.
> There should be an option to enabled the host:port instead just port for allocations.
The nodes reported to the AM should report the 'key' (host or host:port). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message