[
https://issues.apache.org/jira/browse/HDFS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-797:
-----------------------------
Attachment: hdfs-797.txt
When closing DFSClient without force, it wasn't notifying dataQueue and also
wasn't interrupting. This patch adds a dataqueue.notifyAll() even in the
non-force case.
No test included since this is timing related and only occurs on some systems.
To test it manually I changed the dataQueue.wait to wait for 10 seconds and ran
TestHDFSCLI with test output showing. Before the patch, it was pausing 10
seconds in between each test case. With the patch, it did not noticeably pause.
This should be committed to 0.21 and 0.22
> TestHDFSCLI much slower after HDFS-265 merge
> --------------------------------------------
>
> Key: HDFS-797
> URL: https://issues.apache.org/jira/browse/HDFS-797
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-797.txt
>
>
> After the merge of HDFS-265 into trunk, TestHDFSCLI takes much longer to run
> (>10min, got tired of waiting). Changing dataQueue.wait(1000) to
> dataQueue.wait(10) on line 2708 speeds up the test back to its original
> performance. This isn't a fix, but displays the issue - somehow the thread
> isn't getting properly interrupted. In general this probably represents a
> performance regression for the exit of all HDFS writers (most noticeable in
> CLI tools)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
