[jira] [Commented] (IGNITE-11073) Persistence cache snapshot
[ https://issues.apache.org/jira/browse/IGNITE-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097255#comment-17097255 ] Maxim Muzafarov commented on IGNITE-11073: -- [~alex_pl] [~agoncharuk] Folks, thank you for the review. Request remote partitions excluded from PR. Merged to the master branch. > Persistence cache snapshot > -- > > Key: IGNITE-11073 > URL: https://issues.apache.org/jira/browse/IGNITE-11073 > Project: Ignite > Issue Type: New Feature >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: iep-28, iep-43 > Fix For: 2.9 > > Time Spent: 52h 20m > Remaining Estimate: 0h > > *Snapshot requirements* > # Users must have the ability to create a snapshot of persisted user data > (in-memory is out of the scope). > # Users must have the ability to create a snapshot from the cluster under the > load without cluster deactivation. > # The snapshot process must not block for a long time any of the user > transactions (short-time blocks are acceptable). > # The snapshot process must allow creating a data snapshot on each node and > transfer it to any of the remote nodes for internal cluster needs. > # The created snapshot at the cluster-level must be fully consistent from > cluster-wide terms, there should not be any incomplete transactions inside. > # The snapshot of each node must be consistent – cache partitions, binary > meta, etc. must not have unnecessary changes. > *The following API must be available:* > # [public] Java API > # [public] JMX MBean > # [internal] File Transmission -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11073) Persistence cache snapshot
[
https://issues.apache.org/jira/browse/IGNITE-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096407#comment-17096407
]
Ignite TC Bot commented on IGNITE-11073:
{panel:title=Branch: [pull/7760/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5272003buildTypeId=IgniteTests24Java8_RunAll]
> Persistence cache snapshot
> --
>
> Key: IGNITE-11073
> URL: https://issues.apache.org/jira/browse/IGNITE-11073
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: iep-28, iep-43
> Fix For: 2.9
>
> Time Spent: 52h 20m
> Remaining Estimate: 0h
>
> *Snapshot requirements*
> # Users must have the ability to create a snapshot of persisted user data
> (in-memory is out of the scope).
> # Users must have the ability to create a snapshot from the cluster under the
> load without cluster deactivation.
> # The snapshot process must not block for a long time any of the user
> transactions (short-time blocks are acceptable).
> # The snapshot process must allow creating a data snapshot on each node and
> transfer it to any of the remote nodes for internal cluster needs.
> # The created snapshot at the cluster-level must be fully consistent from
> cluster-wide terms, there should not be any incomplete transactions inside.
> # The snapshot of each node must be consistent – cache partitions, binary
> meta, etc. must not have unnecessary changes.
> *The following API must be available:*
> # [public] Java API
> # [public] JMX MBean
> # [internal] File Transmission
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11073) Persistence cache snapshot
[
https://issues.apache.org/jira/browse/IGNITE-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087201#comment-17087201
]
Ignite TC Bot commented on IGNITE-11073:
{panel:title=Branch: [pull/7607/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5237899buildTypeId=IgniteTests24Java8_RunAll]
> Persistence cache snapshot
> --
>
> Key: IGNITE-11073
> URL: https://issues.apache.org/jira/browse/IGNITE-11073
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: iep-28, iep-43
> Fix For: 2.9
>
> Time Spent: 47h 50m
> Remaining Estimate: 0h
>
> *Snapshot requirements*
> # Users must have the ability to create a snapshot of persisted user data
> (in-memory is out of the scope).
> # Users must have the ability to create a snapshot from the cluster under the
> load without cluster deactivation.
> # The snapshot process must not block for a long time any of the user
> transactions (short-time blocks are acceptable).
> # The snapshot process must allow creating a data snapshot on each node and
> transfer it to any of the remote nodes for internal cluster needs.
> # The created snapshot at the cluster-level must be fully consistent from
> cluster-wide terms, there should not be any incomplete transactions inside.
> # The snapshot of each node must be consistent – cache partitions, binary
> meta, etc. must not have unnecessary changes.
> *The following API must be available:*
> # [public] Java API
> # [public] JMX MBean
> # [internal] File Transmission
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11073) Persistence cache snapshot
[ https://issues.apache.org/jira/browse/IGNITE-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085855#comment-17085855 ] Maxim Muzafarov commented on IGNITE-11073: -- [~alex_pl] Thank you for the great review! [~agoncharuk], [~ivan.glukos] Will you look at these changes? > Persistence cache snapshot > -- > > Key: IGNITE-11073 > URL: https://issues.apache.org/jira/browse/IGNITE-11073 > Project: Ignite > Issue Type: New Feature >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: iep-28, iep-43 > Fix For: 2.9 > > Time Spent: 47h 50m > Remaining Estimate: 0h > > *Snapshot requirements* > # Users must have the ability to create a snapshot of persisted user data > (in-memory is out of the scope). > # Users must have the ability to create a snapshot from the cluster under the > load without cluster deactivation. > # The snapshot process must not block for a long time any of the user > transactions (short-time blocks are acceptable). > # The snapshot process must allow creating a data snapshot on each node and > transfer it to any of the remote nodes for internal cluster needs. > # The created snapshot at the cluster-level must be fully consistent from > cluster-wide terms, there should not be any incomplete transactions inside. > # The snapshot of each node must be consistent – cache partitions, binary > meta, etc. must not have unnecessary changes. > *The following API must be available:* > # [public] Java API > # [public] JMX MBean > # [internal] File Transmission -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11073) Persistence cache snapshot
[ https://issues.apache.org/jira/browse/IGNITE-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085837#comment-17085837 ] Aleksey Plekhanov commented on IGNITE-11073: [~mmuzaf], I've reviewed your patch, it looks good to me. But I think it's better to exclude remote partitions request related part from this PR and merge it later, with P2P rebalance. > Persistence cache snapshot > -- > > Key: IGNITE-11073 > URL: https://issues.apache.org/jira/browse/IGNITE-11073 > Project: Ignite > Issue Type: New Feature >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: iep-28, iep-43 > Fix For: 2.9 > > Time Spent: 47h 50m > Remaining Estimate: 0h > > *Snapshot requirements* > # Users must have the ability to create a snapshot of persisted user data > (in-memory is out of the scope). > # Users must have the ability to create a snapshot from the cluster under the > load without cluster deactivation. > # The snapshot process must not block for a long time any of the user > transactions (short-time blocks are acceptable). > # The snapshot process must allow creating a data snapshot on each node and > transfer it to any of the remote nodes for internal cluster needs. > # The created snapshot at the cluster-level must be fully consistent from > cluster-wide terms, there should not be any incomplete transactions inside. > # The snapshot of each node must be consistent – cache partitions, binary > meta, etc. must not have unnecessary changes. > *The following API must be available:* > # [public] Java API > # [public] JMX MBean > # [internal] File Transmission -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11073) Persistence cache snapshot
[
https://issues.apache.org/jira/browse/IGNITE-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077496#comment-17077496
]
Ignite TC Bot commented on IGNITE-11073:
{panel:title=Branch: [pull/7607/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5199634buildTypeId=IgniteTests24Java8_RunAll]
> Persistence cache snapshot
> --
>
> Key: IGNITE-11073
> URL: https://issues.apache.org/jira/browse/IGNITE-11073
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: iep-28, iep-43
> Fix For: 2.9
>
> Time Spent: 31h 10m
> Remaining Estimate: 0h
>
> *Snapshot requirements*
> # Users must have the ability to create a snapshot of persisted user data
> (in-memory is out of the scope).
> # Users must have the ability to create a snapshot from the cluster under the
> load without cluster deactivation.
> # The snapshot process must not block for a long time any of the user
> transactions (short-time blocks are acceptable).
> # The snapshot process must allow creating a data snapshot on each node and
> transfer it to any of the remote nodes for internal cluster needs.
> # The created snapshot at the cluster-level must be fully consistent from
> cluster-wide terms, there should not be any incomplete transactions inside.
> # The snapshot of each node must be consistent – cache partitions, binary
> meta, etc. must not have unnecessary changes.
> *The following API must be available:*
> # [public] Java API
> # [public] JMX MBean
> # [internal] File Transmission
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
