RE: Read Through and WriteThrough and Native Persistence + Ignite .NET

Through and WriteThrough and Native Persistence + Ignite .NET CAUTION: This email originated from outside our organisation - ptupit...@apache.org<mailto:ptupit...@apache.org> Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is sa

Re: Read Through and WriteThrough and Native Persistence + Ignite .NET

Hi Satyajit, Have you tried it? I'm not sure how a combination of CacheStore + native persistence works. On Thu, Sep 7, 2023 at 2:42 PM wrote: > Hi Pavel > > > > Can we do a setting where we enable Native Persistence as well > as ( ReadThrough = true and Wr

Read Through and WriteThrough and Native Persistence + Ignite .NET

Hi Pavel Can we do a setting where we enable Native Persistence as well as ( ReadThrough = true and WriteThrough = true) and save data in disk as well as in External cachestore. And after cache restart we don't do initial loading from external cache store

Native persistence support for TextQuery

Hi all! I have a great question from the Apache Ignite Twitter page ( follow us! :) ), https://twitter.com/techie_das/status/1476461300154703875 Are there plans to include native persistence support for TextQuery in Ignite? I'm sure Suman will appreciate some assistance with this :)

Re: Enable Native persistence only for one node of the cluster

er to hold baseline topology/metastore data between restarts. Regards, -- Ilya Kasnacheev пн, 14 июн. 2021 г. в 15:45, Krish : > Is it possible to have a cluster topology where native persistence is > enabled > only for one node and all other nodes use in-memory cache store *without &g

Re[2]: Enable Native persistence only for one node of the cluster

d on which service can create actual compute >tasks) and store it in the cache store. Service will query the cache-store >to find the next set of valid tasks based on priority and locking. > >We need native persistence because even if the cluster goes down, it should >not lose the t

Re: Enable Native persistence only for one node of the cluster

take care of priority and locking. All clients > will create a cache object(based on which service can create actual compute > tasks) and store it in the cache store. Service will query the cache-store > to find the next set of valid tasks based on priority and locking. > > We need na

Re: Enable Native persistence only for one node of the cluster

based on priority and locking. We need native persistence because even if the cluster goes down, it should not lose the tasks that were sent by the clients. And only ignite service will be dealing with these task objects, we are thinking of enabling it only for the cluster node on which our ignite

Re: Enable Native persistence only for one node of the cluster

Yes, but why? What’s the use case? (Server nodes in your baseline topology will use the persistent store. Other nodes will be memory-only.) > On 14 Jun 2021, at 13:45, Krish wrote: > > Is it possible to have a cluster topology where native persistence is enabled > only for one

Re: Enable Native persistence only for one node of the cluster

As long as you only have persistent caches on the persistent nodes it should be fine, you cannot have a persistent cache on a non persistent node as far as I am aware of. On 2021-06-14 14:45, Krish wrote: Is it possible to have a cluster topology where native persistence is enabled only

Enable Native persistence only for one node of the cluster

Is it possible to have a cluster topology where native persistence is enabled only for one node and all other nodes use in-memory cache store *without *native persistence? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Native Persistence Tuning - Percentage kept in RAM

We encountered the same issue with a small data region (64Mb in our case). If I recall correctly the failure was due to the checkpointing mechanism not having enough pages to perform a checkpoint, rather than a critical failure on a Put(). Adding more memory increases the number of pages (or you

Re: Native Persistence Tuning - Percentage kept in RAM

Your data region is too small. Ignite is an in-memory data grid, it’s not really designed to work with as little as 40Mb of memory. When I tried it on my machine, I get the following message: [17:42:09,246][SEVERE][checkpoint-runner-cpu-#80][] JVM will be halted immediately due to the failure:

Re: Native Persistence Tuning - Percentage kept in RAM

Hi I tried setting the MaxSize on a cache to a low number (40Mb) and it quickly ran in to an IgniteOutOfMemoryException, despite the fact there was plenty of space on disk. Why would it run out of RAM if it can persist data above the MaxSize the excess to disk? -- Sent from:

Re: Native Persistence Tuning - Percentage kept in RAM

That’s how you do what you’re asking. MaxSize is the maximum size of the off-heap memory used. > On 2 Jun 2021, at 16:34, gigabot wrote: > > Hi Stephen, I know how to configure separate data regions, but how do I > configure what % of each is in RAM vs disk? > > > > -- > Sent from:

Re: Native Persistence Tuning - Percentage kept in RAM

Hi Stephen, I know how to configure separate data regions, but how do I configure what % of each is in RAM vs disk? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Native Persistence Tuning - Percentage kept in RAM

Configure two different data regions: one for your “mostly in memory” cache; another for your “mostly on disk” cache. > On 2 Jun 2021, at 16:24, gigabot wrote: > > > When using native persistence, can I configure what percentage or amount f > data is kept in RAM? I have two cac

Native Persistence Tuning - Percentage kept in RAM

When using native persistence, can I configure what percentage or amount f data is kept in RAM? I have two caches, one I want kept mostly in RAM and the other mostly on disk, so I want to configure their Data Regions differently. It seems from testing that MaxSize only affects the total size

Re: [Meetup] Native persistence storage overview. April 27 2021

Thank you, Anton! Here's the video https://youtu.be/LiUoZtSdJ3Y and slides https://t.ly/902X пн, 19 апр. 2021 г. в 17:57, Anton,Kalashnikov : > Hi Igniters, > > There is meetup next week, where I want to share my knowledge about > Ignite Persistence module. It will be high level overview of the

[Meetup] Native persistence storage overview. April 27 2021

Hi Igniters, There is meetup next week, where I want to share my knowledge about Ignite Persistence module. It will be high level overview of the main components and the main ideas behind the Persistence module. If you interested you can join at 8AM(PST), April 27. More info -

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

1) My testing shows that CassandraCacheStoreFactory is read from xml config once if the cache name does not exist in Ignite Persistence. It appears that CassandraCacheStoreFactory bean is persisted along with cache name in Ignite Persistence Store, CassandraCacheStoreFactory will not be

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! Looks overall correct. Regards, -- Ilya Kasnacheev чт, 14 янв. 2021 г. в 11:43, xmw45688 : > 1) My testing shows that CassandraCacheStoreFactory is read from xml config > once if the cache name does not exist in Ignite Persistence. It appears > that > CassandraCacheStoreFactory bean

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! 1) Can you please elaborate? If you set this value in a cache store factory, it will keep this boolean value and deserialize it when node is started. I'm not entirely sure if Ignite will store cache store factory or cache store instance in the persistent cache configuration. My expectation

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your recommendations! 1) The dynamicConfigurationReload is not able to reset once cacheStoreFactory is cached. It means that cacheStoreFactory does not read this value unless cacheStoreFactory is first instantiated. Do I miss something? Which factory should I put

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! This seems like a valid change, however, there are issues with it: if you don't have persistence settings files on some nodes, it will cause failure on these nodes. It may also re-read these files too eagerly in its current form. I can totally see how this may be an option to have in the

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your clarifications, and appreciated your suggestions and guidance. My college and I went to ignite-cassandra module, commented two lines, */testing purpose/*, in org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.getPersistenceSettings(), see the changes below.

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

may improve Cassandra cache store to track environment changes. Regards, -- Ilya Kasnacheev вт, 5 янв. 2021 г. в 04:38, xmw45688 : > Hi Ilya, > > Thanks for your guidance and happy new year! Sorry for late catchup. > > You are right, Ignite Native Persistence does track the c

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hi Ilya, Thanks for your guidance and happy new year! Sorry for late catchup. You are right, Ignite Native Persistence does track the changes in class definition for "Ignite Native Persistence". But the configuration to load data from Cache to Cassandra store is stored in xml con

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! Why do you think that change should be on Ignite Persistence side? You said yourself that Ignite Persistence tracks the changes in class definition, it's the Cassandra store that does not. Regards, -- Ilya Kasnacheev ср, 23 дек. 2020 г. в 00:17, xmw45688 : > Thanks for your

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your suggestion, Ilya. Can you give me a reference to override default Cassandra Store implementation? I thought that the changes would be on Ignite Persistence side because caching data from standalone Cassandra store (with Ignite Persistence) did read configuration including class

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! I think that maybe you could try coding such a cache store which will update this information. It's just that the default Cassandra store doesn't seem to. Regards, -- Ilya Kasnacheev сб, 19 дек. 2020 г. в 05:17, xmw45688 : > Thanks for your confirmation, Ilya. > > I do have a

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thanks for your confirmation, Ilya. I do have a follow-up question for you. When Ignite Persistence is used together with Cassandra. The caches for Cassandra table mappings are provided via xml file. The java class for the mappings is for BOTH Ignite Persistence and Cassandra cache store.

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

dra to > Ignite Cache stores using Cache.loadfull(). This works well for the > use > cases where 3rd party persistence store is used first, then Ignite Native > Persistence store is used with 3rd party persistence together later. > > However, the configuration of 3rd party pe

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Thank you for your answer. I'm able to load the data from Cassandra to Ignite Cache stores using Cache.loadfull(). This works well for the use cases where 3rd party persistence store is used first, then Ignite Native Persistence store is used with 3rd party persistence together later

Re: Native persistence and upgrading

Hello! All of 2.x are compatible, meaning you can upgrade from 2.x to 2.y, y > x, while keeping your persistence files. Yes, I think we should document this somewhere: https://issues.apache.org/jira/browse/IGNITE-13851 Regards, -- Ilya Kasnacheev пн, 14 дек. 2020 г. в 16:09, xero : > Thanks

Re: Native persistence and upgrading

Thanks for the confirmation Stanislav. Is this compatibility kept between minors as a commitment from the team or is it just specific to the versions I mentioned? If this is a backward compatibility feature that you have intentions to maintain, I think it's worth mentioning that in the

Re: Native persistence and upgrading

Yes, you can upgrade from an older version to a newer one and keep the data, it will just work. You don't really need snapshots for that, although I assume snapshots would also work. > On 10 Dec 2020, at 16:20, xero wrote: > > Hi Dimitry and community, > Is this still true? My intention is to

Re: Native persistence and upgrading

Hi Dimitry and community, Is this still true? My intention is to do it between versions 2.7.6 and 2.8.1/2.9. Basically, I want to only update the docker image keeping the volumes so that I can recover the persisted data. I couldn't find documentation regarding this topic. On the other hand,

Re: Native persistence enabled: Loading the same data again takes longer than initially

/durable-memory-tuning   > >From: VincentCE < v...@cephei.com > >To: user@ignite.apache.org >Cc: >Subject: Native persistence enabled: Loading the same data again takes >longer than initially >Date: Mon, 30 Nov 2020 16:55:17 +0300 > >Hi! > >I made the

Re: Native persistence enabled: Loading the same data again takes longer than initially

Vincent, What type of IgniteDataStreamer you are using? allowOverwrite == true/false? Are you loading data to SQL table or just a regular cache? Are there any indexes exists? Yes, disabling WAL means you have a risk of losing data while it still remains disabled. Then the initial loading

Re: Native persistence enabled: Loading the same data again takes longer than initially

Hi Maxim! we are generally using IgniteDataStreamers for cache loadings. Regarding disabling wal: We already thought about that during initial loading but our business business flow requires several further loadings and at least during the second load we cannot switch it off anyway. Otherwise

Re: Native persistence enabled: Loading the same data again takes longer than initially

Hello Vincent, What kind of Ignites API you are using for initial data loading? I always use this man page [1] for my local tests with simultaneously disabling WALs if the Ignite native persistence enabled. [1] https://apacheignite.readme.io/docs/data-loading On Mon, 30 Nov 2020 at 16:55

Native persistence enabled: Loading the same data again takes longer than initially

Hi! I made the observation that loading data initially into the ignite-cluster with native persistence enabled is usually a lot faster than subsequent loadings of the same data, that is 30 min (initially) vs 52 min (4th time) for 170 GB of data. Does this indicate bad configurations from our

Re: Native persistence - No space left on device error

; > Regards, > -- > Ilya Kasnacheev > > > ср, 18 нояб. 2020 г. в 18:29, facundo.maldonado < > maldonadofacu...@gmail.com>: > >> What is the expected behavior of native persistence when there is no more >> space on disk? >> >> I'm getting this error wh

Re: Native persistence - No space left on device error

Kasnacheev ср, 18 нояб. 2020 г. в 18:29, facundo.maldonado : > What is the expected behavior of native persistence when there is no more > space on disk? > > I'm getting this error when I reach the max size of the mounted volume > (storage, not

Native persistence - No space left on device error

What is the expected behavior of native persistence when there is no more space on disk? I'm getting this error when I reach the max size of the mounted volume (storage, not wal): *class org.apache.ignite.IgniteCheckedException: No space left on device* I assumed, that when there is no more

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

's seem to > me > that the keyspace are cached in the Ignite native persistence layer. > > How do I change the keyspaces of Cassandra? > > The use case is that we use Ignite as cache initially with the data stored > in Cassandra. With the data increase, caching all data is impracti

not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

instead of the new keyspace that are in ignite config file. It's seem to me that the keyspace are cached in the Ignite native persistence layer. How do I change the keyspaces of Cassandra? The use case is that we use Ignite as cache initially with the data stored in Cassandra. With the data

Re: [MEETUP] Apache Ignite Best Practices for Native Persistence and Data Recovery

Vasiliy, You can find a link to the recording in the comments section here: https://www.meetup.com/ru-RU/Apache-Ignite-Virtual-Meetup/events/271602652/ - Denis On Wed, Jul 29, 2020 at 2:36 AM Vasily Laktionov wrote:

Re: [MEETUP] Apache Ignite Best Practices for Native Persistence and Data Recovery

Hi, Please share slides and/or video of meetup. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

[MEETUP] Apache Ignite Best Practices for Native Persistence and Data Recovery

Hi, Next Tuesday on meetup [1] I'll make a presentation about Ignite Native Persistence. I'll share insights how it works under the hood. Also I'll give some advice on how to configure it and tune its performance. TIME ZONES 5:30 AM Pacific Daylight Time 8:30 AM Eastern Daylight Time 1:30 PM

Re: Ignite Native Persistence With write behind additional store

ersistence with a configuration for 3rd party cache store. Both can be found in the documentation and Ignite examples. Evgenii ср, 15 июл. 2020 г. в 08:22, Devakumar J : > Hi, > > Thanks for the reply. > > is there a reference to configure custom store along with native > persi

Re: Ignite Native Persistence With write behind additional store

Hi, Thanks for the reply. is there a reference to configure custom store along with native persistence enabled. Thanks & Regards, Devakumar J -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Native Persistence With write behind additional store

июл. 2020 г. в 08:23, Devakumar J : > Hi, > > I am exploring ways to do data backup along with native persistence. Is it > possible to achieve this using cache store implementation. So that data > will > be persisted in disk as well as replica copy. > > Thanks, > Devakum

Ignite Native Persistence With write behind additional store

Hi, I am exploring ways to do data backup along with native persistence. Is it possible to achieve this using cache store implementation. So that data will be persisted in disk as well as replica copy. Thanks, Devakumar J -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: native persistence

Hi, Indexes are stored in the same place as the data, in a file called index.bin You can't change the relative location of the index file(s). Only the storage path/wal path/wal archive path(s) could be specified. See:

native persistence

Hi All, I have read that it is a good idea to have wal, walarchive and data on separate drives. How about indexes? How would you specify the path for the indexes? Is the idea to specify the data and indexes on one drive and wal/walarchive on another? thanks.

Re: Using native persistence to "extend" memory

Thank you both for clarifying this. I usually also have large objects 3KB so I thought about increasing the page size to 32KB to reduce the number of pages and thus reduce the speed at which we get to the 2/3 of dirty pages. Good idea? On top of that during the process at some I generate a

Re: Using native persistence to "extend" memory

just disable it: > https://www.gridgain.com/docs/latest/developers-guide/persistence/native-persistence#disabling-wal > > Best Regards, > Evgenii > > > > вт, 16 июн. 2020 г. в 17:02, Denis Magda : > >> Steve, >> >> Please check these generic recommendations if y

Re: Using native persistence to "extend" memory

in case of failure and start data loading again. Four your use case, if you don't care about restore, you can just disable it: https://www.gridgain.com/docs/latest/developers-guide/persistence/native-persistence#disabling-wal Best Regards, Evgenii вт, 16 июн. 2020 г. в 17:02, Denis Magda

Re: Using native persistence to "extend" memory

Steve, Please check these generic recommendations if you haven't done so already: https://apacheignite.readme.io/docs/durable-memory-tuning#native-persistence-related-tuning Otherwise, send us a note if you come across any bottlenecks or issues so that we can give you more specific

Re: Using native persistence to "extend" memory

Thanks a lot for the recommendation. So keeping the WAL, disabling archiving. I understand all records are kept on disk. Thanks again. Anything else? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Using native persistence to "extend" memory

Hi Steve, I think that you can get a performance hit for your write operations by disabling the WAL. It serves two purposes in Ignite. The first is the recovery while the second is fast disk writes. The WAL is an append-only structure and Ignite can persist changes to disk really quick. If the

Using native persistence to "extend" memory

Hello, I am trying to use ignite persistence to "extend" memory. That is to replace the swap that is not working very well. Therefore since I do not care about recovery I disabled the WAL. Are there other things you would recommend to configure to use the ignite persistence as a sort of swap.

Re: When trying to activate cluster to use ignite native persistence getting topology update failed error .

Hello! By default, information is logged to console (standard out). Please start your node with -DIGNITE_QUIET=false (or bin/ignite.sh -v) and copy-paste its output as you try to activate cluster. Regards, -- Ilya Kasnacheev чт, 27 февр. 2020 г. в 08:39, Preet : > I am new to Ignite. I

Re: When trying to activate cluster to use ignite native persistence getting topology update failed error .

I am new to Ignite. I don't know how to check log. When I searched then I got to know that it is under /work/logs but I think that are static file. I don't know why activating cluster node is failing. I want to use persistence enabled feature for my IGFS application. -- Sent from:

Re: When trying to activate cluster to use ignite native persistence getting topology update failed error .

olve this error. I want > to use native persistence feature. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

When trying to activate cluster to use ignite native persistence getting topology update failed error .

<http://apache-ignite-users.70518.x6.nabble.com/file/t2787/Screenshot_2020-02-26_at_4.png> This is the error I received. Please help me to resolve this error. I want to use native persistence feature. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Native Persistence & JDBC

different type of error. > Now that I enabled the cluster, the code works with native persistence. > thanks. > > On Tue, Jan 21, 2020 at 5:36 AM Ilya Kasnacheev > wrote: > >> Hello! >> >> Can you please provide complete error message, with stack traces if >&g

Re: Native Persistence & JDBC

Hello Ilya, It seems the issue was that I had not enabled the cluster. I'd have expected a different type of error. Now that I enabled the cluster, the code works with native persistence. thanks. On Tue, Jan 21, 2020 at 5:36 AM Ilya Kasnacheev wrote: > Hello! > > Can you please provide

Re: Native Persistence & JDBC

ve any issue with this configuration if I don't > enable native persistence. > > > > > > > > > > > > > > On Mon, Jan 20, 2020 at 10:40 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> wrote: > >> Hello! >> >> Maybe you don't hav

Re: Native Persistence & JDBC

Hello Ilya I do have the PERSON2 cache. Here is the snippet for the cache configuration. I don't have any issue with this configuration if I don't enable native persistence. wrote: > Hello! > > Maybe you don't have PERSON2 cache? :) > > Regards, > -- > Ilya Ka

Re: Native Persistence & JDBC

Hello! Maybe you don't have PERSON2 cache? :) Regards, -- Ilya Kasnacheev пн, 20 янв. 2020 г. в 02:47, narges saleh : > Hi All > > I am using JDBC connection for inserting data into caches specified in my > config file (via query entities). If I don't enable native persistence,

Native Persistence & JDBC

Hi All I am using JDBC connection for inserting data into caches specified in my config file (via query entities). If I don't enable native persistence, everything works fine and I can insert the data into cache/table and query the cache/table. But if I enable native persistence, the client dies

Re: Ignite native persistence

Tried with appending cache name as schema with no success. Attach is a link to my project: https://drive.google.com/open?id=1F53um8TeUK45U3SOW0_Vlj04S8DWyjKI Please take a look. I suspect it is something in my code. Thanks, Naushad -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite native persistence

You might need to set the cache name as a schema for the queries. For instance, the query needs to be transformed to "Select ... {YOUR_CACHE_NAME}.ARInvoice FROM ..". Also, do you really need to have both 3rd party and native persistence enabled for the cluster. If the 3rd party is

Re: Ignite native persistence

ignite_sql_error.ignite_sql_error ARInvoiceRepository.java Attached is the file containing statcktrace and the

Re: Ignite native persistence

Please send exception/error message you are getting and the query you are trying to execute. On Tue, Nov 26, 2019, 8:04 PM niamin wrote: > I found what I was doing wrong. I can now load/pre-fetch from 3rd party > store > to cache. It looks like the data is present in in-memory cache but also >

Re: Ignite native persistence

I found what I was doing wrong. I can now load/pre-fetch from 3rd party store to cache. It looks like the data is present in in-memory cache but also stored in the persistent store. However, when I run a native query configured on my SpringData Repository I get an error that the SQL table

Re: Ignite native persistence

Thanaks Denis. However, how do or should I preload the data to disk first? Or as Ignite fetches data from the 3rd part datastore it is expected to distribute between RAM and disk? Is there an example project that implements this strategy? On my POC, I have SpringBoot project that includes the

Re: Ignite native persistence

Hi there, Looks like you are trying to preload data from the persistence to memory with Cache.loadCache method. Presently, this operation is not supported for the native persistence and it’s optional - just start issuing your queries after the cluster restart and Ignite will get all the data

Ignite native persistence

What is the right way to enable native persistence? As per Ignite documentation, I added the following property to enable native persistence

Re: Cache expiry policy not deleting records from disk(native persistence)

this is same as https://issues.apache.org/jira/browse/IGNITE-10862 >> Any idea on the timeline of these tickets? >> In the documentation >> https://apacheignite.readme.io/v2.7/docs/expiry-policies >> it says when native persistence is enabled "*expired entries are remove

Re: Cache expiry policy not deleting records from disk(native persistence)

https://issues.apache.org/jira/browse/IGNITE-12152 but this is same as https://issues.apache.org/jira/browse/IGNITE-10862 Any idea on the timeline of these tickets? In the documentation https://apacheignite.readme.io/v2.7/docs/expiry-policies it says when native persistence i

Re: Cache expiry policy not deleting records from disk(native persistence)

This is very troublesome. Persistence will kill your disk and LRU doesn't seem to work for offheap with persistence disabled (see "Data region LRU offheap algo not working")It seems the only way to expire items is to keep it on heap with an expiry policy Regards, Rick -- Sent from:

Re: Cache expiry policy not deleting records from disk(native persistence)

tps://issues.apache.org/jira/browse/IGNITE-12152 but > this is same as https://issues.apache.org/jira/browse/IGNITE-10862 > Any idea on the timeline of these tickets? > In the documentation > https://apacheignite.readme.io/v2.7/docs/expiry-policies > it says when native persistence is enabled

Re: Cache expiry policy not deleting records from disk(native persistence)

I have filed a bug https://issues.apache.org/jira/browse/IGNITE-12152 but this is same as https://issues.apache.org/jira/browse/IGNITE-10862 Any idea on the timeline of these tickets? In the documentation https://apacheignite.readme.io/v2.7/docs/expiry-policies it says when native persistence

Re: Cache expiry policy not deleting records from disk(native persistence)

Use% Mounted on > /dev/vdj 15G 1.6G 14G 11% /opt/ignite/persistence > Filesystem Size Used Avail Use% Mounted on > /dev/vdj 15G 1.6G 14G 11% /opt/ignite/persistence > Filesystem Size Used Avail Use% Mounted on > /dev/vdj 15G 1.6G 14G 11% /opt/ignite/persistence > Filesystem Siz

Re: Cache expiry policy not deleting records from disk(native persistence)

records from the disk, but ignite document says when expiry policy is set and native persistence is enabled then it deletes records from disk as well. Am I missing some configuration? Any help is appreciated. Shiva

Cache expiry policy not deleting records from disk(native persistence)

s when expiry policy is set and native persistence is enabled then it deletes records from disk as well. Am I missing some configuration? Any help is appreciated. Shiva

Re: Using Ignite Native Persistence as a "temporary durable" cache

: (modified section in above example) [image: image.png] On Thu, Sep 5, 2019 at 12:17 PM Alexander Korenshteyn < alexanderko...@gmail.com> wrote: > Hello, >Ignite native persistence has a good track record, is fast and > reliable, you can use it in your application. >

Re: Using Ignite Native Persistence as a "temporary durable" cache

Hello, Ignite native persistence has a good track record, is fast and reliable, you can use it in your application. Take a look at the following example of how to use a streamer to quickly insert data: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite

Using Ignite Native Persistence as a "temporary durable" cache

Hi all, We have MS SQL database server which contains all data. Our application will fetch some datas from database server and put them to the cache. And then, during 5-10 seconds we will do some updates to that objects and push that changes to ignite in-memory cache. And then, after 5-10 seconds

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Are you available for a verbal conversation? I would invite a solution architect on a call to figure out if Ignite works or not for your use case. - Denis On Wed, May 15, 2019 at 10:17 PM Denis Magda wrote: > Hi, > > But after seeing your explanation below I understand that option 2 above is

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Hi, But after seeing your explanation below I understand that option 2 above is > not really the way Ignite is supposed to be used - even if it is on top of > hadoop. Did I get that right? In this configuration, Ignite will not be on top of Hadoop, it will be close to it - deployed as separate

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

Hi Denis, Thank you very much for a good response. Definitely helps. Hope I can ask one follow-up question which I feel I did not make so clear from the beginning: The business has a very strong (non-negotiable) requirement on that the data warehouse should be modeled with high normalisation.

Re: SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

HDFS. And the maintenance team requires the data > movement to be implemented through SQL APIs. > > Main Question: Would it be a viable use case to use Ignite with native > persistence store as storage when building a relational data warehouse? So > that we do not have to manage

SW recommendation: Ignite Native Persistence for traditional relational data warehouse?

it be a viable use case to use Ignite with native persistence store as storage when building a relational data warehouse? So that we do not have to manage both a RDBMS and Ignite. I don’t fully see a clear picture of what the limitations would be of using native persistence instead of RDBMS for persistence

Re: NATIVE PERSISTENCE: Cache data is destroyed after disable WAL and restart

Thanks Denis! Regards. Manu. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: NATIVE PERSISTENCE: Cache data is destroyed after disable WAL and restart

oreCacheGroupStart > > > Process to replicate it: > > 1. Start one or more server nodes with native persistence enabled > 2. Create a cache (natively persisted) and store some data > 3. Disable WAL for cache - ignite().cluster().disableWal("TheCacheName") > 4. Restart

  1   2   3   >