You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (Updated) (JIRA)" <ji...@apache.org> on 2011/11/19 02:18:53 UTC

[jira] [Updated] (ZOOKEEPER-546) add "diskless" ensemble support

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-546:
-----------------------------------

    Fix Version/s:     (was: 3.4.0)
    
> add "diskless" ensemble support
> -------------------------------
>
>                 Key: ZOOKEEPER-546
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-546
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Patrick Hunt
>
> In some cases there is no need to have the ZK data persisted to disk. For example if all you are doing is group membership and leadership
> election the data is totally ephemeral, storing on disk is unnecessary. We've also seen cases where any non-ephemeral data can be
> easily recovered (say configuration data that's generated/read and loaded into zk) and there is less need to worry about recovery of the
> data in the case of catastrophic failure (meaning _all_ replicas are lost, remember, recovery is automatic if 2n+1 servers and <= n servers
> fail, even if > n fail manual recovery is still possible as long as at least 1 replica, or replica backup can be recovered)
> In these cases it makes sense to have a "diskless" zookeeper ensemble. The result should be improved write performance
> an less moving parts (no disk to fail!), simplifiying ops in cases where this can be applied.

--
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