[
https://issues.apache.org/jira/browse/YARN-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143460#comment-16143460
]
Hudson commented on YARN-7051:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #12253 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/12253/])
YARN-7051. Avoid concurrent modification exception in (sunilg: rev
02599bda04e0ef46f4628b006f2430ad63cac97e)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/monitor/capacity/FifoIntraQueuePreemptionPlugin.java
> Avoid concurrent modification exception in FifoIntraQueuePreemptionPlugin
> -------------------------------------------------------------------------
>
> Key: YARN-7051
> URL: https://issues.apache.org/jira/browse/YARN-7051
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, scheduler preemption, yarn
> Affects Versions: 2.9.0, 2.8.1, 3.0.0-alpha3
> Reporter: Eric Payne
> Assignee: Eric Payne
> Priority: Critical
> Attachments: YARN-7051.001.patch, YARN-7051.002.patch
>
>
> {{FifoIntraQueuePreemptionPlugin#calculateUsedAMResourcesPerQueue}} has the
> following code:
> {code}
> Collection<FiCaSchedulerApp> runningApps = leafQueue.getApplications();
> Resource amUsed = Resources.createResource(0, 0);
> for (FiCaSchedulerApp app : runningApps) {
> {code}
> {{runningApps}} is unmodifiable but not concurrent. This caused the
> preemption monitor thread to crash in the RM in one of our clusters.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
