You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "aaron@tophold.com" <aa...@tophold.com> on 2017/11/02 07:03:50 UTC
Some concern regards the DataRegionConfiguration of the 2.3
hi All,
We are upgrading to the 2.3, so as recommend we should use the DataRegionConfiguration instead of the old memory configuration.
if we set the persistenceEnabled to true; but meaning-while the cache we set the cacheStoreFactory. should we only keep one of them? otherwise they will conflict.
Regards
Aaron
aaron@tophold.com
Re: Re: Some concern regards the DataRegionConfiguration of the 2.3
Posted by Alexey Kukushkin <ku...@gmail.com>.
Apache Ignite has no data migration/archiving tool but Ignite supports
plugins and Ignite native persistence exposes
org.apache.ignite.internal.processors.cache.persistence.snapshot.IgniteCacheSnapshotManager
that you could use to implement your own tool.
There are commercial solutions available, for example, this one
<https://docs.gridgain.com/docs/data-snapshots>.
Re: Re: Some concern regards the DataRegionConfiguration of the 2.3
Posted by "aaron@tophold.com" <aa...@tophold.com>.
one more question; compare with DB, is there any tools like migrate, purge and archive data tools?
or we have to implement it in our application code?
Regards
Aaron
aaron@tophold.com
From: aaron@tophold.com
Date: 2017-11-02 18:02
To: user
Subject: Re: Re: Some concern regards the DataRegionConfiguration of the 2.3
Got thanks Alexey!
Regards
Aaron
aaron@tophold.com
From: Alexey Kukushkin
Date: 2017-11-02 17:43
To: user
Subject: Re: Some concern regards the DataRegionConfiguration of the 2.3
Hi,
When you said "old memory configuration" did you mean using cacheStoreFactory?
Ignite has two persistence options: native and 3rd-party persistence and having cacheStoreFactory configured means you use the latter one.
Unlike Ignite native persistence, the 3rd party persistence is slower in most cases, not transparent to SQL, requires explicit initial data load and the associated storage might become a performance or availability issue. But 3rd party persistence allows you to plug Ignite into your existing system between the application and database layers, protecting your investment into other apps using the same database.
You can keep using 3rd-party persistence with Ignite 2.3. You might evaluate if you want to migrate to native persistence. Do not use both.
Re: Re: Some concern regards the DataRegionConfiguration of the 2.3
Posted by "aaron@tophold.com" <aa...@tophold.com>.
Got thanks Alexey!
Regards
Aaron
aaron@tophold.com
From: Alexey Kukushkin
Date: 2017-11-02 17:43
To: user
Subject: Re: Some concern regards the DataRegionConfiguration of the 2.3
Hi,
When you said "old memory configuration" did you mean using cacheStoreFactory?
Ignite has two persistence options: native and 3rd-party persistence and having cacheStoreFactory configured means you use the latter one.
Unlike Ignite native persistence, the 3rd party persistence is slower in most cases, not transparent to SQL, requires explicit initial data load and the associated storage might become a performance or availability issue. But 3rd party persistence allows you to plug Ignite into your existing system between the application and database layers, protecting your investment into other apps using the same database.
You can keep using 3rd-party persistence with Ignite 2.3. You might evaluate if you want to migrate to native persistence. Do not use both.
Re: Some concern regards the DataRegionConfiguration of the 2.3
Posted by Alexey Kukushkin <ku...@gmail.com>.
Hi,
When you said "old memory configuration" did you mean using
cacheStoreFactory?
Ignite has two persistence options: native and 3rd-party persistence and
having cacheStoreFactory configured means you use the latter one.
Unlike Ignite native persistence, the 3rd party persistence is slower in
most cases, not transparent to SQL, requires explicit initial data load and
the associated storage might become a performance or availability issue.
But 3rd party persistence allows you to plug Ignite into your existing
system between the application and database layers, protecting your
investment into other apps using the same database.
You can keep using 3rd-party persistence with Ignite 2.3. You might
evaluate if you want to migrate to native persistence. Do not use both.