[ https://issues.apache.org/jira/browse/ZOOKEEPER-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-866: ------------------------------------ Attachment: ZOOKEEPER-nodisk.patch Here is a patch that I had worked on. This is not a complete patch since this actually changes the code and doesnt make it configurable option. I will be creating another patch wherein there is a configuration option for this. Feedback is welcome. > 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.