zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Germán Blanco (JIRA) <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-866) Adding no disk persistence option in zookeeper.
Date Wed, 06 Nov 2013 06:10:19 GMT

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

Germán Blanco commented on ZOOKEEPER-866:
-----------------------------------------

I wouldn't recommend to run zookeeper using ramdisk without having an additional method that
ensures consistency. Ramdisk means data is not persistent after a reboot, and this JIRA shows
that losing data in one node when the quorum was in minority may lead to permanent inconsistencies
in the quorum.

> 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.5.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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message