[
https://issues.apache.org/jira/browse/ZOOKEEPER-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037281#comment-13037281
]
Sergey Doroshenko commented on ZOOKEEPER-784:
---------------------------------------------
Awesome to see this is finally integrated! Thanks Henry for reviewing it again
and Ketan for contributing.
@Benjamin: this change is fully backwards compatible. A client will be able to
connect to read-only server only if it (client) has 'canBeReadOnly' flag (which
is off by default) explicitly set. Old clients won't notice anything, they'll
still receive an exception saying there's no quorum. You can check out
http://wiki.apache.org/hadoop/ZooKeeper/GSoCReadOnlyMode, the design is
outlined there.
> 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
> Components: server
> Reporter: Sergey Doroshenko
> Assignee: Sergey Doroshenko
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-784.patch, ZOOKEEPER-784.patch,
> ZOOKEEPER-784.patch, ZOOKEEPER-784.patch, ZOOKEEPER-784.patch,
> ZOOKEEPER-784.patch, ZOOKEEPER-784.patch, ZOOKEEPER-784.patch,
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
