Return-Path: X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28FD0106D0 for ; Wed, 18 Sep 2013 14:26:07 +0000 (UTC) Received: (qmail 12654 invoked by uid 500); 18 Sep 2013 14:26:00 -0000 Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org Received: (qmail 12191 invoked by uid 500); 18 Sep 2013 14:25:55 -0000 Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-dev@hadoop.apache.org Delivered-To: mailing list mapreduce-dev@hadoop.apache.org Received: (qmail 12130 invoked by uid 99); 18 Sep 2013 14:25:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Sep 2013 14:25:52 +0000 Date: Wed, 18 Sep 2013 14:25:51 +0000 (UTC) From: "Jason Lowe (JIRA)" To: mapreduce-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MAPREDUCE-5513) ConcurrentModificationException in JobControl MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jason Lowe created MAPREDUCE-5513: ------------------------------------- Summary: ConcurrentModificationException in JobControl Key: MAPREDUCE-5513 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5513 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 0.23.9, 2.1.0-beta Reporter: Jason Lowe JobControl.toList is locking individual lists to iterate them, but those lists can be modified elsewhere without holding the list lock. The locking approaches are mismatched, with toList holding the lock on the actual list object while other methods hold the JobControl lock when modifying the lists. -- 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