[ https://issues.apache.org/jira/browse/MYRIAD-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Santosh Marella reopened MYRIAD-102: ------------------------------------ Assignee: DarinJ > Issue MYRIAD-40: Mesos now dynamically configures ports of the Node Manager > --------------------------------------------------------------------------- > > Key: MYRIAD-102 > URL: https://issues.apache.org/jira/browse/MYRIAD-102 > Project: Myriad > Issue Type: Bug > Reporter: DarinJ > Assignee: DarinJ > > Mesos now dynamically configures ports of the Node Manager. This addresses > Issue MYRIAD-40 completely and Issue MYRIAD-45 partially. > This is done by first checking if three ports are available in the resource > offer, if so they are added the TaskInfo object and passed to the executor > via NMTaskConfig. > Added {{NMPorts.java}}, an immutable helper class used by > {{TaskFactory.java}}, essentially a Tuple Object. > Tested on one node cluster, map reduce jobs complete as expected, all NM web > ports are linked to the RM as expected. > Updated {{myriad-dev.md}} to reflect changes. Other than the modifications > to {{yarn-site.xml}} no other changes are needed. If the modifications are > left out, the node manage will use the default ports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)