[ https://issues.apache.org/jira/browse/FLINK-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972615#comment-15972615 ]
ASF GitHub Bot commented on FLINK-6130: --------------------------------------- Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/3726 What is the problem we're trying here to solve? > Consider calling resourceManager#getTerminationFuture() with lock held > ---------------------------------------------------------------------- > > Key: FLINK-6130 > URL: https://issues.apache.org/jira/browse/FLINK-6130 > Project: Flink > Issue Type: Bug > Reporter: Ted Yu > Assignee: mingleizhang > Priority: Minor > > In YarnFlinkApplicationMasterRunner#runApplicationMaster() : > {code} > synchronized (lock) { > LOG.info("Starting High Availability Services"); > ... > } > // wait for resource manager to finish > resourceManager.getTerminationFuture().get(); > {code} > resourceManager#getTerminationFuture() is called without holding lock. > We should store the value returned from > resourceManager#getTerminationFuture() inside the synchronized block. -- This message was sent by Atlassian JIRA (v6.3.15#6346)