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

Chris Nauroth commented on HDFS-5175:
-------------------------------------

Yes, you're right.  I mistakenly looked at the old httpclient dependency that 
we're going to remove.

Then, if I understand correctly, we have this dependency now...

{code}
    <dependency>
      <groupId>org.apache.httpcomponents</groupId>
      <artifactId>httpclient</artifactId>
      <scope>compile</scope>
    </dependency>
{code}

...and in addition, you're proposing that we add this dependency:

{code}
    <dependency>
      <groupId>org.apache.httpcomponents</groupId>
      <artifactId>httpcomponents-client</artifactId>
      <scope>compile</scope>
    </dependency>
{code}

Do I have it correct now?

It's possible I'm exaggerating the impact of adding this dependency, so it 
would be great to get more opinions.  An email to hdfs-dev would be a good way 
to call attention to it.

> 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)

Reply via email to