[
https://issues.apache.org/jira/browse/ZOOKEEPER-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010096#comment-13010096
]
Jürgen Schumacher commented on ZOOKEEPER-866:
---------------------------------------------
Hi, I tried this patch with our application with Zokkeeper 3.3.3, because we do
not care for persistence of data after complete system restarts but we need
reliablity if only single Zookeeper servers crash and restart later. Is it
correct that with this path the Zookeeper ensemble loses all currently stored
data when just the leader server crashes or is killed (our test ensemble
consists of 5 nodes)? I would have expected that each follower has the complete
current data in memory and can continue to work on it, when it becomes the new
leader. Or is this assumption wrong? Thanks.
> Adding no disk persistence option in zookeeper.
> -----------------------------------------------
>
> Key: ZOOKEEPER-866
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-866
> Project: ZooKeeper
> Issue Type: New Feature
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-nodisk.patch
>
>
> Its been seen that some folks would like to use zookeeper for very fine
> grained locking. Also, in there use case they are fine with loosing all old
> zookeeper state if they reboot zookeeper or zookeeper goes down. The use case
> is more of a runtime locking wherein forgetting the state of locks is
> acceptable in case of a zookeeper reboot. Not logging to disk allows high
> throughput on and low latency on the writes to zookeeper. This would be a
> configuration option to set (ofcourse the default would be logging to disk).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
