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

Josh Elser commented on HBASE-20951:
------------------------------------

Those with a close eye might stumble onto 
https://github.com/hbase-temp-wal-refactor/hbase/tree/wal-refactor.

To prevent anyone from thinking something heinous is going on: between myself, 
Ted, Ankit, and Sergey who were trying to get this effort off the ground, we 
have been struggling to get the ball rolling. To try to iterate faster and get 
something of better quality into Apache for an initial API/interface review, 
we've spun out this organization/fork.

Please rest assured that it is not a fork to do feature development outside of 
Apache, nor is it an attempt to circumvent those in Apache who have expressed 
interest in working on this. It is only a place for us to iterate on potential 
API changes more quickly, in order to bring a better first patch into Apache 
for review by the community. Please reach out to me if there are any concerns 
about this.

 

> Ratis LogService backed WALs
> ----------------------------
>
>                 Key: HBASE-20951
>                 URL: https://issues.apache.org/jira/browse/HBASE-20951
>             Project: HBase
>          Issue Type: New Feature
>          Components: wal
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>
> Umbrella issue for the Ratis+WAL work:
> Design doc: 
> [https://docs.google.com/document/d/1Su5py_T5Ytfh9RoTTX2s20KbSJwBHVxbO7ge5ORqbCk/edit#|https://docs.google.com/document/d/1Su5py_T5Ytfh9RoTTX2s20KbSJwBHVxbO7ge5ORqbCk/edit]
> The (over-simplified) goal is to re-think the current WAL APIs we have now, 
> ensure that they are de-coupled from the notion of being backed by HDFS, swap 
> the current implementations over to the new API, and then wire up the Ratis 
> LogService to the new WAL API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to