[
https://issues.apache.org/jira/browse/HBASE-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221834#comment-14221834
]
stack commented on HBASE-12476:
-------------------------------
Thanks for putting the code into a module (thanks also for posting)
What direction do you think we should take this contrib? Toward the layout
described in the hydrabase doc or are you thinking we'd recast it as an
in-cluster quorum-of-regions? If the latter, would it be on all the time -- a
different sort of hbase -- or would it be something you could enable? HBase
2.0 or HBase 1.0?
Sorry for the big questions. No need of an answer now.... but we need to all
chat.
What should we do about swift out here in apache hbase? We'd redo it as pb and
rpc calls?
airlift is not for REST services, right? You are just using it for stats? You
like it? Better than the histograms we have going on out herein apache hbase?
You have a Counter, Duration, TimeDistribution, and ExpotentialDecay.. Need
airlift for this or could redo doing our current metrics dependencies?
Should apache hbase make use of jmxutils too? How you folks using it (Not
reviewed the patch yet).
Let me get you more feedback. Above are first impression. Thanks.
> HydraBase Consensus Protocol
> ----------------------------
>
> Key: HBASE-12476
> URL: https://issues.apache.org/jira/browse/HBASE-12476
> Project: HBase
> Issue Type: Sub-task
> Components: Consensus, wal
> Reporter: Gaurav Menghani
> Assignee: Gaurav Menghani
> Attachments: 0001-HydraBase-consensus-protocol.patch
>
>
> This is the first patch for the HydraBase consensus protocol implemented
> according to the Raft consensus protocol
> (https://ramcloud.stanford.edu/raft.pdf), as advertised in (HBASE-12259)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
