Re: Crash recover for Ignite persistence cluster (lost partitions case)

Hello Ilya! Thank you very much for your explanations! It became much more clear what is going on when nodes are going to be shut down. Out main goal is to restore cluster in case of unexpected errors and be able to restore all data that was backupped on persistence. So I enabled auto adjust a

Re: Crash recover for Ignite persistence cluster (lost partitions case)

Hi Роза, In addition to my previous answer: Nov 22 12:39:25 yc-ignite-lab-02 systemd[1]: apache-ign...@config.xml.service: State 'stop-final-sigterm' timed out. Killing. Nov 22 12:39:25 yc-ignite-lab-02 systemd[1]: apache-ign...@config.xml.service: Killing process 11135 (java) with signal SIGKILL

Re: Crash recover for Ignite persistence cluster (lost partitions case)

About baseline topology you can read in documentation [1]. Manual baseline baseline management can be done available by means of control script [2]. Links: 1. https://ignite.apache.org/docs/latest/clustering/baseline-topology 2. https://ignite.apache.org/docs/latest/tools/control-script#activation

Re: Crash recover for Ignite persistence cluster (lost partitions case)

There is a typo here: > Lost partitions are expected behaviour in case of partition because you have only 1 backup and lost two nodes. I mean, that lost partitions are expected behaviour in case of partitioned caches when the number of offline nodes is more than the number of backups. In your case

Re: Crash recover for Ignite persistence cluster (lost partitions case)

Hi, > 1) What can I do to recover from partitions lost problem after shutting down several nodes? > I thought that in case of graceful shutdown this problem must be solved. > Now I can recover by returning *one* of offline nodes to cluster (starting the service) and running *reset_lost_partitions*

Re: Crash recover for Ignite persistence cluster (lost partitions case)

Hi Sumit! Thanks for your reply! Yeah, I have used this utility reset_lost_partitions many times. The problem is that this function requires all baseline nodes to be present. If I shutdown node auto adjustment does not remove this node from baseline topology and reset_lost_partitions ends with

Re: Crash recover for Ignite persistence cluster (lost partitions case)

Please check if this helps: https://ignite.apache.org/docs/latest/configuring-caches/partition-loss-policy#handling-partition-loss Also any reason baseline auto adjustment is disabled? On Tue, Nov 22, 2022 at 6:38 PM Айсина Роза Мунеровна < roza.ays...@sbermarket.ru> wrote: > Hola again! > > I di

Re: Crash recover for Ignite persistence cluster (lost partitions case)

Hola again! I discovered that enabling graceful shutdown via does not work. In service logs I see that nothing happens when SIGTERM comes :( Eventually stopping action has been timed out and SIGKILL has been sent which causes ungraceful shutdown. Timeout is set to 10 minutes. Nov 22 12:27:23 yc

Crash recover for Ignite persistence cluster (lost partitions case)

Hola! I have a problem recovering from cluster crash in case when persistence is enabled. Our setup is - 5 VM nodes with 40G Ram and 200GB disk, - persistence is enabled (on separate disk on each VM), - all cluster actions are made through Ansible playbooks, - all caches are either partitioned wi

Re: ignite-persistence distribution is not even

stent store until you >>> insert these keys back into Ignite. So, it looks like voids in data pages. >>> But the rebalanced data is put into persistent storage without any kind of >>> "voids", i.e. it is already compressed during the rebalance routine. >>

Re: ignite-persistence distribution is not even

ng the rebalance routine. >> >> пн, 8 нояб. 2021 г. в 17:36, Ibrahim Altun > >: >> >>> Hi, >>> >>> We had a 2 node cluster with persistence enabled with backup(1) enabled, >>> this morning we've added a new node to the cluster. >>

Re: ignite-persistence distribution is not even

balance routine. >> >> пн, 8 нояб. 2021 г. в 17:36, Ibrahim Altun > <mailto:ibrahim.al...@segmentify.com>>: >> Hi, >> >> We had a 2 node cluster with persistence enabled with backup(1) enabled, >> this morning we've added a new node t

Re: ignite-persistence distribution is not even

яб. 2021 г. в 17:36, Ibrahim Altun : > >> Hi, >> >> We had a 2 node cluster with persistence enabled with backup(1) enabled, >> this morning we've added a new node to the cluster. >> Although rebalancing is finished Ignite Persistence values are not evenly >> dis

Re: ignite-persistence distribution is not even

t is already compressed during the rebalance routine. > > пн, 8 нояб. 2021 г. в 17:36, Ibrahim Altun <mailto:ibrahim.al...@segmentify.com>>: > Hi, > > We had a 2 node cluster with persistence enabled with backup(1) enabled, this > morning we've added a new node to t

Re: ignite-persistence distribution is not even

> ... initCfg=40MB, maxCfg=100MB, usedRam=0MB, freeRam=100%, > allocRam=100MB, allocTotal=0MB] > > ^-- volatileDsMemPlc region [type=user, persistence=false, > lazyAlloc=true, > > ... initCfg=40MB, maxCfg=100MB, usedRam=0MB, freeRam=100%, > allocRam=0MB] >

ignite-persistence distribution is not even

Hi, We had a 2 node cluster with persistence enabled with backup(1) enabled, this morning we've added a new node to the cluster. Although rebalancing is finished Ignite Persistence values are not evenly distributed; server-1: [2021-11-08T14:31:29,371][INFO ][grid-timeout-worke

Re: Ignite persistence is accepting null value in not null field

Hello! Okay, this looks like a bug. Can you please put a small reproducer project with this code somewhere on github, or provide as tarball? I will try it and file a ticket, or you can do that yourself. Regards, -- Ilya Kasnacheev пн, 5 апр. 2021 г. в 18:16, sourav dihidar : > Thanks for your

Re: Ignite persistence is accepting null value in not null field

Thanks for your response. Wanted to understand that then how in the second run it is throwing error? On Mon, Apr 5, 2021, 4:27 PM Ilya Kasnacheev wrote: > Hello! > > I guess that "not null" is only tracked by SQL code, but not by cache API > or data streamer. > > Regards, > -- > Ilya Kasnacheev

Re: Ignite persistence is accepting null value in not null field

Hello! I guess that "not null" is only tracked by SQL code, but not by cache API or data streamer. Regards, -- Ilya Kasnacheev сб, 3 апр. 2021 г. в 18:22, sourav dihidar : > Hi Team, > I am facing one issue > I created one table as below > CREATE TABLE STUDENT > ( > ID INTEGER NOT NULL, > NAM

Ignite persistence is accepting null value in not null field

Hi Team, I am facing one issue I created one table as below CREATE TABLE STUDENT ( ID INTEGER NOT NULL, NAME VARCHAR(200) NOT NULL, SALARY INTGER NOT NULL, PRIMARY KEY(STUDENTID) )WITH "KEY_TYPE=Tab_Key,VALUE_TYPE=TAB_VALUE"; I used datastreamer to load the data into the table try(IgniteDataStre

Re: Ignite persistence: Data of node lost that got excluded from baseline topology

Hello! 1. I guess it's possible to activate a cluster manually when not all baseline nodes are in. Later you can join your node back to baseline, hopefully. Please note that there's still chance that old data will be deleted from node upon join: We can only re-use data from old partition when we'r

Re: Ignite persistence: Data of node is lost after being excluded from baseline topology

Hi igniters! could I have short answers to my questions? Thanks a lot! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite persistence: Data of node lost that got excluded from baseline topology

Hi! in our project we are currently using ignite 2.8.1 without ignite native persistence enabled. No we would like to enable this feature to prevent data loss during node restart. Important: We use AttributeNodeFilters to separate our data, e.g data of type1 only lives in the type1-clustergroup

Re: Question about Ignite persistence disk space used after clearing cache

5, 2020 at 1:52 PM Scott Prater wrote: > >> I have a question about how the off-heap usage is reported when Ignite >> persistence is configured. I have a single node set up. I stored about >> 1GB of items in the cache, then cleared the cache (remotely, using the Java >>

Re: Question about Ignite persistence disk space used after clearing cache

/administrators-guide/monitoring-metrics/metrics#allocated-space-vs-actual-size-of-data - Denis On Fri, Sep 25, 2020 at 1:52 PM Scott Prater wrote: > I have a question about how the off-heap usage is reported when Ignite > persistence is configured. I have a single node set up. I stored about

Question about Ignite persistence disk space used after clearing cache

I have a question about how the off-heap usage is reported when Ignite persistence is configured. I have a single node set up. I stored about 1GB of items in the cache, then cleared the cache (remotely, using the Java thin client: ClientCache.clear()). I then verified that the items were no

Re: Ignite persistence and activation

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

Re: Ignite persistence and activation

. Evgenii чт, 11 июн. 2020 г. в 05:18, steve.hostettler : > Hello. > > I am trying to implement ignite persistence but I stumbled upon the > following problems/questions. It is required to activate the cluster, that > much is clear but I have bootstrap code that is using technical caches

Ignite persistence and activation

Hello. I am trying to implement ignite persistence but I stumbled upon the following problems/questions. It is required to activate the cluster, that much is clear but I have bootstrap code that is using technical caches that I do not want to persist and more problematic I need to use

Re: Apache Ignite Persistence Issues/Warnings

Hello! In both cases Ignite will walk through the segments it needs, and adjust persistence for any data that was updated in already completed operations. Archive or no archive is a logistical choice, as far as my understanding goes. Regards, -- Ilya Kasnacheev вт, 12 мая 2020 г. в 07:28, adi

Re: Apache Ignite Persistence Issues/Warnings

Hi Alex, Are you saying if we disable WAL Archiving, will there be any problem? Let's say if I disable WAL archiving and if 6 out of 10 WAL segments are filled then what happens during OS crash? When we restart the server, will all the operations in those 6 segments be updated on the disc data b

Re: Apache Ignite Persistence Issues/Warnings

Hi, You need to be careful w/disabling WAL archiving. It is best to put the WAL on a separate (quicker) disk: https://apacheignite.readme.io/docs/durable- memory-tuning#separate-disk-device-for-wal This section will be of benefit to you when tuning persistence: https://apacheignite.readme

Re: Apache Ignite Persistence Issues/Warnings

Hi Alex, thanks for the reply. But as our application is write/update intensive, we want a good performance/high availability application solution along with disk persistence. In that case, what configuration would you suggest for the following case, 1. Disk storing functionality can run periodi

Re: Apache Ignite Persistence Issues/Warnings

Hi, Throttling is applied to page modifications [percentOfPartTime=0.62, markDirty=2440 pages/sec, checkpointWrite=1971 pages/sec, estIdealMarkDirty=0 pages/sec, curDirty=0.00, maxDirty=0.02, avgParkTime=253807 ns, pages: (total=132474, evicted=0, written=831, synced=0, cpBufUsed=543, cpBufTotal=25

Apache Ignite Persistence Issues/Warnings

We are running a write-intensive load test on Apache Ignite. We are also doing reads. We are getting the following warning messages from sys-stripe threads quite often after a few hours of testing. DB Config -> RAM - 8GB, CPU cores - 64, Persistence - ON, Heap - 2GB, Durable memory Off-heap - 2GB,

Re: Ignite Persistence

Thanks for sharing this useful info -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Persistence

> Hi > > Currently we are using ignite as an in-memory cache.We are now trying to > explore the ignite persistence to avoid reloading the caches whenever the > cluster restarts. > > Had a walk through of the documentation and have one question.Can any one > help me answer the followi

Ignite Persistence

Hi Currently we are using ignite as an in-memory cache.We are now trying to explore the ignite persistence to avoid reloading the caches whenever the cluster restarts. Had a walk through of the documentation and have one question.Can any one help me answer the following question. For example i

Re: Ignite Persistence: Baseline Topology

Denis, it's not about the size - the size could be different. It's about having different configured DataRegions and creating caches without NodeFilter. If newly added node has new DataRegion and cache created for this region - it will lead to the cluster failure. Evgenii ср, 8 янв. 2020 г. в 13:

Re: Ignite Persistence: Baseline Topology

Andrey, Are you saying we require to have regions of the same size preconfigured across the nodes? Hope I misunderstood you. - Denis On Mon, Jan 6, 2020 at 7:18 AM Andrei Aleksandrov wrote: > Hi, > > I guess that every data node should have have the same data regions. I > checked that in case

Re: Ignite Persistence: Baseline Topology

Hi, I guess that every data node should have have the same data regions. I checked that in case if you have for example 2 nodes with persistence region in BLT and then start a new node (that isn't the part of BLT) with new region and some cache in this new region then it will produce next exc

Re: Ignite Persistence: Baseline Topology

You can also look to this topic, probably related to yours with code sample http://apache-ignite-users.70518.x6.nabble.com/Embedded-ignite-and-baseline-upgrade-questions-td30822.html -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite Persistence: Baseline Topology

I have a few queries: 1. There are 4 nodes. 2 of them with persistence enabled and rest with persistence disabled. And now I want to activate the cluster. Is it normal? Will it work? 2. There 2 nodes with persistence enabled. I have activated the cluster, and I am able to see two nodes in baselin

Re: ignite persistence size growing

This is very abstract question, could you pinpoint what folders are exactly growing in size in your node work directory? I would assume that your WAL archive is growing in size, could you please check subfolders sizes in $IGNITE_HOME/work/db and especially /wal folder inside that one? -- Sent f

ignite persistence size growing

Hi Team, I have enabled persistence with cache eviction of 8 days of creation time. But my persistence data folder is keep on growing. Even we are deleting entries from Caches, but persistence size still growing. Is there way we can clean and reduce the size of persistence. Thanks & Regards, Ve

Re: Mysql and ignite persistence inheritance issues

This won't be supported - our SQL engine can't be integrated with 3rd party storage like MySQL. If you can't fit all the data in RAM then use native persistence which is supported by SQL. - Denis On Thu, Feb 21, 2019 at 11:54 PM hulitao198758 wrote: > Ignite does not enable the persistence fun

Mysql and ignite persistence inheritance issues

Ignite does not enable the persistence function. The startup is to connect to the MySql database. The Sql statement can be run in Ignite to automatically load the data in mysql. In Ignite, select, insert, update, delete, etc., if the data in the memory does not exist, then Automatically load data f

Re: Ignite Persistence

l the nodes go down at one time. If it's an unlikely event situation that it's ok to relax the mode to LOG_ONLY as long as you have backups copies on other nodes. -- Denis On Tue, Jan 1, 2019 at 8:23 PM Ignite Enthusiast wrote: > Question on Ignite Persistence: > > On a deployed Ig

Ignite Persistence

Question on Ignite Persistence: On a deployed Ignite (3 node) cluster, I see one one node being taken out of the cluster because it encounters GC Pauses. Worse, when this node leaves the cluster, a Rebalance is initiated (and re-initiated when the node joins back). Note: Data that Ignite Cluster

Re: Using 3rd Party Persistence Together with Ignite Persistence

Hello Patrick, Do you really need to persist to both MySQL and Ignite Persistence? Is it possible to settle on one of the disk storages only? -- Denis On Tue, Nov 27, 2018 at 9:36 AM PatrickEgli wrote: > Hi > > We're interested in using Apache Ignite for our next project. Ou

Using 3rd Party Persistence Together with Ignite Persistence

ith Apache Ignite Persistence. Today we saw that Ignite cannot guarantee consistency between native persistence and 3rd party persistence. 3rd Party Persistence <https://apacheignite.readme.io/docs/3rd-party-store#section-using-3rd-party-persistence-together-with-ignite-persistence>

Re: Long activation times with Ignite persistence enabled

Do we have any update on this Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Long activation times with Ignite persistence enabled

Hi Pavel We are using Ignite 2.6 You were saying, usage of cache groups is definitely needed to improve to the cluster activation time ? I could see below documentation on the usage of cache groups. Should the grouping be used all the times? With all the benefits the cache groups have, th

Re: Long activation times with Ignite persistence enabled

Hi Pavel We are using Ignite 2.6 You were saying, usage of cache groups is definitely needed to improve to the cluster activation time ? I could see below documentation on the usage of cache groups. *Should the grouping be used all the times? With all the benefits the cache groups have, they mi

Re: Long activation times with Ignite persistence enabled

Hi Naveen and Andrey, We've recently done major optimization https://issues.apache.org/jira/browse/IGNITE-9420 that will speed-up activation time in your case. Iteration over WAL now happens only on a node start-up, so it will not affect activation anymore. Partitions state restoring (which is the

Re: Long activation times with Ignite persistence enabled

Hi Denis We have already reduced the partition to 128, after which activation time has come down a bit. You were saying that, by reducing the partitions, it may lead to uneven distribution of data between nodes. Isn't it the same when we go for cache groups, group of caches will use the same res

Re: Long activation times with Ignite persistence enabled

HI Gianluca Removing this -XX:+AlwaysPreTouch did not help us at all, it took the same time with or without this. But I observed without this was, OS has not allocated entire heap memory we have given as JVM options, we were giving 200G as heap for ignite node, so when we execute top command, I

Re: Long activation times with Ignite persistence enabled

Naveen, 40 caches is quite a lot. It means, that Ignite needs to handle 40 * (number of partitions) files. By default each cache has 1024 partitions. This is quite a lot, and a disk is the bottleneck here. Changing of thread pool sizes won't save you. If you divide your caches into cache groups, t

Re: Long activation times with Ignite persistence enabled

Hello In my case of slow startup, as suggested from a member of this mailing list, I deleted the -XX:+AlwaysPreTouch command line option from JVM launch, and the cluster got back to very fast startup. Don't know if you are using this option, hope it helps. Cheers Gianluca Il giorno lun 5 nov 201

Re: Long activation times with Ignite persistence enabled

Hi Denis We have only 40 caches in our cluster. If we introduce grouping of caches, guess we need to reload the data from scratch, right ?? We do have very powerful machines as part of cluster, they are 128 CPU very high end boxes and huge resources available, by increasing any of the below threa

Re: Long activation times with Ignite persistence enabled

Naveen, How many caches do you have? As Alexey mentioned, usage of cache groups could reduce the number of created partitions and improve the startup time. Denis сб, 27 окт. 2018 г. в 11:12, Naveen : > Do we have any update long activation tim

Re: Long activation times with Ignite persistence enabled

Do we have any update long activation times ? I too face the same issue, am using 2.6. Cluster with 100 GB of disk size, got activated in 5 minutes, and when I tried with a cluster which has 3 TB is taking close to an hour. Is it the expected behavior OR some configuration I am missing here T

Re: Ignite Persistence Storage : Full data is stored in all activated nodes just local Data?

Hello! If your cache is REPLICATED then all data is stored on each node, if your cache is PARTITIONED then a subset of data is stored on each node. Please see CacheMode enum. Regards, -- Ilya Kasnacheev вт, 9 окт. 2018 г. в 18:27, ApacheUser : > Hi Team, > How does the data stored when the p

Re: Ignite Persistence Storage : Full data is stored in all activated nodes just local Data?

Only the data for that node is stored there, backup data on backup nodes, primary data on primary nodes and so on. Mikael Den 2018-10-09 kl. 17:27, skrev ApacheUser: Hi Team, How does the data stored when the persistenc eis enabled? Does Ignite Store all data in all Nodes enabled persistence

Ignite Persistence Storage : Full data is stored in all activated nodes just local Data?

Hi Team, How does the data stored when the persistenc eis enabled? Does Ignite Store all data in all Nodes enabled persistence or just the data which in that node? Ex: I have 4 node Ignite Cluster and persistence is enabled in all 4 nodes (activated after 4 nodes come up) . When the data is loa

Re: Problems are enabling Ignite Persistence

Hello! My only idea is that maybe you have PDS directory left over from 2.3 or earlier so it does not contain baseline. Otherwise, can you try adding your node to baseline? Regards, -- Ilya Kasnacheev ср, 3 окт. 2018 г. в 9:33, Lokesh Sharma : > I activated the cluster using "./control.sh --

Re: Problems are enabling Ignite Persistence

I activated the cluster using "./control.sh --activate" and it successfully activated the cluster. But when I try to see the baseline it says "no nodes found". The docs says "*As explained above, baseline

Re: Problems are enabling Ignite Persistence

Yes it works fine with just one node, I do it all the time for testing. Mikael Den 2018-10-01 kl. 09:06, skrev Ilya Kasnacheev: Hello! Due to https://apacheignite.readme.io/docs/baseline-topology your cluster should indeed auto-activate on a second run provided that all nodes which were in

Re: Problems are enabling Ignite Persistence

Hello! Due to https://apacheignite.readme.io/docs/baseline-topology your cluster should indeed auto-activate on a second run provided that all nodes which were in the original cluster are still available. Note that it will only work if you keep persistence directory intact between runs. I'm also n

Re: Problems are enabling Ignite Persistence

> > Could you also set correct path for IGNITE_HOME or set work directory in > Ignite configuration to exclude chances for your /tmp directory to be > wiped. Yes, tried but had no luck. On Fri, Sep 28, 2018 at 7:59 PM Lokesh Sharma wrote: > Hi > > Thanks for looking into this. > > >> First, I

Re: Problems are enabling Ignite Persistence

Hi Thanks for looking into this. > First, I had to change h2 version dependency from 1.4.197 to 1.4.195 - > maybe > this is because I have later snapshot of Apache Ignite compiled. The version is already 1.4.195. Second, I had to activate the cluster! You have to activate persistent > cluster

Re: Problems are enabling Ignite Persistence

Hello! Seems to be working for me after two changes. First, I had to change h2 version dependency from 1.4.197 to 1.4.195 - maybe this is because I have later snapshot of Apache Ignite compiled. Second, I had to activate the cluster! You have to activate persistent cluster after you bring all no

Re: Problems are enabling Ignite Persistence

> > Could you try to send minimalistic reproducer that > shows issue on clean setup? I have reproduced a minimal project that shows this behaviour. Here it is https://bitbucket.org/lokesh_blue/bugdemo/src/master/ It's a simple application. It should execute function "test" when ran. See ( https:

Re: Problems are enabling Ignite Persistence

As a general recommendation, whenever you see a hang like that make a thread dump to see why the threads are blocked. -- Denis On Wed, Sep 19, 2018 at 12:59 PM akurbanov wrote: > Hello, > > Could you also set correct path for IGNITE_HOME or set work directory in > Ignite configuration to exclud

Re: Problems are enabling Ignite Persistence

Hello, Could you also set correct path for IGNITE_HOME or set work directory in Ignite configuration to exclude chances for your /tmp directory to be wiped. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Problems are enabling Ignite Persistence

Hello, There are no issues with starting nodes with enabled persistence, your DataStorageConfiguration is fine, are there any other preconditions to be met to face same issue? Could you try to send minimalistic reproducer that shows issue on clean setup? Regards, -- Sent from: http://apache-ig

Problems are enabling Ignite Persistence

I enabled Ignite Persistence. Following is my configuration: //New Data Region > DataStorageConfiguration storageCfgPersistence = new > DataStorageConfiguration(); > DataRegionConfiguration regionCfg = new DataRegionConfiguration(); > regio

Re: Ignite persistence to local disk vs to cassandra

This article might be exactly what you're looking for: https://dzone.com/articles/apachereg-ignite-and-apachereg-cassandra-benchmark -- Denis On Fri, Aug 10, 2018 at 9:24 AM Wlodek, Tomasz wrote: > I have a question: Does anyone have numbers which compare the speed of > ignite when persistence

Ignite persistence to local disk vs to cassandra

I have a question: Does anyone have numbers which compare the speed of ignite when persistence is set to local file system as compared to when it is set to Cassandra? Tom This message may contain information that is confidential or privileged. If you are not the intended recipient, please ad

Re: Backup and Restore of Ignite Persistence

Hi, Yes Ignite store the data into files. For every cache entity could exist some primiry node and optionally several backups node. It could be configured in CacheConfiguration. Read about it you can here: https://apacheignite.readme.io/v1.1/docs/primary-and-backup-copies For example you have 3

Backup and Restore of Ignite Persistence

hi, I am planning to have some important tables on Apache Ignite Persistence and therefore am looking for best practices and recommendations around backup and restore of Ignite Persistence layer. As I understand, Ignite stores data in standard files. Will just taking a backup of these files

Re: Ignite Persistence performance issue

Yeah. Thats exactly what I am doing and seems to have improved. The frequency is set at 5000 i.e. 5 seconds Thanx and Regards, KR Kumar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Persistence performance issue

i've been having some issues with EC2 too. Are you actually paging from memory to disk or just using the WAL for durable memory? you can use a different walMode to make it "better". https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/WALMode.html. I was playing wi

Re: Ignite Persistence performance issue

Dave - Thanks... will toy with the I3 instance and see how that goes -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Persistence performance issue

I have had more success with i3 instances On Feb 21, 2018 10:01 PM, "KR Kumar" wrote: Hi All - I am using Ignite Persistence ( 2.3) for storing events that we receive from different sources. Currently the write and read throughput is 2k to 4k per second on a t2.xlarge and c4.2xlarge m

Ignite Persistence performance issue

Hi All - I am using Ignite Persistence ( 2.3) for storing events that we receive from different sources. Currently the write and read throughput is 2k to 4k per second on a t2.xlarge and c4.2xlarge machines on a 3 node cluster. The disks attached are provisioned SSDs with 1 IOPS. These

Re: 20 minute 12x throughput drop using data streamer and Ignite persistence

I've started reproducing this issue with more statistics, but have not reached the worst performance point yet, but somethings are starting to become clearer: The DataStreamer hashes the affinity key to partition, and then maps the partition to a node, and fills a single buffer at a time for the

Re: 20 minute 12x throughput drop using data streamer and Ignite persistence

I've started reproducing this issue with more statistics, but have not reached the worst performance point yet, but somethings are starting to become clearer: The DataStreamer hashes the affinity key to partition, and then maps the partition to a node, and fills a single buffer at a time for the

Re: 20 minute 12x throughput drop using data streamer and Ignite persistence

I made improvements to the statistics collection in the stream receiver, and I'm finding an excessive number of retry's of the optimistic transactions we are using. I will understand that and retry. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 20 minute 12x throughput drop using data streamer and Ignite persistence

We are pulling in a large number of records from an RDB, and reorganizing the data so that our analytics will be much faster. I'm running Sumo, and have looked at all of the log files from all the nodes, and the only things are checkpoints and GC logs. The checkpoints are fast, and occur at a low

Re: 20 minute 12x throughput drop using data streamer and Ignite persistence

Hi Dave, Is possible to share a code snippet which illustrates DataStreamer settings and stream receiver code? Best regards, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 20 minute 12x throughput drop using data streamer and Ignite persistence

Hi Dave, Could you please provide more details about that use-case. Is it possible to reproduce the issue and gather JFR and log files from all participated nodes? It would be very helpful in order to understand the cause of that behavior. Thanks! -- Sent from: http://apache-ignite-users.70518

20 minute 12x throughput drop using data streamer and Ignite persistence

I have a 8 node cluster with 244GB/node, and I see a behavior I don't have any insight into, and which doesn't make sense. I'm using a custom StreamReceiver which starts a transaction that starts a transaction and updates 4 partitioned caches, 2 of which should be local up

Re: Long activation times with Ignite persistence enabled

Hello! Can you please also provide full cache configuration and your hardware specs (especially for storage)? After 2.4 release is done, I hope your case will get attention of PDS developers. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Long activation times with Ignite persistence enabled

6 AM To: Alexey Goncharuk; user@ignite.apache.org Subject: Re: Long activation times with Ignite persistence enabled Alexey, Thanks a lot for looking into this! My configuration is very basic: 3 caches all using standard 1024 partitions, sharing a 1GB persistent memory region. Please find below the

Re: Long activation times with Ignite persistence enabled

-22 11:30:01,789 INFO [main] GridDiscoveryManager - ^-- durable [initSize=256.0 MiB, maxSize=1.0 GiB, persistenceEnabled=true] From: Alexey Goncharuk Sent: Monday, January 22, 2018 12:30 AM To: user@ignite.apache.org Subject: Re: Long activation times wi

Re: Long activation times with Ignite persistence enabled

Andrey, Can you please describe in greater detail the configuration of your nodes (specifically, number of caches and number of partitions). Ignite would not load all the partitions into memory on startup simply because there is no such logic. What it does, however, is loading meta pages for each

Re: Long activation times with Ignite persistence enabled

In my case, I had only 10G of data on disk and that took 1.5 minutes from node start to the active state. Now, in production I'm looking at more than 100G of data per node (primary + backup partitions). Should I expect the activation to take 15 minutes? If this is indeed the case, then Ignite P

Re: Long activation times with Ignite persistence enabled

Hello! As far as my understanding goes, there's no distinction in Ignite between "data pages" and "index pages" All pages in durable memory are parts of "B+ tree" and are holding both data and references to downward branches in other pages. I'm not sure it had to load all the pages. Maybe only on

Long activation times with Ignite persistence enabled

Hello, I'm wondering if there is a way to improve the startup time of Ignite node when the persistence is enabled? It seems the time is proportional to the size (and number) of the partition files. This is somewhat surprising as I expected the startup time be the same (plus-minus some constant

  1   2   >