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

Mike Drob commented on HBASE-19841:
-----------------------------------

There's a lot of failure on branch-2, I'm going to revert this from master 
until I figure out why there are such huge differences. Sorry for the noise.

> Tests against hadoop3 fail with StreamLacksCapabilityException
> --------------------------------------------------------------
>
>                 Key: HBASE-19841
>                 URL: https://issues.apache.org/jira/browse/HBASE-19841
>             Project: HBase
>          Issue Type: Test
>            Reporter: Ted Yu
>            Assignee: Mike Drob
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>
>         Attachments: 19841.06.patch, 19841.v0.txt, 19841.v1.txt, 
> HBASE-19841.v2.patch, HBASE-19841.v3.patch, HBASE-19841.v4.patch, 
> HBASE-19841.v5.patch, HBASE-19841.v7.patch
>
>
> The following can be observed running against hadoop3:
> {code}
> java.io.IOException: cannot get log writer
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.compactingSetUp(TestCompactingMemStore.java:107)
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.setUp(TestCompactingMemStore.java:89)
> Caused by: 
> org.apache.hadoop.hbase.util.CommonFSUtils$StreamLacksCapabilityException: 
> hflush and hsync
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.compactingSetUp(TestCompactingMemStore.java:107)
>       at 
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.setUp(TestCompactingMemStore.java:89)
> {code}
> This was due to hbase-server/src/test/resources/hbase-site.xml not being 
> picked up by Configuration object. Among the configs from this file, the 
> value for "hbase.unsafe.stream.capability.enforce" relaxes check for presence 
> of hflush and hsync. Without this config entry,  
> StreamLacksCapabilityException is thrown.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to