[
https://issues.apache.org/jira/browse/ZOOKEEPER-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han updated ZOOKEEPER-3419:
-----------------------------------
Description:
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.
was:
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.
> 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
(v7.6.3#76005)
