[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885349#action_12885349
 ] 

Sergey Doroshenko commented on ZOOKEEPER-784:
---------------------------------------------

I've updated the wiki page 
(http://wiki.apache.org/hadoop/ZooKeeper/GSoCReadOnlyMode) to address backwards 
compatibility, searching of r/w server during r-o mode, session handling and 
other questions, and  made it more structured overall. Soon I will also add 
some use case / recipe updated with regard to read-only mode.

Overall, the latest patch presents ready-to-use implementation of the read-only 
mode feature. It's fully backwards compatible, new server is safe to use along 
with old ones, new client is safe to use against old servers etc. 
Documentation and tests will be improved of course, but again, this patch is 
ready to use. You could try this if you're interested. Consult the wiki page 
about usage and design details.

> server-side functionality for read-only mode
> --------------------------------------------
>
>                 Key: ZOOKEEPER-784
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-784
>             Project: Zookeeper
>          Issue Type: Sub-task
>            Reporter: Sergey Doroshenko
>            Assignee: Sergey Doroshenko
>         Attachments: ZOOKEEPER-784.patch, ZOOKEEPER-784.patch, 
> ZOOKEEPER-784.patch, ZOOKEEPER-784.patch, ZOOKEEPER-784.patch
>
>
> As per http://wiki.apache.org/hadoop/ZooKeeper/GSoCReadOnlyMode , create 
> ReadOnlyZooKeeperServer which comes into play when peer is partitioned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to