[
https://issues.apache.org/jira/browse/HADOOP-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943363#comment-13943363
]
Haohui Mai commented on HADOOP-10410:
-------------------------------------
bq. If i want to let some online users read/write HBase more timely ...
That's exactly the point I'm making. The patch is for your particular use case
on a specific platform of a specific setting (HBase on Linux). Though valuable
to make the use case work, the HDFS APIs, however, have to carefully designed
to support other use cases (e.g., MR) and other platforms.
I have raised my concerns that the design is yet to be completed. IMHO I don't
think committing to any mechanisms like {{ioprio_*}} before going through the
design is a good idea.
bq. Do you agree then that his suggestion of a QoS pool, HDFS-5727, the right
way to proceed?
Detailed designs are welcome.
> Support ioprio_set in NativeIO
> ------------------------------
>
> Key: HADOOP-10410
> URL: https://issues.apache.org/jira/browse/HADOOP-10410
> Project: Hadoop Common
> Issue Type: New Feature
> Components: native
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Attachments: HADOOP-10410.txt
>
>
> It would be better to HBase application if HDFS layer provide a fine-grained
> IO request priority. Most of modern kernel should support ioprio_set system
> call now.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
