You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/09/09 23:14:33 UTC

[jira] [Updated] (HADOOP-9194) RPC Support for QoS

     [ https://issues.apache.org/jira/browse/HADOOP-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated HADOOP-9194:
-------------------------------------
    Fix Version/s:     (was: 3.0.0)
                   2.1.0-beta

> 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: 2.1.0-beta
>
>         Attachments: HADOOP-9194-v2.patch, HADOOP-9194.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 was sent by Atlassian JIRA
(v6.3.4#6332)