You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2011/04/23 08:51:05 UTC
[jira] [Created] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Rename dfs.datanode.max.xcievers and bump it's default value
------------------------------------------------------------
Key: HDFS-1861
URL: https://issues.apache.org/jira/browse/HDFS-1861
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Eli Collins
Assignee: Eli Collins
Fix For: 0.23.0
Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HDFS-1861:
------------------------------
Attachment: hdfs-1861-1.patch
Patch attached.
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.23.0
>
> Attachments: hdfs-1861-1.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023530#comment-13023530 ]
dhruba borthakur commented on HDFS-1861:
----------------------------------------
maybe do it in a backward-compatible way for a release or two?
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.23.0
>
> Attachments: hdfs-1861-1.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HDFS-1861:
------------------------------
Component/s: data-node
Fix Version/s: 0.22.0
Hadoop Flags: [Reviewed]
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HDFS-1861:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've committed this to branch 22 and trunk. Thanks Dhruba and Todd!
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024879#comment-13024879 ]
Todd Lipcon commented on HDFS-1861:
-----------------------------------
how about "dfs.datanode.max.xfer.threds?"
Just kidding. Yours is good.
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.23.0
>
> Attachments: hdfs-1861-1.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HDFS-1861:
------------------------------
Attachment: hdfs-1861-2.patch
Patch attached. Same as the last one just s/"receiver"/"transfer" in DFSConfigKeys.
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated HDFS-1861:
------------------------------
Status: Patch Available (was: Open)
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024855#comment-13024855 ]
Eli Collins commented on HDFS-1861:
-----------------------------------
How about "dfs.datanode.max.transfer.threads"? The words receiver and transceiver refer to the implementation (pipe-lined repl) and therefore probably make less sense to users.
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.23.0
>
> Attachments: hdfs-1861-1.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024684#comment-13024684 ]
Todd Lipcon commented on HDFS-1861:
-----------------------------------
I don't think "receiver.threads" is correct - these threads are used for both writing and reading blocks. max.transceiver.threads is probably a better name.
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.23.0
>
> Attachments: hdfs-1861-1.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023611#comment-13023611 ]
dhruba borthakur commented on HDFS-1861:
----------------------------------------
apologies, patch looks good. +1
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.23.0
>
> Attachments: hdfs-1861-1.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025931#comment-13025931 ]
Eli Collins commented on HDFS-1861:
-----------------------------------
Filed HDFS-1866.
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026288#comment-13026288 ]
Hudson commented on HDFS-1861:
------------------------------
Integrated in Hadoop-Hdfs-trunk #650 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/650/])
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031464#comment-13031464 ]
Hudson commented on HDFS-1861:
------------------------------
Integrated in Hadoop-Hdfs-22-branch #41 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-22-branch/41/])
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Aaron T. Myers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025871#comment-13025871 ]
Aaron T. Myers commented on HDFS-1861:
--------------------------------------
Apologies for showing up to this JIRA late, but this JIRA seems like a good opportunity to have added this config to {{hdfs-default.xml}}, with a helpful description. Changing the name of it is good, but I believe there's still no documentation about it.
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Jakob Homan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Homan updated HDFS-1861:
------------------------------
Summary: Rename dfs.datanode.max.xcievers and bump its default value (was: Rename dfs.datanode.max.xcievers and bump it's default value)
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025027#comment-13025027 ]
Hadoop QA commented on HDFS-1861:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12477337/hdfs-1861-2.patch
against trunk revision 1096010.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these core unit tests:
org.apache.hadoop.hdfs.TestFileAppend4
org.apache.hadoop.hdfs.TestLargeBlock
org.apache.hadoop.hdfs.TestWriteConfigurationToDFS
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/415//testReport/
Findbugs warnings: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/415//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/415//console
This message is automatically generated.
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025045#comment-13025045 ]
Hudson commented on HDFS-1861:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #604 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/604/])
HDFS-1861. Rename dfs.datanode.max.xcievers and bump its default value. Contributed by Eli Collins
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump its default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025037#comment-13025037 ]
Eli Collins commented on HDFS-1861:
-----------------------------------
Test failures are unrelated.
> Rename dfs.datanode.max.xcievers and bump its default value
> -----------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hdfs-1861-1.patch, hdfs-1861-2.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and
bump it's default value
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023571#comment-13023571 ]
Eli Collins commented on HDFS-1861:
-----------------------------------
Isn't the attached patch backwards-compatible? It adds dfs.datanode.max.xcievers as a deprecated key, does not remove it.
> Rename dfs.datanode.max.xcievers and bump it's default value
> ------------------------------------------------------------
>
> Key: HDFS-1861
> URL: https://issues.apache.org/jira/browse/HDFS-1861
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.23.0
>
> Attachments: hdfs-1861-1.patch
>
>
> Reasonably sized jobs and HBase easily exhaust the current default for dfs.datanode.max.xcievers. 4096 works better in practice.
> Let's also deprecate it in favor of a more intuitive name, eg dfs.datanode.max.receiver.threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira