[
https://issues.apache.org/jira/browse/HBASE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639945#comment-13639945
]
Jonathan Hsieh edited comment on HBASE-8337 at 4/24/13 1:28 AM:
----------------------------------------------------------------
I need some feedback from [~apurtell] about why we need the use of the
different users in MiniHBaseCluster. For the sake of getting unit tests to
pass, I think turning SCR off is our current goto option (a few recovery tests
have been "fixed" by disabling SCR in them). The next option is to use the
insecure version and fix our configuration/users in our MiniHBaseCluster.
Colin advocate for using new style, but apache 2.0 series won't have it.
was (Author: jmhsieh):
I need some feedback from [~apurtell] about why we need the use of the
different users in MiniHBaseCluster. For the sake of getting unit tests to
pass, I think turning SCR off is open option. The next option is to use the
insecure version and fix our configuration/users in our MiniHBaseCluster.
Colin advocate for using new style, but apache 2.0 series won't have it.
> 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
