Re: Abrupt stop of application on using sql

Hi Ilya, we could find out the problem of the application stop. We see "Buffer Overflow" error when application stops. We commented out mCache.Put() in our code(basically not calling Put API to write data to DB) and the restart did not happen. Also this restart happens after a certain number of

Re: Fastest way to iterate over a persistence cache

Hi Sebastian. You can try to use QueryParallelism feature, also try to use LazyLoading feature. More details is here: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/sql-tuning Thanks, Ilya ср, 14 апр. 2021 г. в 02:28, Sebastian Macke : > Hi Ignite Team, > > I have stumbled

Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Hi, * Tested with:* - Ignite version - 2.10.0 - Multinode cluster on single/different JVM - localhost - First node successfully starts, shared memory endpoint also starts but cluster formation fails moving ahead and is indefinitely stuck at GridCachePartitionExchangeManager - Failed to wait for

Re: Re: SQL query performance with JOIN and ORDER BY or WHERE

Wow, that seems to do the trick. When forcing the index use on the column that I order by the query returns within milliseconds instead of >40 seconds!I‘ll do more tests but so far it looks like you are right, this helps significantly:USE

Fastest way to iterate over a persistence cache

Hi Ignite Team, I have stumbled across a problem when iterating over a persistence cache that does not fit into memory. The partitioned cache consists of 50M entries across 3 nodes with a total cache size of 3*80GB on the volumes. I use either a ScanQuery or a SQL query over a non-indexed

Re: reading encrypted password from Ignite config file

I wrote a blog about this: https://www.gridgain.com/resources/blog/managing-apache-ignite-secrets-hashicorp-vault Regards, Stephen > On 13 Apr 2021, at 18:31, shivakumar wrote: > > Hi Ilya, > if I have

Re: reading encrypted password from Ignite config file

Hi Ilya, if I have to use username/password is it possible to implement SecurityCredentialsProvider.java interface? https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/plugin/security/SecurityCredentialsProvider.java is there any example for this ? regards,

Re: Java Thin Client: Continuous Queries

Yes, it is in master and will be included in the next release (2.11). There is no release date yet, but I think it should happen in Q3 or Q4. On Tue, Apr 13, 2021 at 6:56 PM ssansoy wrote: > Hi, I saw the changes for this were in the master branch? Is there a rough > release date for this by

Re: Java Thin Client: Continuous Queries

Hi, I saw the changes for this were in the master branch? Is there a rough release date for this by any chance? https://issues.apache.org/jira/browse/IGNITE-14402 Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Is Geo redundancy supported in Ignite

Hello! There is a third-party solution for geo-redundancy based on Apache Ignite. But as X Guest said, no native support in Apache Ignite. Regards, -- Ilya Kasnacheev пн, 12 апр. 2021 г. в 16:20, vbm : > Hi, > > Is geo-redundancy supported in Ignite ? > > Can we bring up 2 clusters in

Re: SQL query performance with JOIN and ORDER BY or WHERE

Hi, Please try to enforce use index for sorted select. It make sense when filter produce a lot pf results. So, full table will be scanned by ordered index, but result will be not materialized on map nodes. Using the example of the first message, it looks like this: SELECT JQ._KEY FROM

Re: Is Geo redundancy supported in Ignite

I am afraid it does't support it this time. On Mon, Apr 12, 2021, at 9:20 PM, vbm wrote: > Hi, > > Is geo-redundancy supported in Ignite ? > > Can we bring up 2 clusters in different location(geo) and make one cluster > as backup for another ? > Basically can ignite cluster in different