[ 
https://issues.apache.org/jira/browse/HDFS-11287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829511#comment-15829511
 ] 

Hudson commented on HDFS-11287:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11140 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/11140/])
HDFS-11287. Storage class member storageDirs should be private to avoid (lei: 
rev 63320d1daab7ce846bb180623378efe431ad8c52)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockPoolSliceStorage.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/Storage.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataStorage.java


> Storage class member storageDirs should be private to avoid unprotected 
> access by derived classes
> -------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-11287
>                 URL: https://issues.apache.org/jira/browse/HDFS-11287
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Manoj Govindassamy
>            Assignee: Manoj Govindassamy
>             Fix For: 2.9.0, 3.0.0-alpha2
>
>         Attachments: HDFS-11287.01.patch, HDFS-11287.02.patch
>
>
> HDFS-11267 fix made the abstract class Storage.java member variable 
> storageDirs a thread safe one so that all its derived classes like NNStorage, 
> JNStorage, DataStorage will not face any ConcurrentModificationException when 
> there are volume add/remove and listing operations running in parallel. The 
> fix rebase missed out few changers to the original patch. This jira is to 
> address the addendum needed for the HDFS-11267 commits. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to