[
https://issues.apache.org/jira/browse/IGNITE-17613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-17613:
------------------------------------
Description:
Incremental snapshot is a lightweight alternative to full snapshot. It bases on
the non-blocking Consistent Cut algorithm and provides a collection of WAL
segments that hold logical changes since previous snapshot (full or
incremental).
Incremental snapshot should contain:
* compacted WAL segments
* meta file with Consistent Cut to restore on
* binary_meta if it has changed since previous snapshot.
Incremental snapshot is stored within full snapshot directory.
Incremental snapshot before creation checks:
* Base snapshot (at least its metafile) exists. Exists metafile for all
incremental snapshots.
* Validate that no misses in WAL segments since previous snapshot.
* Check that new _ConsistentCutVersion_ is greater than version of previous
snapshots.
* Check that baseline topology and cacheGroups are the same (relatively to
base snapshot).
More info in IEP:
[https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884314]
was:
Incremental snapshot is a lightweight alternative to full snapshot. It bases on
the non-blocking Consistent Cut algorithm and provides a collection of WAL
segments that hold logical changes since previous snapshot (full or
incremental).
Incremental snapshot should contain:
* compacted WAL segments
* meta file with Consistent Cut to restore on
* binary_meta if it has changed since previous snapshot.
Incremental snapshot is stored within full snapshot directory.
Incremental snapshot before creation checks:
* Base snapshot (at least its metafile) exists. Exists metafile for all
incremental snapshots.
* Validate that no misses in WAL segments since previous snapshot.
* Check that new _ConsistentCutVersion_ is greater than version of previous
snapshots.
* Check that baseline topology and cacheGroups are the same (relatively to
base snapshot).
More info:
[https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884314]
> Create incremental snapshot
> ---------------------------
>
> Key: IGNITE-17613
> URL: https://issues.apache.org/jira/browse/IGNITE-17613
> Project: Ignite
> Issue Type: New Feature
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: IEP-89, ise
>
> Incremental snapshot is a lightweight alternative to full snapshot. It bases
> on the non-blocking Consistent Cut algorithm and provides a collection of WAL
> segments that hold logical changes since previous snapshot (full or
> incremental).
> Incremental snapshot should contain:
> * compacted WAL segments
> * meta file with Consistent Cut to restore on
> * binary_meta if it has changed since previous snapshot.
> Incremental snapshot is stored within full snapshot directory.
> Incremental snapshot before creation checks:
> * Base snapshot (at least its metafile) exists. Exists metafile for all
> incremental snapshots.
> * Validate that no misses in WAL segments since previous snapshot.
> * Check that new _ConsistentCutVersion_ is greater than version of previous
> snapshots.
> * Check that baseline topology and cacheGroups are the same (relatively to
> base snapshot).
> More info in IEP:
> [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884314]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
