Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 22 May 2013 17:37:31 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12626879.1357776464693.5360.1369244251086@arcas>
In-Reply-To: <JIRA.12626879.1357776464693@arcas>
References: <JIRA.12626879.1357776464693@arcas>
Subject: [jira] [Commented] (HADOOP-9194) RPC Support for QoS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas commented on HADOOP-9194:
-----------------------------------------

Luke, please update the trunk CHANGES.txt once a change gets ported to 2.x, to move the jira to appropriate section. I have made that change for this jira description in trunk.
                
> RPC Support for QoS
> -------------------
>
>                 Key: HADOOP-9194
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9194
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: ipc
>    Affects Versions: 2.0.2-alpha
>            Reporter: Luke Lu
>            Assignee: Junping Du
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-9194.patch, HADOOP-9194-v2.patch
>
>
> One of the next frontiers of Hadoop performance is QoS (Quality of Service). We need QoS support to fight the inevitable "buffer bloat" (including various queues, which are probably necessary for throughput) in our software stack. This is important for mixed workload with different latency and throughput requirements (e.g. OLTP vs OLAP, batch and even compaction I/O) against the same DFS.
> Any potential bottleneck will need to be managed by QoS mechanisms, starting with RPC. 
> How about adding a one byte DS (differentiated services) field (a la the 6-bit DS field in IP header) in the RPC header to facilitate the QoS mechanisms (in separate JIRAs)? The byte at a fixed offset (how about 0?) of the header is helpful for implementing high performance QoS mechanisms in switches (software or hardware) and servers with minimum decoding effort.

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