[
https://issues.apache.org/jira/browse/HDFS-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302782#comment-15302782
]
Hudson commented on HDFS-10431:
-------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #9866 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9866/])
HDFS-10431 Refactor and speedup TestAsyncDFSRename. Contributed by (szetszwo:
rev f4b9bcd87c66a39f0c93983431630e9d1b6e36d3)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestAsyncDFS.java
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestAsyncDFSRename.java
> Refactor and speedup TestAsyncDFSRename
> ---------------------------------------
>
> Key: HDFS-10431
> URL: https://issues.apache.org/jira/browse/HDFS-10431
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: test
> Reporter: Xiaobing Zhou
> Assignee: Xiaobing Zhou
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HDFS-10431-HDFS-9924.000.patch,
> HDFS-10431-HDFS-9924.001.patch
>
>
> 1. Move irrelevant parts out of TestAsyncDFSRename
> 2. Limit of max async calls(i.e. ipc.client.async.calls.max) is set and
> cached in ipc.Client. Client instances are cached based on SocketFactory. In
> order to test different cases in various limits, every test (e.g.
> TestAsyncDFSRename and TestAsyncDFS) creates separate instance of
> MiniDFSCluster and that of AsyncDistributedFileSystem hence. This is not
> efficient in that tests may take long time to bootstrap MiniDFSClusters. It's
> even worse if cluster needs to restart in the middle. This proposes to do
> refactoring to use shared instance of AsyncDistributedFileSystem for speedup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
