hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4814) Configurable DataXceiver thread stack size
Date Sat, 11 May 2013 21:55:16 GMT

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

Tsz Wo (Nicholas), SZE commented on HDFS-4814:

According to the [javadoc|http://docs.oracle.com/javase/6/docs/api/java/lang/Thread.html#Thread%28java.lang.ThreadGroup,%20java.lang.Runnable,%20java.lang.String,%20long%29]
quoted below, setting the stackSize indeed could reduce memory usage in some platforms.

On some platforms, specifying a higher value for the stackSize parameter may allow a thread
to achieve greater recursion depth before throwing a StackOverflowError. Similarly, specifying
a lower value may allow a greater number of threads to exist concurrently without throwing
an OutOfMemoryError (or other internal error). The details of the relationship between the
value of the stackSize parameter and the maximum recursion depth and concurrency level are
platform-dependent. On some platforms, the value of the stackSize parameter may have no effect

> Configurable DataXceiver thread stack size
> ------------------------------------------
>                 Key: HDFS-4814
>                 URL: https://issues.apache.org/jira/browse/HDFS-4814
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: datanode
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: h4814_20130510.patch
> By default, Java creates a thread with 512kB stack size.  In Datanode, we may have 4096
or more DataXceiver threads.  These threads do not require such large stack size and unnecessarily
occupy a large amount of memory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message