[
https://issues.apache.org/jira/browse/YARN-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765904#comment-13765904
]
Karthik Kambatla commented on YARN-1183:
----------------------------------------
bq. It may be a non necessary optimization in the testing code
MiniYARNCluster is used by several tests. This might bite us if and when we run
tests parallely.
bq. Can you advice on how to get ApplicationID from
RegisterApplicationMasterRequest/RegisterApplicationMasterResponse?
Here, using host:port should be good - only a single application runs on the
host:port at any point.
Also, in the following code, even the while() should also be in the
synchronized block. Otherwise, it is possible to loose notifications and wait
longer than needed.
{code}
while (!appMasters.isEmpty() && System.currentTimeMillis() - started <
timeoutMillis) {
synchronized (appMasters) {
appMasters.wait(1000);
}
}
{code}
> MiniYARNCluster shutdown takes several minutes intermittently
> -------------------------------------------------------------
>
> Key: YARN-1183
> URL: https://issues.apache.org/jira/browse/YARN-1183
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Andrey Klochkov
> Attachments: YARN-1183--n2.patch, YARN-1183.patch
>
>
> As described in MAPREDUCE-5501 sometimes M/R tests leave MRAppMaster java
> processes living for several minutes after successful completion of the
> corresponding test. There is a concurrency issue in MiniYARNCluster shutdown
> logic which leads to this. Sometimes RM stops before an app master sends it's
> last report, and then the app master keeps retrying for >6 minutes. In some
> cases it leads to failures in subsequent tests, and it affects performance of
> tests as app masters eat resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
