[
https://issues.apache.org/jira/browse/HBASE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641031#comment-13641031
]
Gary Helmling commented on HBASE-8337:
--------------------------------------
[[email protected]] Yes the separate user per regionserver stuff in
MiniHBaseCluster is a bit wonky, but I believe that pre-dates my changes. I
would have to look back through the history again, but I think I just adapted
the mini cluster code to correctly handle this using User.runAs() when
integrating security.
I agree that each RS running as a different user is not going to be a typical
setup. Sounds like we might have been using that to work around FileSystem
instance caching? There may also be issues with HConnection sharing with a
single user, due to the HCM connection caching. There's another config
property we can set to work around that though. In general, running multiple
RS's within a single process is not a typical setup either.
Maybe I'm missing it in the discussion above, but why is this only a problem
with hadoop2 and not hadoop1? Is SCR not enabled by default in hadoop1?
> Investigate why disabling hadoop short circuit read is required to make
> recovery tests pass consistently under hadoop2
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-8337
> URL: https://issues.apache.org/jira/browse/HBASE-8337
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop2, test
> Affects Versions: 0.98.0, 0.95.1
> Reporter: Jonathan Hsieh
> Priority: Critical
> Fix For: 0.95.1
>
>
> HBASE-7636 makes some TestDistributedLogSplitting pass consistently by
> disabling hdfs short circuit reads.
> HBASE-8349 makes datanode node death recovery pass consistently by disabling
> hdfs short circuit reads.
> This will likely require configuration modifications to fix and may have
> different fixes for hadoop1, hadoop2 (HDFS-2246), and hadoop3 (HDFS-347)...
--
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
