zjffdu commented on issue #8144: [FLINK-12159]. Enable YarnMiniCluster integration test under non-secure mode URL: https://github.com/apache/flink/pull/8144#issuecomment-483517975 > If a downstream process sets up a YarnMiniCluster it could configure the port differently. Flink would not need to be changed. If user use YarnMiniCluster directly, and don't set `yarn.minicluster.fixed.ports` to be `true`, then JM can not connect RM (JM will connect to default scheduler port 8030, but the actual scheduler port is a random port which is stored in yarn-site.xml and flink didn't ship it to JM). @tillrohrmann I have fixed the UT failure issue. The root cause is that if I remove the setting of `yarn.minicluster.fixed.ports`, flink client can not connect RM to allocate container for JM because it didn't create yarnClient properly.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
