[
https://issues.apache.org/jira/browse/HCATALOG-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753902#comment-13753902
]
Hudson commented on HCATALOG-631:
---------------------------------
SUCCESS: Integrated in Hive-trunk-h0.21 #2296 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/2296/])
HCATALOG-631 HBase e2e tests on single nodes on Hadoop 2.0.3 with
"dfs.client.read.shortcircuit" turning on for HBase (Daniel Dai via Sushanth
Sowmyan) (khorgath:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1518401)
*
/hive/trunk/hcatalog/core/src/main/java/org/apache/hcatalog/mapreduce/HCatOutputFormat.java
> HBase e2e tests on single nodes on Hadoop 2.0.3 with
> "dfs.client.read.shortcircuit" turning on for HBase
> ---------------------------------------------------------------------------------------------------------
>
> Key: HCATALOG-631
> URL: https://issues.apache.org/jira/browse/HCATALOG-631
> Project: HCatalog
> Issue Type: Bug
> Components: hbase
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: 0.6
>
> Attachments: HCATALOG-631-1.patch
>
>
> All HBase e2e fail: Pig_HBase_1, Pig_HBase_2.
> Here is diagnosis:
> * "dfs.client.read.shortcircuit" in hbase-site.xml is set to true, and
> "dfs.block.local-path-access.user" in hdfs-site.xml is set to "hbase"
> * HCat is running as "hcat"
> * HCat reads the hbase config and try to access hdfs block using local path
> * "hcat" is not in "dfs.block.local-path-access.user", so local access fail
> HDFS-4595 fix the issue in hdfs side. When local access fail, fall back to
> conventional read. However, performance wise, it is not desired because every
> time hdfs will try and fail while we know this will fail.
> Another possible fix is on hbase side, which separate client/server config,
> since "dfs.client.read.shortcircuit" is only needed on server side.
> Before hbase do anything, I provide a walk around to force
> "dfs.client.read.shortcircuit" to false on hcat side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
