[
https://issues.apache.org/jira/browse/ZOOKEEPER-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206482#comment-17206482
]
Hunter L commented on ZOOKEEPER-3419:
-------------------------------------
[~hanm] do you have any estimates in terms of when this will be made available
in upstream?
Some of us at LinkedIn are interested in having a similar feature/system that
supports a native backup of/recovery from fuzzy snapshots and transaction logs,
and we're trying to determine if we could leverage what might become available
in upstream ZooKeeper.
> Backup and recovery support
> ---------------------------
>
> Key: ZOOKEEPER-3419
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3419
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Affects Versions: 3.6.0
> Reporter: Michael Han
> Assignee: Michael Han
> Priority: Major
> Labels: Twitter
>
> Historically ZooKeeper has no intrinsic support for backup and restore. The
> usual approach of doing backup and restore is through customized scripts to
> copy data around, or through some 3rd party tools (exhibitor, etc), which
> introduces operation burden.
> This Jira will introduce another option: a direct support of backup and
> restore from ZooKeeper itself. It's completely built into ZooKeeper, support
> point in time recovery of an entire tree rooted after an oops event, support
> recovery partial tree for test/dev purpose, and can help replay history for
> bug investigation. It will try to provide a generic interface so the backups
> can be directed to different data storage systems (S3, Kafka, HDFS, etc).
> This same system has been in production at Twitter for X years and proved to
> be quite helpful for various use cases mentioned earlier. This will be a
> relative big patch, we'll try break the feature down and incrementally submit
> the patches when they are ready.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
