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

Sean Busbey commented on HBASE-25449:
-------------------------------------

we've recently run into this at $DAYJOB as well. Personally I don't think any 
HDFS configs should be present in the hbase config files. Our server processes 
should get the configs they need for their HDFS client connections from a 
hdfs-site.xml file. Doing otherwise raises a lot of concerns about how we 
prioritize various site and default xml files.

For example, we found in our case deployments would have {{hbase-default.xml}} 
was taking priority and effectively disabling ALL SCR access for HBase 
RegionServers even when HDFS was set to enable the feature.

> '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)

Reply via email to