[ https://issues.apache.org/jira/browse/MYRIAD-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Santosh Marella updated MYRIAD-160: ----------------------------------- Fix Version/s: Myriad 0.1.0 > Randomize ports on which NM starts > ---------------------------------- > > Key: MYRIAD-160 > URL: https://issues.apache.org/jira/browse/MYRIAD-160 > Project: Myriad > Issue Type: Bug > Components: Scheduler > Reporter: Aashreya Ravi Shankar > Assignee: Yuliya Feldman > Fix For: Myriad 0.1.0 > > > When a CGS node is present and gets replaced by a FGS node after a flex-down > and flex-up, the memory calculation is going wrong. I see the applications > hang and the AM container fails to get scheduled. > By default when a NM is started, it is started on a random port. Only the web > server port is fixed to 8042. > The behavior should be similar in Myriad. We need to randomize the port of > the NM from the offer obtained from mesos. So when we flex down and flex-up > it starts on a different port. Otherwise Myriad considers this as the same NM > with different resources. Hence the memory calculation issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)