[
https://issues.apache.org/jira/browse/IGNITE-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Pavlov updated IGNITE-13805:
-----------------------------------
Labels: iep-43 important ise (was: iep-43 important)
> Add support for cache group restore from a snapshot on the same topology
> ------------------------------------------------------------------------
>
> Key: IGNITE-13805
> URL: https://issues.apache.org/jira/browse/IGNITE-13805
> Project: Ignite
> Issue Type: New Feature
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: iep-43, important, ise
> Fix For: 2.11
>
> Time Spent: 12h 50m
> Remaining Estimate: 0h
>
> Ignite 2.9 introduces a new feature to take [consistent cluster
> snapshot|https://ignite.apache.org/docs/latest/persistence/snapshots].
> However, there is currently no way for the user to restore a separate cache
> group from such a snapshot.
> As a first step, we must provide the ability (CLI command and public API) to
> restore the separate cache group(s) without considering the current partition
> distribution and rely on rebalancing to achieve the ideal distribution.
> This process consists of the following steps:
> # Make sure that all partitions of the cache group are available in the
> cluster and that there are no conflicts in the saved cache configurations.
> # Make sure the target cache group does not exist (user must manually
> destroy the cache before restoring)..
> # Move the cache data files locally on each node with the cache data
> snapshots.
> # Merge the binary metadata from the snapshot on each node.
> # Dynamically start the restored cache group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
