Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 10 Oct 2012 23:33:03 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1026426758.23269.1349911983138.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HDFS-4035) LightWeightGSet and LightWeightHashSet
 increment a volatile without synchronization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Eli Collins created HDFS-4035:
---------------------------------

             Summary: LightWeightGSet and LightWeightHashSet increment a volatile without synchronization
                 Key: HDFS-4035
                 URL: https://issues.apache.org/jira/browse/HDFS-4035
             Project: Hadoop HDFS
          Issue Type: Sub-task
    Affects Versions: 2.0.0-alpha
            Reporter: Eli Collins
            Assignee: Eli Collins


LightWeightGSet and LightWeightHashSet have a volatile modification field that they use to detect updates while iterating so they can throw a ConcurrentModificationException. Since these "LightWeight" classes are explicitly "not thread safe" (eg access to their members is not synchronized) then the current use is OK, we just need to update findbugsExcludeFile.xml to exclude them.

  
--
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