[
https://issues.apache.org/jira/browse/HBASE-20429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440006#comment-16440006
]
Andrew Purtell commented on HBASE-20429:
----------------------------------------
bq. A while back there was some work done (or proposed) to have HBase handle
the file metadata somewhere to avoid the necessity of renames (HBase would
update the path/location in this table so in effect, the rename would be
atomic).
This is interesting. Of course I missed it mired in 0.98 fleet maintenance. :-/
Could do this instead of or in addition to HBASE-20431, which proposes
something like SplitTransaction but for commits of store files after compaction
or flush.
> 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)
