[
https://issues.apache.org/jira/browse/ZOOKEEPER-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293619#comment-13293619
]
Matthew Krenzer commented on ZOOKEEPER-866:
-------------------------------------------
I'd like to second the request for this feature for another reason. We have a
large set of simulations and tests where zookeeper is a small but important
part. We use a server instance embedded in the tests where necessary and we
want to be able to run many of these tests on the same box at the same time.
Currently we have to muck about creating unique directories for each instance
of each test to ensure there are no conflicts and do a bunch of work to clean
up all the droppings regardless of how the tests exit. It's a minor hassle,
but it would be really nice if we could configure zookeeper to not need any of
those files.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
