[ https://issues.apache.org/jira/browse/ZOOKEEPER-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873003#action_12873003 ]
Sergey Doroshenko commented on ZOOKEEPER-704: --------------------------------------------- I have updated wiki page to describe new (quite simple and elegant) approach of implementing server-side part of the read-only mode. Already discussed this with Henry yesterday. Take a look if you're interested in the details, and lmk if you have some thoughts about this. > GSoC 2010: Read-Only Mode > ------------------------- > > Key: ZOOKEEPER-704 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-704 > Project: Zookeeper > Issue Type: Wish > Reporter: Henry Robinson > > Read-only mode > Possible Mentor > Henry Robinson (henry at apache dot org) > Requirements > Java and TCP/IP networking > Description > When a ZooKeeper server loses contact with over half of the other servers in > an ensemble ('loses a quorum'), it stops responding to client requests > because it cannot guarantee that writes will get processed correctly. For > some applications, it would be beneficial if a server still responded to read > requests when the quorum is lost, but caused an error condition when a write > request was attempted. > This project would implement a 'read-only' mode for ZooKeeper servers (maybe > only for Observers) that allowed read requests to be served as long as the > client can contact a server. > This is a great project for getting really hands-on with the internals of > ZooKeeper - you must be comfortable with Java and networking otherwise you'll > have a hard time coming up to speed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.