hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18784) Use of filesystem that requires hflush / hsync / append / etc should query outputstream capabilities
Date Wed, 15 Nov 2017 16:58:00 GMT

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

Mike Drob commented on HBASE-18784:
-----------------------------------

We only need this in branch-1 if we're planning on supporting hadoop-3 there, right? That
may be too aggressive of a goal, I'm not sure.

> 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
>             Fix For: 2.1.0, 1.5.0
>
>         Attachments: HBASE-18784-branch-1.v2.patch, HBASE-18784.0.patch, HBASE-18784.1.patch,
HBASE-18784.2.patch
>
>
> 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