[
https://issues.apache.org/jira/browse/HBASE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177895#comment-14177895
]
Rishit Shroff commented on HBASE-12259:
---------------------------------------
[~stack] HydraBase aims at X-DC WAN story, but it can be easily deployed to
in-DC, in-cluster setup. We will be able to reap in the same benefits with the
new quorum based WAL.
Refactoring the WAL into a separate module is a good idea and should make it
easier to plug in the RAFT Consensus protocol.
We should start this effort in a separate feature branch as there will be
changes not only in the WAL but in other modules like HRegion/HMaster/etc. I
will discuss the approach with other team members first before we lay down the
roadmap for this integration.
Regarding upgrades, I think taking a down time will be much cleaner, but we can
look into rolling-upgrades if that's a necessity.
> Bring quorum based write ahead log into HBase
> ---------------------------------------------
>
> Key: HBASE-12259
> URL: https://issues.apache.org/jira/browse/HBASE-12259
> Project: HBase
> Issue Type: Improvement
> Components: wal
> Affects Versions: 2.0.0
> Reporter: Elliott Clark
>
> HydraBase (
> https://code.facebook.com/posts/321111638043166/hydrabase-the-evolution-of-hbase-facebook/
> ) Facebook's implementation of HBase with Raft for consensus will be going
> open source shortly. We should pull in the parts of that fb-0.89 based
> implementation, and offer it as a feature in whatever next major release is
> next up. Right now the Hydrabase code base isn't ready to be released into
> the wild; it should be ready soon ( for some definition of soon).
> Since Hydrabase is based upon 0.89 most of the code is not directly
> applicable. So lots of work will probably need to be done in a feature branch
> before a merge vote.
> Is this something that's wanted?
> Is there anything clean up that needs to be done before the log
> implementation is able to be replaced like this?
> What's our story with upgrading to this? Are we ok with requiring down time ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
