[
https://issues.apache.org/jira/browse/ZOOKEEPER-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Doroshenko updated ZOOKEEPER-784:
----------------------------------------
Attachment: ZOOKEEPER-784.patch
* As per Henry's suggestion, updated QuorumePeer to wait some time before
starting RO server (currently it's 1 tickTime)
* About watches: no, setting watches doesn't turn operation to a write
operation.
If a client is connected to a partitioned server and sets a watch in r/o mode,
and meanwhile data is changed in the majority part, the watch will be triggered
when the client reconnects to the majority. This is consistent with the current
behavior, that is, if a watch is set before partitioning, it's triggered upon
rejoining if there's any change
* Added a test to ensure read operations succeed in r/o mode and write
operations fail.
Created QuorumUtil class which encapsulates quorum testing logic, e.g. allows
to start/shutdown all peers or particular ones. It's used in the new test for
r/o mode. I will refactor QuorumBase to be a special case of QuorumUtil.
What I'll do next is update wiki page to address Patrick's comments and make
r/o client to seek for r/w server (currently if client's connected to a r/o
server it doesn't try to find another server).
> 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
>
>
> 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.
