[
https://issues.apache.org/jira/browse/YARN-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765538#comment-13765538
]
Karthik Kambatla commented on YARN-1183:
----------------------------------------
Patch looks mostly good. Few comments:
# The ConcurrentHashMap should be initialized with a smaller value for
concurrencyLevel (2?), and may be initialCapacity too.
# For the keys in the map, we should probably use ApplicationID instead of
trackingUrl as the trackingUrl can change by the time the app completes.
# Rename waitAppMastersToFinish to waitForAppMastersToFinish?
> 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.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
