hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5278) Reduce memory consumptions of TestDFSClientRetries
Date Tue, 15 Oct 2013 22:32:42 GMT

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

Jing Zhao commented on HDFS-5278:

Thanks for the update, Haohui! Some comments:
# testWriteTimoutAtDataNode actually tests DFSInputStream's retry when DN's socket is closed
because of timeout. The current patch removes this part of test. Also, maybe we can rename
testWriteTimoutAtDataNode to "testReadRetryWithDNTimeout"?
# In testDFSClientRetriesOnBusyBlocks, I think we'd better keep the original number of clients
unchanged (i.e., 50) to make sure that each client has to retry and possibly retries multiple

> Reduce memory consumptions of TestDFSClientRetries
> --------------------------------------------------
>                 Key: HDFS-5278
>                 URL: https://issues.apache.org/jira/browse/HDFS-5278
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>            Priority: Minor
>         Attachments: HDFS-5278.000.patch, HDFS-5278.001.patch
> TestDFSClientRetries::testDFSClientRetriesOnBusyBlocks() spawns about 50 threads during
the execution, each of which takes more than 6m memory.  It makes debugging it in eclipse
under the default settings difficult since it triggers the OutOfMemoryException.

This message was sent by Atlassian JIRA

View raw message