You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "maoling (JIRA)" <ji...@apache.org> on 2019/03/26 08:12:00 UTC
[jira] [Updated] (ZOOKEEPER-3318) Add a complete backup mechanism
for zookeeper internal
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
maoling updated ZOOKEEPER-3318:
-------------------------------
Description:
we already had some workaround ways for the backup, e.g
scenario 1: just write a cron shell to copy the snapshots periodically.
scenario 2: use the observer as the role of backup, then write the snapshots to file system. (e.g HDFS)
this issue is aiming to implement a complete backup mechanism for zookeeper internal:
the init propose:
1. write a new CLI:snapshot
1.1 because this CLI may be time-consuming.A confirmation is needed. e.g.
[zk: 127.0.0.1:2180(CONNECTED) 0] snapshot backupDataDir
Are you sure to exec:snapshot [yes/no]
1.2 if no parameter, the default backupDataDir is the dataDir. the format of the backup-snapshot is just like: backup_snapshot.f9f800002834 with the "backup_" prefix,when recovering, rename backup_snapshot.f9f800002834 to snapshot.f9f800002834 and move it to the dataDir, then restart the ensemble.
1.3 will not expose the takeSnap() api to the client.
2. write a new tool/shell: zkBackup.sh which is the reverse proces of the zkCleanup.sh
> Add a complete backup mechanism for zookeeper internal
> ------------------------------------------------------
>
> Key: ZOOKEEPER-3318
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3318
> Project: ZooKeeper
> Issue Type: New Feature
> Components: other
> Reporter: maoling
> Assignee: maoling
> Priority: Major
>
> we already had some workaround ways for the backup, e.g
> scenario 1: just write a cron shell to copy the snapshots periodically.
> scenario 2: use the observer as the role of backup, then write the snapshots to file system. (e.g HDFS)
> this issue is aiming to implement a complete backup mechanism for zookeeper internal:
> the init propose:
> 1. write a new CLI:snapshot
> 1.1 because this CLI may be time-consuming.A confirmation is needed. e.g.
> [zk: 127.0.0.1:2180(CONNECTED) 0] snapshot backupDataDir
> Are you sure to exec:snapshot [yes/no]
> 1.2 if no parameter, the default backupDataDir is the dataDir. the format of the backup-snapshot is just like: backup_snapshot.f9f800002834 with the "backup_" prefix,when recovering, rename backup_snapshot.f9f800002834 to snapshot.f9f800002834 and move it to the dataDir, then restart the ensemble.
> 1.3 will not expose the takeSnap() api to the client.
> 2. write a new tool/shell: zkBackup.sh which is the reverse proces of the zkCleanup.sh
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)