Re: Near cache configuration for partitioned cache

Hi, between first test with near cache configured in xml and configuring near cache via java code i cleaned data. But why should I clean data on server nodes when I add near cache only on client nodes to gain performance? Now I am testing ignite so I could do this, but it won't be acceptable when r

RE: [External]Re: Exporter usage of Ignite 2.8.0

Thanks for the update Anton. Have some queries as below: 1. How do we feed the Ignite cluster data which is exposed on JMX port to custom exporter given on (https://opencensus.io/exporters/supported-exporters/java/prometheus/) ? 2. If we move opencensus lib to $IGNITE_HOME/libs/

java.sql.SQLException: Schema change operation failed: Thread got interrupted while trying to acquire table lock.

Hello. I am testing ignite 2.8.It sometimes throws following exception: java.sql.SQLException: Schema change operation failed: Thread got interrupted while trying to acquire table lock. at org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:901) at org.apac

Re: Re: RE: Re: Unsafe usage of org.h2.util.JdbcUtils in Ignite

Hello! I have never seen a stack trace like this one. Can you provide a reproducer for this behavior? Regards, -- Ilya Kasnacheev пт, 20 мар. 2020 г. в 20:20, Andrey Davydov : > Hello, > > Current implementation is really unsafe for multiple Ignite in same JVM. > In tests for our system when

RE: Re: Re: RE: Re: Unsafe usage of org.h2.util.JdbcUtils in Ignite

When I got OutOfMemory and become research heapDumps, I have found some bugs and leaks not only in Ignite but in our code too. So I already implement some fixes in our system, and I don’t see this error more. May be it was because of our logic (we register/unregister drivers too). So if I get it ag

Re: Ignite memory leaks in 2.8.0

Hello! I have filed an issue about this: https://issues.apache.org/jira/browse/IGNITE-12837 Please feel free to contribute or draw attention to it. Regards, On 2020/03/18 15:37:26, Andrey Davydov wrote: > Hello, > > > > There are at least two way link to IgniteKernal leaks to GC root and

Re: Near cache configuration for partitioned cache

Dominik, This cache was already created in the cluster with Near Cace for all nodes. Once created, this configuration can't be changed, so, it's needed to clean persistence data or just destroy the cache and create it without Near Cache in configuration. After this, you can dynamically add Near ca

Re: No ignitevisorcmd.sh in Ignite 2.8

Hello! We hope to ship a fix for it in 2.8.1: https://issues.apache.org/jira/browse/IGNITE-12757 Until then, you can apply recommendation from the linked thread. Regards, -- Ilya Kasnacheev вт, 24 мар. 2020 г. в 14:10, joaogoncalves : > Hi again > > It happened to be the same as Thank you f

Application fails to boot under Ignite 2.8

Hi, I have setup a Ignite Server Node with the following configuration default-config.xml And I also put together a demo Spring Boot application, to the Ignite Server Node as follow (config below is the same) When

Re: Application fails to boot under Ignite 2.8

Hi, It looks like some information wasn't added to the message, for example, spring boot configuration. Can you please attach the code with Spring boot(xxx.Application)? It would be great if you could share small reproducer. Thanks, Evgenii ср, 25 мар. 2020 г. в 11:10, aveiros : > Hi, > > I ha