[
https://issues.apache.org/jira/browse/IGNITE-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Boudnik updated IGNITE-3457:
--------------------------------------
Description:
h2. Purpose
To address missing features, such as backup/restore, snapshot, replication, and
continues export.
h2. How it works
All changes made to data in cache are passed to associated Active Store where
they stored in:
* Transaction Log, which contains the all history of changes made
* Snapshot - the instance of Key-Value store, which contains changes made since
last merge with Main Key-Value store
* Main Key-Value Store, which contains up-to-date copy of cache's data
Since cache has been backed by persistent store it should be configured with
*read-through* and *write-through* modes. To represent deleted key the special
constant *NAUGHT* stored as value together with that key.
!Data Flow.png!
h3. New snapshot
At any time a new snapshot can be created and all changes will be stored in it.
Previous snapshot stays in read-only mode.
h3. Rollback
To rollback cache to the state when new snapshot was created, all keys in
snapshot should be invalidated in cache. Then snapshot deactivated.
h3. Roll forward
After rolling back the snapshot, all transaction from log could be filtered and
re-executed.
h3. Merge
Either periodically or by explicitly, content of Snapshot merged into Main. To
do so and do not interrupt normal cache operation, Active Store creates a new
snapshot, start storing changes into it, and copies the content of previous
snapshot to the main. After that the previous snapshot could be either kept or
reclaimed.
was:
To address missing features, such as backup/restore, snapshot, replication, and
continues export
> Active Store
> ------------
>
> Key: IGNITE-3457
> URL: https://issues.apache.org/jira/browse/IGNITE-3457
> Project: Ignite
> Issue Type: New Feature
> Components: general
> Reporter: Alexandre Boudnik
> Assignee: Alexandre Boudnik
> Attachments: Data Flow.png
>
>
> h2. Purpose
> To address missing features, such as backup/restore, snapshot, replication,
> and continues export.
> h2. How it works
> All changes made to data in cache are passed to associated Active Store where
> they stored in:
> * Transaction Log, which contains the all history of changes made
> * Snapshot - the instance of Key-Value store, which contains changes made
> since last merge with Main Key-Value store
> * Main Key-Value Store, which contains up-to-date copy of cache's data
> Since cache has been backed by persistent store it should be configured with
> *read-through* and *write-through* modes. To represent deleted key the
> special constant *NAUGHT* stored as value together with that key.
> !Data Flow.png!
> h3. New snapshot
> At any time a new snapshot can be created and all changes will be stored in
> it. Previous snapshot stays in read-only mode.
> h3. Rollback
> To rollback cache to the state when new snapshot was created, all keys in
> snapshot should be invalidated in cache. Then snapshot deactivated.
> h3. Roll forward
> After rolling back the snapshot, all transaction from log could be filtered
> and re-executed.
> h3. Merge
> Either periodically or by explicitly, content of Snapshot merged into Main.
> To do so and do not interrupt normal cache operation, Active Store creates a
> new snapshot, start storing changes into it, and copies the content of
> previous snapshot to the main. After that the previous snapshot could be
> either kept or reclaimed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
