Re: Ignite JDBC connection pooling mechanism

We solved the problem by removing the complete hikari connection pooling mechanism. Instead we use IgniteJdbcThinDataSource ( https://apacheignite-sql.readme.io/docs/jdbc-driver) , with appropriate client connector configuration( https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite

Re: Nodes failed to join the cluster after restarting

Sorry, I see that you use TcpDiscoverySpi. ср, 18 нояб. 2020 г. в 10:44, Ivan Bessonov : > Hello, > > these parameters are configured automatically, I know that you don't > configure them. And with the fact that all "automatic" configuration is > completed, chances of seeing the same bug are low.

Re: Nodes failed to join the cluster after restarting

Hello, these parameters are configured automatically, I know that you don't configure them. And with the fact that all "automatic" configuration is completed, chances of seeing the same bug are low. Understanding the reason is tricky, we would need to debug the starting node or at least add more

Failed to prepare update plan error while inserting data, when select is used aong with insert

Hi, Using ignite thick client, i'm trying to copy data from one table into another table using following sql statement "INSERT INTO desttable (name, lastname, age) (SELECT name, lastname, age from srctable)" I'm getting the following error while i run sql query. "Failed to prepare update plan."

not in, not exists sql result is not correct

Hi, We are using ignite 2.8.1, with this sql statement, SELECT * FROM orders p WHERE NOT exists (SELECT accountid FROM account b WHERE b.accountid = p.accountid); Retured result accountid actually exists in table account, change to NOT IN also is not correct. But I have another table result is

Re: Nodes failed to join the cluster after restarting

Hi, The parameters values on two other nodes are the same. Actually I do not configure these values. When you enable the native persistence, you will see these logs by default. Nothing is special. When this error occurs on the restarting node, nothing happens on two other nodes. When I restart the

Re: Live coding session next week

That was really fun! We should definitely repeat in January or February. Thanks for participating! Video: https://youtu.be/RsqeIaQfSpc Project: https://github.com/vkulichenko/code-session Article about data distribution in Apache Ignite: https://www.gridgain.com/resources/blog/data-distribution-in

Re: Thin Client connection not working...

Hi, sorry for the late reply but it was getting too late yesterday evening... Below you can find the code from the Apache Ignite Website that I tried without successfully getting a connection to the Ignite Server Node... Just to mention. I had both (the thin client and the server) running on

What is considered high IO wait and partition exchange fiallure?

So if I understand correctly the logs below... The node that shut off was timing out trying to get partition exchange from the indicated nodes and it shut itself off correct? Does this mean this node was also the master? 1- The time indicated in the log is that UTC? 2- I'm trying to see if it was

What is considered high IO wait and partition exchange failure?

So if I understand correctly the logs below... The node that shut off was timing out trying to get partition exchange from the indicated nodes and it shut itself off correct? Does this mean this node was also the master? 1- The time indicated in the log is that UTC? 2- I'm trying to see if it was

Re: Eviction policy enablement leads to ignite cluster blocking, it does not use pages from freelist

Hi Evgenii, Later investigations, we found that this is happening due to the near-cache "rdrs" not released from entries i.e. GridDhtCacheEntry objects. When near-cache entry is getting evicted from a ignite-client node; it is not clearing the rdrs from Server. Due to these rdrs not empty, the en

Query on CVE-2020-5421

Hi, Is the CVE-2020-5421 applicable to Ignite ? I have a doubt whether it is applicable to only spring-web package (https://mvnrepository.com/artifact/org.springframework/spring-web) or to all the springframework packages. Regards, Vishwas

Re: On disk compression

If you have a write-heavy workload, to reduce disk usage you can also compress WAL (see "WAL compaction" and "WAL page snapshots compression" features). I'm not sure about ZSTD compression levels, you can try it. But there is a warning in the ZSTD manual: "Levels >= 20 should be used with caution,

Re: Nodes failed to join the cluster after restarting

Thank you for the reply! Right now the only existing distributed properties I see are these: - Baseline parameter 'baselineAutoAdjustEnabled' was changed from 'null' to 'false' - Baseline parameter 'baselineAutoAdjustTimeout' was changed from 'null' to '30' - SQL parameter 'sql.disabledFunctio

Re: How to get column names for a query in Ignite thin client mode

Thank you Ilya Regards, Shravya Nethula, BigData Developer, [cid:2d89cf9f-aa3f-4a88-aea2-70b3dfe9cb3e] Hyderabad. From: Ilya Kasnacheev Sent: Wednesday, November 11, 2020 7:46 PM To: user@ignite.apache.org Cc: Bhargav Kunamneni Subject: Re: How to get colu

Re: On disk compression

Aha! I didn't know about the sparse file thing. Thanks! # ll -hs 159M -rw-r--r-- 1 ignite ignite 339M Nov 16 21:32 part-96.bin So the real space used is only 159M. That's great. I currently have all of this data stored on the filesystem in csv.gz files using 177M of space for the 16000 I tested