[
https://issues.apache.org/jira/browse/METRON-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918040#comment-16918040
]
Michael Miklavcic commented on METRON-2239:
-------------------------------------------
We probably want to distinguish between a full platform DR replication type
solution and a metron-specific backup. The Hadoop components themselves have
steps and tooling for managing those upgrades and/or migrations. I think we
should make note of them, and provide some links to the appropriate
documentation, but I don't think the Metron project should own those
integration points. Here's one such example from when we upgraded Elasticsearch
-
[https://github.com/apache/metron/pull/840/files#diff-325aea0d364d12c8637eef347ebcfca6R64]
> Metron Automated backup and restore
> -----------------------------------
>
> Key: METRON-2239
> URL: https://issues.apache.org/jira/browse/METRON-2239
> Project: Metron
> Issue Type: Improvement
> Reporter: Otto Fowler
> Priority: Blocker
>
> Metron, for upgrading to HDP 3.1 should have the ability to backup and
> restore metron specific configurations.
> For many, this upgrade will involve OS upgrade and Hadoop/HDP upgrade/Amabari
> etc.
> Such a tool would:
> Backup to file metron configurations from different locations, along with
> enough meta data on the files to restore them. The directory/backup location
> would be structured.
> * Disk on nodes
> * HDFS
> * Zookeeper
> * ??
> This backup will then be archived by the tool, and could then be saved by the
> user.
> The tool ( or a companion tool ) would be able to take these archives and
> restore them back to the cluster.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
