Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.2-alpha
-
None
-
Incompatible change, Reviewed
-
Part of the RPC version 9 change. A service class byte is added after the version byte.
Description
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.
Attachments
Attachments
Issue Links
- duplicates
-
HDFS-945 Make NameNode resilient to DoS attacks (malicious or otherwise)
- Resolved
- is blocked by
-
HADOOP-9380 Add totalLength to rpc response
- Closed
- relates to
-
HDFS-4412 Support HDFS IO throttling
- Open
-
HDFS-237 Better handling of dfsadmin command when namenode is slow
- Resolved
-
HADOOP-9640 RPC Congestion Control with FairCallQueue
- Resolved