[
https://issues.apache.org/jira/browse/ZOOKEEPER-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877343#comment-15877343
]
ASF GitHub Bot commented on ZOOKEEPER-2700:
-------------------------------------------
Github user flier commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/180#discussion_r102372975
--- Diff: src/java/main/org/apache/zookeeper/server/ZooKeeperServer.java ---
@@ -303,15 +305,38 @@ public void loadData() throws IOException,
InterruptedException {
public void takeSnapshot(){
--- End diff --
@hanm Thanks for your advice :)
We are using a similar structure as `2.2 Alternative 2 – Learners` in the
paper, it is good enough for most of online scenes. I don't think it is worthy
to introduce another layer because we give up the write operation to all
observers, just use it as a read only view.
For the remote replication, I doubt it also blocked by packet loss rate
like Observer. On the other hand, we have an internal project named `zkpipe`,
it read Zookeeper snapshot/binlog and send it to a Kafka topic, our client
could choose to rebuild the transaction or subscribe the changes. I believe it
will better than hack Zookeeper itself. If you have interested, I could push it
to github later.
> Force ZooKeeper to generate snapshot
> ------------------------------------
>
> Key: ZOOKEEPER-2700
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2700
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Flier Lu
> Priority: Minor
>
> When cold backup or remote offline sync Zookeeper instances, we need the
> latest snapshot.
> Add a four letter `snap` command to force Zookeeper to generate snapshot.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
