Snapshotting and Restore in Ignite

[aravind s <su...@gmail.com>]

Hi,

When using Ignite as a persistence store is there a way to snapshot and
restore from one cluster to the other?

Ignite as a database is there any data loss when one of the nodes in
baseline topology goes down. Is there an ideal recommendation for a number
of replicas a table should run if it has to run as persistence store.

Regards,
Aravind S

Re: Snapshotting and Restore in Ignite

[Gaurav Bajaj <ga...@gmail.com>]

Hello,

If cache backups are zero, ofcourse there will be data loss when node is
removed from BLT.

Number of replicas (assuming you mean number of backups) depends upon how
resilient you want your cluster to be but ofcourse having more replicas can
affect cache write performance.

Best,
Gaurav

On Wed 14 Nov, 2018, 10:37 AM aravind s, <su...@gmail.com> wrote:

> Hi,
>
> When using Ignite as a persistence store is there a way to snapshot and
> restore from one cluster to the other?
>
> Ignite as a database is there any data loss when one of the nodes in
> baseline topology goes down. Is there an ideal recommendation for a number
> of replicas a table should run if it has to run as persistence store.
>
> Regards,
> Aravind S
>

Re: Snapshotting and Restore in Ignite

[Dave Harvey <dh...@jobcase.com>]

Gridgain has some kind of snapshoting add in.

You can save and restore the workDirectory from each node when the cluster
is in a stable state, provided that you use the same CONSISTENT_ID when
restoring.  We were able to convert the directory name back into a
consistent ID on restore, but we had to hack around "-".   If you a careful
about your original consistent_id, then the directory name will be the same
as the consistent id.
but
We have a prototype running that creates cross-node coherent LVM snapshots
on a running cluster by hooking into the topology discovery process, and
taking the snapshot on each node when transactions are frozen, but it is
not quite ready to share.
(Our earlier prototype failed because if we used and LINUX fsfreeze and
then tried to do an LVM snapshot in that state, the snapshot deadlocked.
 We were never able to understand how an FS level operation holds locks
that are needed for a volume level operation. )

Note: You can control where the persistent data is stored.

        <property name="workDirectory" value=
"#{systemEnvironment['IGNITE_PERSISTENT_STORE']}/work"/>


        <!-- Enabling Apache Ignite native persistence.

             Details
https://apacheignite.readme.io/docs/distributed-persistent-store.

          -->

        <property name="dataStorageConfiguration">

            <bean class=
"org.apache.ignite.configuration.DataStorageConfiguration">

                <property name="defaultDataRegionConfiguration">

                    <bean class=
"org.apache.ignite.configuration.DataRegionConfiguration">

  ....

                </property>



  ...



                <!-- Path to the root directory where the Persistent Store
will persist data and indexes.

                  -->

                <property name="storagePath" value=
"#{systemEnvironment['IGNITE_PERSISTENT_STORE']}/store"/>



                <!-- <property name="storagePath" value="/opt/jobcase/db"/>
-->



                <!-- Sets a path to the directory where WAL is stored. -->


                <property name="walPath" value=
"#{systemEnvironment['IGNITE_PERSISTENT_STORE']}/wal"/>



                <!-- Sets a path for the WAL archive directory.

                     Every WAL segment will be fully copied to this
directory

                     before it can be reused for WAL purposes. -->


                <property name="walArchivePath" value=
"#{systemEnvironment['IGNITE_PERSISTENT_STORE']}/wal/archive"/>

            </bean>

       </property>

On Wed, Nov 14, 2018 at 9:32 AM ilya.kasnacheev <il...@gmail.com>
wrote:

> Hello!
>
> Currently there is no snapshotting in Apache Ignite. You could restore a
> different cluster from shutdown nodes' persistence directories but not from
> live nodes'.
>
> There are third party commercial implementations of snapshotting for
> Ignite.
>
> Regards,
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

Re: Snapshotting and Restore in Ignite

["ilya.kasnacheev" <il...@gmail.com>]

Hello!

Currently there is no snapshotting in Apache Ignite. You could restore a
different cluster from shutdown nodes' persistence directories but not from
live nodes'.

There are third party commercial implementations of snapshotting for Ignite.

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/