[
https://issues.apache.org/jira/browse/HDFS-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819611#comment-13819611
]
Lohit Vijayarenu commented on HDFS-5499:
----------------------------------------
[~wheat9] Thanks. Yes, that is one option as well. But concern of other hidden
components getting throttled would still remain for this if this was set as a
clusterwide config, right?
> Provide way to throttle per FileSystem read/write bandwidth
> -----------------------------------------------------------
>
> Key: HDFS-5499
> URL: https://issues.apache.org/jira/browse/HDFS-5499
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Lohit Vijayarenu
> Attachments: HDFS-5499.1.patch
>
>
> In some cases it might be worth to throttle read/writer bandwidth on per JVM
> basis so that clients do not spawn too many thread and start data movement
> causing other JVMs to starve. Ability to throttle read/write bandwidth on per
> FileSystem would help avoid such issues.
> Challenge seems to be how well this can be fit into FileSystem code. If one
> enables throttling around FileSystem APIs, then any hidden data transfer
> within cluster using them might also be affected. Eg. copying job jar during
> job submission, localizing resources for distributed cache and such.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
