Re: tuning near cache performance

Hi Scott, Performance won't be better than using a local HashMap because there is a lot of additional procedures for replicating, marshaling and so on. In some cases, performance can be improved. Could you provide a more detailed information? 1. Cache configuration 2. How many entries in the

Using 3rd party DB together with native persistence (WAS: Getting Invalid state exception when Persistance is enabled.)

Hi Prasad, // Please send different questions separately – this way it’s easier to answer and to search for existing answers > Also, I am loading the cache from oracle table using loadCache method. If the > persistence is enabled and if the data is already persisted, I want to make > sure

Custom log location for IgniteVisor

Hi All, Is it possible to give custom log location for all the logs generated by IgniteVisor instead of IGINITE_HOME/work ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Using 3rd party DB together with native persistence (WAS: GettingInvalid state exception when Persistance is enabled.)

Sorry, I wasn’t completely correct. Persistence and CacheStore can work together, but if cache configured with write-through or read-through modes enabled then data consistency between Ignite persistence and CacheStore is not guaranteed at all times, so such configurations are usually avoided.

Re: Custom log location for IgniteVisor

Hello, I think the easiest way is to specify IGNITE_LOG_DIR environment variable and starts Visor. more details can be found here: https://apacheignite.readme.io/docs/logging#section-default-logging Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Large durable caches

[03:14:36,596][INFO][db-checkpoint-thread-#77][GridCacheDatabaseSharedManager] Checkpoint finished [cpId=e2648942-961a-45c4-a7f9-41129e76b70f, pages=801041, markPos=FileWALPointer [idx=2131, fileOffset=1035404, len=60889, forceFlush=true], walSegmentsCleared=50, markDuration=913ms,

Re: Large durable caches

I fought with trying to get Ignite Persistence to work well on AWS GP2 volumes, and finally gave up, and moved to i3 instances, where the $ per write IOP are much lower, and a i3.8xlarge gets 720,000 4K write IOPS vs on the order of 10,000 for about the same cost. -- Sent from:

Re: tuning near cache performance

Hi Roman, 1. Cache Configuration NearCacheConfiguration nearCfg = new NearCacheConfiguration<>(); LruEvictionPolicy lruEvictionPolicy = new LruEvictionPolicy<>(5); nearCfg.setNearEvictionPolicy(lruEvictionPolicy); nearCfg.setNearStartSize(5);

Re: unsubscribe

To unsubscribe send an email to user-unsubscr...@ignite.apache.org : subject=Unsubscribe body=Please unsubscribe me. -- Roman -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

unsubscribe

Regards, Haopu

Re: Large durable caches

Of course, there is another option that may help - trying better AWS instances. Best Regards, Ivan Rakov On 22.02.2018 0:58, Ivan Rakov wrote: [03:14:36,596][INFO][db-checkpoint-thread-#77][GridCacheDatabaseSharedManager] Checkpoint finished [cpId=e2648942-961a-45c4-a7f9-41129e76b70f,

[Rank up] Prove there are many Ignite users and developers

Igniters, I've come across an interesting article [1] that suggests measuring project/product state and its community grows by putting together information from LinkedIn. Personally, I'm totally for this metric -- it's simple and vivid. However, we were so busy deploying our Ignite applications

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

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: Correct build process for Ignite

Hi, Please use instructions provided at DEVNOTES.txt On Wed, Feb 21, 2018 at 6:37 PM, shikharraje wrote: > Errata: mvn clean in the parent directory works. The other goals fail, > though. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Large durable caches

I'll give that tweaking a try. It's hard to do a thread dump just when it freezes, do you think there is harm in doing a thread dump every 10 seconds or something? I tried a new setup with more nodes to test out how that affects this problem (from 2 to 4). I saw less datastreaming errors, but

Re: Correct build process for Ignite

Hi Anton, As mentioned in my original mail, I tried the following command from DEVNOTES.txt: mvn clean install -Pall-java,all-scala,licenses -DskipTests But that gave the same error: [ERROR] Failed to execute goal on project ignite-core: Could not resolve dependencies for project

Re: Correct build process for Ignite

Errata: mvn clean in the parent directory works. The other goals fail, though. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Correct build process for Ignite

what maven version you use? On Wed, Feb 21, 2018 at 6:49 PM, shikharraje wrote: > Hi Anton, > > As mentioned in my original mail, I tried the following command from > DEVNOTES.txt: > > mvn clean install -Pall-java,all-scala,licenses -DskipTests > > But that gave the same

Ignite indexes and persistence

I've been testing ignite durable memory with trying to load a lot more data than I have configured for the dataregion, thereby using disk for a lot of data. I was wondering how indexes get persisted to disk in this situation where more data exists than will fit in memory? Is there a way to

Correct build process for Ignite

Hi, I am trying to build Ignite after cloning from Github. From the parent directory (i.e. containing folders assembly, bin, config, dev-tools, etc.), I tried the following commands: mvn clean mvn install mvn package mvn eclipse:eclipse mvn clean install -Pall-java,all-scala,licenses -DskipTests

Re: Correct build process for Ignite

Hi Anton, This is the output of "mvn -version": Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T13:28:13+05:30) Maven home: C:\Users\\Downloads\apache-maven-3.5.2\bin\.. Java version: 1.8.0_121, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_121\jre

Re: Ignite indexes and persistence

Hi, Did you test on single node or cluster? Could you describe in more ditails and provide configs? On Wed, Feb 21, 2018 at 11:24 PM, lawrencefinn wrote: > I've been testing ignite durable memory with trying to load a lot more data > than I have configured for the dataregion,

Re: Using 3rd party DB together with native persistence (WAS: Getting Invalid state exception when Persistance is enabled.)

Hi Stan, Thank you for the reply. I will send different questions separately now onwards. I do not understand what are you trying to say ( "*Ignite doesn’t support using 3rd party DBs and native persistence with the same cache*" ) . If the persistence is enabled and if you create or load the

Re: Issues trying to force redeployment in shared mode

Unsubscribe On Tue, Feb 20, 2018 at 1:09 PM Dave Harvey wrote: > I've done some additional testing. By shutting down another (the last) > client node that was running independent code, I was able to purge the bad > version of my code from the servers, while leaving the

Re: How to monitor page eviction ?

Hi, Ivan, thanks for your response. We found that cause of data loss was in our code (incorrect datastreamer usage), so our favorite IMDG isn't responsible for it. Best regards, Sergey 20 февр. 2018 г. 19:04 пользователь "Ivan Rakov" написал: Sergey, Pages can't be

FINAL REMINDER: CFP for Apache EU Roadshow Closes 25th February

Hello Apache Supporters and Enthusiasts This is your FINAL reminder that the Call for Papers (CFP) for the Apache EU Roadshow is closing soon. Our Apache EU Roadshow will focus on Cloud, IoT, Apache Tomcat, Apache Http and will run from 13-14 June 2018 in Berlin. Note that the CFP deadline

Re: [Bug-7688] DDL does not working properly on sql queries

Hello, I added 'SQL' label to the ticket. I hope that SQL folks will take a look at this issue. In meanwhile, I will try to reproduce it on my side. Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite indexes and persistence

Yep. Four nodes running on ec2 with 2 gp2 ebs disks each (one for persistence and one for wal). Running loader on first node connecting to local host. The cache in question is using the data region included in this config included at the bottom. here is the query info: explain select count(*)