hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5267) Modification field in LightWeightHashSet and LightWeightLinkedSet should't be volatile which cause wrong expectation on thread-safe visibility
Date Fri, 27 Sep 2013 06:20:03 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Junping Du updated HDFS-5267:
-----------------------------

    Summary: Modification field in LightWeightHashSet and LightWeightLinkedSet should't be
volatile which cause wrong expectation on thread-safe visibility  (was: Modification field
in LightWeightHashSet and LightWeightLinkedSet should't be volatile to get rid of wrong expectation
on thread-safe visibility)
    
> Modification field in LightWeightHashSet and LightWeightLinkedSet should't be volatile
which cause wrong expectation on thread-safe visibility
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5267
>                 URL: https://issues.apache.org/jira/browse/HDFS-5267
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Junping Du
>            Assignee: Junping Du
>             Fix For: 2.3.0
>
>         Attachments: HADOOP-9980.patch
>
>
> LightWeightGSet should have a volatile modification field (like: LightWeightHashSet or
LightWeightLinkedSet) that is used to detect updates while iterating so they can throw a ConcurrentModificationException.

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

Mime
View raw message