hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matteo Bertozzi <theo.berto...@gmail.com>
Subject Re: Ramifications of minimizing use of .tmp directories / renames in HBase when using S3 as backing store
Date Wed, 09 Sep 2015 23:31:24 GMT
hbase relies on .tmp directories to do some sort of "atomic" file creation.
and avoid problems like half data written when it crashes.

there is a jira open, to solve that problem in one of the next major
There is a document in it, if you are interested in reading about the


On Wed, Sep 9, 2015 at 4:23 PM, Anthony Nguyen <anthony.an.nguyen@gmail.com>

> Hi all,
> I'm investigating the use of S3 as a backing store for HBase. Would there
> be any major issues with modifying HBase in such a way where when an S3
> location is set for the rootdir, writes to .tmp are removed and minimized,
> instead writing directly to the final destination? The reason I'd like to
> do this is because renames in S3 are expensive and performance for
> operations such as compactions and snapshot restores that have many renames
> suffer.
> Thanks!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message