hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18784) Use of filesystem that requires hflush / hsync / append / etc should query outputstream capabilities
Date Fri, 08 Sep 2017 21:36:00 GMT

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

Sean Busbey commented on HBASE-18784:
-------------------------------------

If we make a jira for "move Hadoop 3 to S in the support matrix" then this should be a blocker
for that.

> Use of filesystem that requires hflush / hsync / append / etc should query outputstream
capabilities
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18784
>                 URL: https://issues.apache.org/jira/browse/HBASE-18784
>             Project: HBase
>          Issue Type: Improvement
>          Components: Filesystem Integration
>    Affects Versions: 1.4.0, 2.0.0-alpha-2
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 2.1.0, 1.5.0
>
>
> In places where we rely on the underlying filesystem holding up the promises of hflush/hsync
(most importantly the WAL), we should use the new interfaces provided by HDFS-11644 to fail
loudly when they are not present (e.g. on S3, on EC mounts, etc).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message