[
https://issues.apache.org/jira/browse/ZOOKEEPER-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906328#action_12906328
]
Thomas Koch commented on ZOOKEEPER-866:
---------------------------------------
Just 2c: I'm going to use ZK too for some middle grained locking, locking
domains a crawler is working on.
- I'd be very fine, if I could specify durability for every single create. This
way I can use the same ZK instance for fine grained locking as well as for
system configuration. Maybe another flag besides PERSISTENT | EPHEMERAL:
DURABLE?
- Actually there are more shades of grey then just durable and non durable:
It'd be possible, that not so important locks will only be flushed every few
minutes. But maybe this would make things too complicate?
> 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.
-
You can reply to this email to add a comment to the issue online.
