[
https://issues.apache.org/jira/browse/HBASE-20429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584555#comment-16584555
]
Steve Loughran commented on HBASE-20429:
----------------------------------------
One thing which would be good for you all to write down is: what are your
expectations of an FS to work.
in particular
* create/read/update/delete consistency
* listing consistency
* which ops are required to be atomic and O(1)
* is it ok for create(path, overwrite=false) to be non-atomic?
* when you expect things to be written to store
* how long do you expect the final close() to take.
Identify these things and you can start to see what stores can work. And show
you where you need to involve other thigs for the semantics you need.
> Support for mixed or write-heavy workloads on non-HDFS filesystems
> ------------------------------------------------------------------
>
> Key: HBASE-20429
> URL: https://issues.apache.org/jira/browse/HBASE-20429
> Project: HBase
> Issue Type: Umbrella
> Reporter: Andrew Purtell
> Priority: Major
>
> We can support reasonably well use cases on non-HDFS filesystems, like S3,
> where an external writer has loaded (and continues to load) HFiles via the
> bulk load mechanism, and then we serve out a read only workload at the HBase
> API.
> Mixed workloads or write-heavy workloads won't fare as well. In fact, data
> loss seems certain. It will depend in the specific filesystem, but all of the
> S3 backed Hadoop filesystems suffer from a couple of obvious problems,
> notably a lack of atomic rename.
> This umbrella will serve to collect some related ideas for consideration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
