[
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
Patch includes ReadOnlyZooKeeperServer and ReadOnlyReqestProcessor.
This patch outlines the general idea: read-only server is spawned when peer
becomes partitioned, and is able to serve read-only requests but drops
state-changing ones.
It's by no means a final version, however it's already possible to connect to a
partitioned peer (or remain connected to it when it loses a quorum) and make
read requests (write requests are dropped with explanation message).
Next things to work on are:
* session handling during partition. For now ReadOnlyServer creates
SessionTrackerImpl and it's ok for manual tests, but that's just to make this
proof-of-concept patch work
* distinguish read-only clients and usual ones (depends on yet non-existent
ticket about creation of read-only client), accept only read-onlies
* create test cases, make all current ones pass
> 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
>
>
> 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.
