Re: Tuning parameters for performance of ignite Persistence store

Hi, I have tried settings you have mentioned for WAL, it improves performance in case of WAL write. But when check pointing process starts(default - after 3 mins), caching process slows down(almost stops). Is there any way by which we can write checkpoint to disk in background, so that

OOM in Heap though offHeap is available/free

Hi, I am using onHeap along with the default offHeap memory in my Ignite 2.0 server nodes. I am getting out of memory error even though there is enough memory available offHeap. My understanding (based on my earlier posts) is that onHeap is just a cache for offHeap. If that's how it works then

Re: Platform updates

Hi Luqman, I meant the service deployment. Most likely, you will do this in init() method - just call Class.forName() and create the instance of the class. Makes sense? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-tp15998p16069.html

Re: Query about running SQL with durable memory

On Sat, Aug 5, 2017 at 10:17 PM, iostream wrote: > Suppose I have 10 Person entries in the disk, out of which only 5 are > in-memory. Now if I run a SQL query which is expected to count the number > of > entries in Person cache, will the query run only on the disk or RAM

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

java 1.7.0_67 definitely has this issue with ignite 1.9, 2.0 and 2.1. We do not see this issue with java 8 On Tue, Aug 8, 2017 at 6:56 AM, Evgenii Zhuravlev wrote: > I tried your code with java 1.7.0_80-b15 and everything works fine. > > Also, check that you use right

Re: Streaming test

Jessie, What do you mean by "stuck"? Did you check thread dumps? Is it possible you have memory/GC issues? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p16066.html Sent from the Apache Ignite Users mailing list archive at

Re: Ignite behaving strange with Spark SharedRDD in AWS EMR Yarn Client Mode

IgniteContext does not create any executors, Spark does. And frankly I don't know why you have so many, I was not able to reproduce it myself. As for large number of tasks, only assumption I can make is that your cache doesn't actually have any data, which forces Spark to scan ALL partitions to

Re: GA Grid (Beta): Genetic Algorithm component for Ignite is here!

Thanks, Turik, very interesting! On Mon, Aug 7, 2017 at 8:58 PM, techbysample wrote: > Igniters, > > Check out the new GA Grid(Beta) project here: > > https://github.com/techbysample/gagrid > > GA Grid (Beta) is a distributive in memory Genetic Algorithm (GA) component > for

Re: Streaming test

Val, I replace atomicSequence with atomicLong and used the method below. I need to specify an initial value, start, according to requirement. return ignite.atomicLong( "id", // name. start, // Initial value true // Create if it does not exist. ); But the

Re: Tuning parameters for performance of ignite Persistence store

When you add persistence, latency of each individual updates gets bigger, because you update disk as well. In case you test on the same amount of parallel threads, throughput will obviously go down. However, if you increase the load, i.e. execute more operations in parallel, throughput will go

Re: Ignite behaving strange with Spark SharedRDD in AWS EMR Yarn Client Mode

Thanks for your reply Val. We tried that, now it stopped spinning up several servers, all of those became clients now (I still dont know the difference). But still just for a single row rdd it takes several minutes to retrieve it. It still spins up 100s of executor even though i specify 1

Re: Ignite suitable for jobs returning fairly large data sets ?

Hello, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send an empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Ignite can cope with such cases but it's highly

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

I tried your code with java 1.7.0_80-b15 and everything works fine. Also, check that you use right config file - you provided a file with name ignite-config.xml.xml, but in the code, you use ignite-config-login.xml. Evgenii 2017-08-08 16:44 GMT+03:00 Evgenii Zhuravlev

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Even disabling TLS/SSL doesn't have any effect. Moving to Java 1.8 is not an option as we have other dependencies which are incompatible with 1.8. Any other suggestion? Regards, Ankit Singhai -- View this message in context:

Re: Tuning parameters for performance of ignite Persistence store

Hi, You could try tuning persistence store update reliability vs. performance trade-opff by setting walMode to: DEFAULT: every update is flushed to disk (sync). Least performant but survives power loss. LOG_ONLY: OS-managed buffered output (write). Survives process crash but not OS crash.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

I would suggest updating to the last version of java and check if it will work. I can't reproduce same behavior with your code, but I use java 1.8.0_121-b13. Please share results after updating. Evgenii 2017-08-08 15:28 GMT+03:00 Ankit Singhai : > PFA log. No luck even by

Re: I am not able to read mxbean values of ignite

Hello, The reason whyr mxbean is false that Apache Ignite "exports" its own beans as DynamicBean. I've tried logstash 5.5.1 with logstash-input-jmx 3.0.2 plugin I've used the following jmx configuration that is gathering simple statistics about MyTestCache, DiscoverySpi and CommunicationSpi: {

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

Hi, I tried to run your code on Linux, but everything works fine for me. One thing - I don't see SSL configuration in your config files, while your log contains information that SSL was enabled. Is the same behavior reproducible without SSL? Also, I see that you use both ipv4 and ipv6, possibly

Re: ignite visor not workin in case ignite is started from a tomcat

Hi Alexey Thanks, we found the issue. We were not giving port in config xml through which we were connecting ignitevisor Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-visor-not-workin-in-case-ignite-is-started-from-a-tomcat-tp16043p16045.html

Re: ignite visor not workin in case ignite is started from a tomcat

Hi! Can you prepare a simple project to reproduce the issue? Also please specify versions of Ignite and Tomcat. On Tue, Aug 8, 2017 at 1:18 PM, neerajbhatt wrote: > Hi All > > We have a web application deployed in tomcat, from which we are starting > ignite server >

ignite visor not workin in case ignite is started from a tomcat

Hi All We have a web application deployed in tomcat, from which we are starting ignite server It seems in this scenario ignite visor is not able to detect ignite instance. In case we start ignite from a java class(not through tomcat), ignite visor is able to connect to ignite and give cache

Re: I am not able to read mxbean values of ignite

mxbean in MBeaninfo of a particluar cache is coming as false, because of which logstash jmx plugin is not able to get data. I am also facing the same problem we have used cacheCfg.setStatisticsEnabled(true); cacheCfg.setManagementEnabled(true); Attributes values are coming in jconsole but