hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11898) DFSClient#isHedgedReadsEnabled() should be per client flag
Date Mon, 29 May 2017 09:53:04 GMT

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

Vinayakumar B commented on HDFS-11898:

bq. Vinayakumar B While the patch 01 LGTM, there seems to be some fundamental issue described
in HDFS-11900 I just filed. Could you please take a look?
Yes, that seems to be reasonable analysis.
May be if go with #2 there non-static threadpool, current issue would be solved automatically.
Do you want to upload patch for that? or convert current jira itself to solve HDFS-11900.

> DFSClient#isHedgedReadsEnabled() should be per client flag 
> -----------------------------------------------------------
>                 Key: HDFS-11898
>                 URL: https://issues.apache.org/jira/browse/HDFS-11898
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-11898-01.patch
> DFSClient#isHedgedReadsEnabled() returns value based on static {{HEDGED_READ_THREAD_POOL}}.

> Hence if any of the client initialized this in JVM, all remaining client reads will be
going through hedged read itself.
> This flag should be per client value.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message