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

stack commented on HDFS-5776:
-----------------------------

Thanks lads.  We are almost there.

[~xieliang007] It is better if we work through the issues here before the patch 
goes in especially while you have the attention of quality reviewers.  From 
your POV, I'm sure it a little frustrating trying to drive the patch home 
between differing opinions (The time difference doesn't help either -- smile).  
Try to salve any annoyance with the thought that, though it may appear 
otherwise, folks here are trying to work together to help get the best patch 
in.  Good on you Liang.

[~xieliang007] I'd agree with the last few [~jingzhao] review comments.  What 
you think?

[~arpitagarwal] Do you buy [~cmccabe]'s argument?  It is good by me. If you 
agree, lets shift the focus to v10 and leave the v9 style behind.

Good stuff

> Support 'hedged' reads in DFSClient
> -----------------------------------
>
>                 Key: HDFS-5776
>                 URL: https://issues.apache.org/jira/browse/HDFS-5776
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client
>    Affects Versions: 3.0.0
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>         Attachments: HDFS-5776-v10.txt, HDFS-5776-v2.txt, HDFS-5776-v3.txt, 
> HDFS-5776-v4.txt, HDFS-5776-v5.txt, HDFS-5776-v6.txt, HDFS-5776-v7.txt, 
> HDFS-5776-v8.txt, HDFS-5776-v9.txt, HDFS-5776.txt
>
>
> This is a placeholder of hdfs related stuff backport from 
> https://issues.apache.org/jira/browse/HBASE-7509
> The quorum read ability should be helpful especially to optimize read outliers
> we can utilize "dfs.dfsclient.quorum.read.threshold.millis" & 
> "dfs.dfsclient.quorum.read.threadpool.size" to enable/disable the hedged read 
> ability from client side(e.g. HBase), and by using DFSQuorumReadMetrics, we 
> could export the interested metric valus into client system(e.g. HBase's 
> regionserver metric).
> The core logic is in pread code path, we decide to goto the original 
> fetchBlockByteRange or the new introduced fetchBlockByteRangeSpeculative per 
> the above config items.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to