[
https://issues.apache.org/jira/browse/ZOOKEEPER-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836709#comment-16836709
]
David Mollitor commented on ZOOKEEPER-3352:
-------------------------------------------
I haven't moved much on this. I spent some time looking at the issue and like
most things, the more I saw, the more I realized this would not be easy to shim
in.
However, I can imagine a situation where ZK is greatly simplified and
implemented more-or-less as Netty connectors to an LSM instance. LSMs already
have a WAL (transaction log) and have a datastore (data tree) with fast
look-ups. one of the slightly trickier parts I was looking at is that the
LSMs, from a glance, do not expose their internal TXiD, so ZK would have to be
stored its own in each record. It feels a bit dirty having to have two
different TXiDs and also finding the record with the highest TXiD at startup
would require a scan of the entire data set... that also feels wrong.
> Use LevelDB For Backend
> -----------------------
>
> Key: ZOOKEEPER-3352
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3352
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Critical
> Fix For: 4.0.0
>
>
> Use LevelDB for managing data stored in ZK (transaction logs and snapshots).
> https://stackoverflow.com/questions/6779669/does-leveldb-support-java
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
