[
https://issues.apache.org/jira/browse/ZOOKEEPER-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162967#comment-13162967
]
Per Steffensen commented on ZOOKEEPER-866:
------------------------------------------
If it really true that writing to disk is as fast as not writing to disk, it
indicates to me that something could be optimized in the case where you do not
have to write to disk. I would still vote for the feature, because I simply do
not believe that it cannot be made faster when you do not have to write to disk
than when you have to write to disk. But maybe, if I need it badly enough, I
will have to make it myself. Maybe including some analysis on why it is not
faster not writing to disk than writing to disk.
But even though it cannot be made faster it would still be a nice feature,
because I believe it is important that an API allows users to indicate their
true intention - and using EPHEMERAL really indicates something else that what
you would indicate with an NON_PERSISTENT option.
But thanks for your reply.
Regards
> 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
