[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639881#comment-14639881 ]
Brahma Reddy Battula commented on YARN-3528: -------------------------------------------- [~wheat9] Yes, will bind to '0' wherever applicable(Please check comment [here|https://issues.apache.org/jira/browse/YARN-3528?focusedCommentId=14567153&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14567153] ). but as [~rkanter] mentioned, In some places it looks like we set a config (e.g. NM address,,Recovery enabled) and then some other code actually starts using the port based on the config. In that case, I think we can do something like this to choose a dynamic port. > Tests with 12345 as hard-coded port break jenkins > ------------------------------------------------- > > Key: YARN-3528 > URL: https://issues.apache.org/jira/browse/YARN-3528 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 3.0.0 > Environment: ASF Jenkins > Reporter: Steve Loughran > Assignee: Brahma Reddy Battula > Priority: Blocker > Labels: test > Attachments: YARN-3528-002.patch, YARN-3528.patch > > > A lot of the YARN tests have hard-coded the port 12345 for their services to > come up on. > This makes it impossible to have scheduled or precommit tests to run > consistently on the ASF jenkins hosts. Instead the tests fail regularly and > appear to get ignored completely. > A quick grep of "12345" shows up many places in the test suite where this > practise has developed. > * All {{BaseContainerManagerTest}} subclasses > * {{TestNodeManagerShutdown}} > * {{TestContainerManager}} > + others > This needs to be addressed through portscanning and dynamic port allocation. > Please can someone do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)