amahussein opened a new pull request #3200:
URL: https://github.com/apache/hadoop/pull/3200


   
    - Backporting HDFS-15160 to branch-3.2
      - First: [HDFS-15150. Introduce read write lock to Datanode. Contributed 
Stephen O'Donnell](https://issues.apache.org/jira/browse/HDFS-15150)
        - `git cherry-pick -x d7c136b9ed6d99e1b03f5b89723b3a20df359ba8`
        - main conflicts:
          - `FsDatasetImpl.java.deepCopyReplica`
          - `FoldedTreeSet` is not used in branch-3.2
        - testing:
          - ```
            mvn test -Dtest=TestWriteToReplica,TestReplicaMap,\
                    TestProvidedImpl,TestFsVolumeList,TestInterDatanodeProtocol
            ```
      - Second: [HDFS-15160](https://issues.apache.org/jira/browse/HDFS-15160)
        - `git cherry-pick -x 2a67e2b1a0e3a5f91056f5b977ef9c4c07ba6718`
        - main conflicts:
          - `ReplicaMap.java`
          - `FsDatasetImpl.java.deepCopyReplica`
          - `FsDatasetImpl.java.addVolume` different code. I passed the red and 
write locks to `tempVolumeMap`
          - `DirectoryScanner.scan()` conflict in the entire loop.
             - [HDFS-15415. Reduce locking in Datanode 
DirectoryScanner](https://issues.apache.org/jira/browse/HDFS-15415) Which is 
already committed to branch-2.10 removes what 
[HDFS-15160](https://issues.apache.org/jira/browse/HDFS-15160) has added. So, I 
skipped that.
       - Third: [HDFS-15457. TestFsDatasetImpl fails intermittently 
(#2407)](https://issues.apache.org/jira/browse/HDFS-15457) and [HDFS-15818. Fix 
TestFsDatasetImpl.testReadLockCanBeDisabledByConfig 
(#2679)](https://issues.apache.org/jira/browse/HDFS-15818)
         - `git cherry-pick -x 98097b8f19789605b9697f6a959da57261e0fe19 
9434c1eccc255a25ea5e11f6d8c9e1f83996d6b4`
         - main conflicts:
           - Java imports


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



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

Reply via email to