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

Sean Busbey commented on HBASE-21735:
-------------------------------------

that config was added in HBASE-19289 and things didn't show up because out of 
the box we aren't running against a hadoop version that has StreamCapabilities.

I think StreamCapabilities got into branch-2 Hadoop now? If I'm remembering 
that correctly then we should consider including in this backport the related 
fixes it took to have unit tests pass, ITBLL pass, and guidance for downstream 
users of LocalFileSystem. Unfortunately the JIRA titles didn't do a good job 
here:

* HBASE-19289 CommonFSUtils$StreamLacksCapabilityException: hflush when running 
test against hadoop3 beta1
* HBASE-19841 Tests against hadoop3 fail with StreamLacksCapabilityException
* HBASE-19947 MR jobs using ITU use wrong filesystem
* HBASE-20354 [DOC] quickstart guide needs to include note about durability 
checks for standalone mode

> Port HBASE-18784 (Use of filesystem that requires hflush / hsync / append / 
> etc should query outputstream capabilities) to branch-1
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-21735
>                 URL: https://issues.apache.org/jira/browse/HBASE-21735
>             Project: HBase
>          Issue Type: Sub-task
>          Components: fs, wal
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Major
>              Labels: s3
>             Fix For: 1.5.0
>
>         Attachments: HBASE-21735-branch-1.patch, HBASE-21735-branch-1.patch
>
>
> HBASE-18784 has nice checks for fs capabilities and logged warnings, 
> especially useful on recent versions of hadoop. The refactors are minor and 
> are compatible with a minor release. Port to branch-1. 



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

Reply via email to