[ 
https://issues.apache.org/jira/browse/HBASE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213735#comment-14213735
 ] 

Rishit Shroff commented on HBASE-12259:
---------------------------------------

[~stack], No. The code over in HBASE-12476 is the RAFT Protocol implementation. 
The document in this JIRA is about the overall architecture. Please let me know 
if you need any information regarding HBASE-12476.

[~tedyu], No. The ACTIVE-WITNESS|SHADOW-WITNESS are both shown as 'Witness' in 
the diagram to keep it simple. The ACTIVE follower in the diagram means that:
1. From RAFT protocol perspective, that region server is a FOLLOWER
2. The same region server is the ACTIVE guy for DC-2 and will be doing 
flushes/compactions to HDFS. However it does not serve any client traffic. 

> 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
>         Attachments: Architecture for HydraBase (4).pdf
>
>
> 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)

Reply via email to