[
https://issues.apache.org/jira/browse/HDFS-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183148#comment-14183148
]
Ming Ma commented on HDFS-5175:
-------------------------------
Thanks, Chris. Really appreciate your input.
1. Each http connection might have different DSCP values. It is a good idea to
use thread local variable so that webHDFS use it to set the DSCP value and
custom {{SocketFactory}} can access it . But yeah, the code might not be clean.
2. For httpclient dependency, per
https://issues.apache.org/jira/browse/HADOOP-10105, I assume it is on its way
out. If we keep httpclient, then we have to provide a way for webHDFS to use
httpclient given its dependency on URLConnection. For example, we can make
webHDFS configurable to use either URLConnection or httpclient. If people are
ok that, then we are good. The other option is to have webHDFS switch from
URLConnection to httpclient.
> Provide clients a way to set IP header bits on connections
> ----------------------------------------------------------
>
> Key: HDFS-5175
> URL: https://issues.apache.org/jira/browse/HDFS-5175
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.5-alpha
> Reporter: Lohit Vijayarenu
>
> It would be very helpful if we had ability for clients to set IP headers when
> they make socket connections for data transfers. We were looking into setting
> up QoS using DSCP bit and saw that there is no easy way to let clients pass
> down a specific value when clients make connection to DataNode.
> As a quick fix we did something similar to io.file.buffer.size where client
> could pass down DSCP integer value and when DFSClient opens a stream, it
> could set the value on socket using setTrafficClass
> Opening this JIRA to get more inputs from others who have had experience and
> might have already thought about this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
