[
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
Hey Flavio, thanks for reviewing!
Re your comments:
1. added warn messages both to server- and client-side
2. done
3. done
4. r-o server gets killed in "finally" block of LOOKING case of QuorumPeer#run
(QuorumPeer#645 in the latest patch). Interesting thing is, it may actually
won't have started by the time shutdown is called (if peer regains the quorum
during the grace period), but #shutdown is called in any case
> 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
>
>
> 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.
