[
https://issues.apache.org/jira/browse/HBASE-25449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259961#comment-17259961
]
Josh Elser commented on HBASE-25449:
------------------------------------
Our [~karthikshva...@gmail.com] found this one over the weekend, too. We've
been scrambling to realize the impact of this. It's bad.
Worse, really, because on 2.1 based releases, we don't have HBASE-8868 to even
tell us (via metrics) that SCRs aren't happening.
Discussions with Busbey so far seem to indicate that our best course of action
is to remove these from hbase-default.xml and that will fix a bunch of other
things. The workaround is to re-set all of these properties from hdfs-site.xml
back into hbase-site.xml.
> 'dfs.client.read.shortcircuit' should not be set in hbase-default.xml
> ---------------------------------------------------------------------
>
> Key: HBASE-25449
> URL: https://issues.apache.org/jira/browse/HBASE-25449
> Project: HBase
> Issue Type: Improvement
> Components: conf
> Affects Versions: 2.0.1
> Reporter: shenshengli
> Assignee: shenshengli
> Priority: Major
>
> I think this parameter is not suitable for in hbase-default.xml, because in
> this case, HDFS explicitly set to "dfs.client.read.shortcircuit=true", hbase
> rely on HDFS configuration, the parameters in hbase service still is
> false.Must be explicitly in hbase-site.xml is set to
> "dfs.client.read.shortcircuit=true" to take effect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
