hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@cloudera.com>
Subject Re: [DISCUSS] Make AsyncFSWAL the default WAL in 2.0
Date Fri, 29 Apr 2016 02:57:34 GMT
I am nervous about having default out-of-the-box new HBase users reliant on
a bespoke HDFS client, especially given Hadoop's compatibility
promises and history. Answers for these questions would make me more

1) Where are we on getting the client-side changes to HDFS pushed back upstream?

2) How well do we detect when our FS is not HDFS and what does
fallback look like?

3) Will this mean altering the versions of Hadoop we label as
supported for HBase 2.y+?

4) How are we going to ensure our client remains compatible with newer
Hadoop releases?

On Thu, Apr 28, 2016 at 9:42 PM, Duo Zhang <zhangduo@apache.org> wrote:
> Six month after I filed HBASE-14790...
> Now the AsyncFSWAL is ready. The WALPE result shows that it is *1.4x~3.7x*
> faster than FSHLog. The ITBLL result turns out that it is *not bad* than
> FSHLog(the master branch is not that stable itself...).
> More details can be found on HBASE-15536.
> So here we propose to change the default WAL from FSHLog to AsyncFSWAL.
> Suggestions are welcomed.
> Thanks.


View raw message