hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8337) Investigate why disabling hadoop short circuit read is required to make recovery tests pass consistently under hadoop2
Date Fri, 19 Apr 2013 23:25:16 GMT

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

Jonathan Hsieh commented on HBASE-8337:
---------------------------------------

We defaulted to having "old-style" insecure scr on.  The error occurs because we create separate
users in HBaseMiniCluster (originally added from HBASE-3194)

https://github.com/apache/hbase/blob/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/MiniHBaseCluster.java#L279

https://github.com/apache/hbase/blob/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/MiniHBaseCluster.java#L353
                
> 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

Mime
View raw message