[MYRIAD-160] Randomize ports on which NM starts

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Myriad 0.1.0
• Component/s: Scheduler
• Assignee: Yuliya Feldman
• Reporter: Aashreya Ravi Shankar
• Created: 21/Oct/15 18:55
• Updated: 29/Oct/15 21:45
• Resolved: 29/Oct/15 21:45

Description

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.

Issue Links

• relates to: MYRIAD-161 Flexdown should remove NM from RM's view