[
https://issues.apache.org/jira/browse/HDFS-11898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035615#comment-16035615
]
Konstantin Shvachko commented on HDFS-11898:
--------------------------------------------
I don't think new variable {{hedgedReadEnabled}} is needed. You should reset
{{HEDGED_READ_THREAD_POOL}} as I commented above.
Not sure you addressed any of my comments in the last patch.
I think HDFS-11900 should be combined with this issue.
> 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, HDFS-11898-02.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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
