Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

Lazy is something which we can use when we are expecting huge result set to minimize the memory consumption at the cost of little performance hit. However my requirement to run a query by joining couple of tables with complex where clause to debug some data related issues, this query may not

Ignite Client Heap out of Memory issue

Hi,My Ignite client heap OOM yesterday.  This is the first time we encounter this issue.My ignite client colocates within Storm worker process. this issue cause storm worker restart.I have several questions about it: our ignite version is 2.3.01) if ignite in client mode, it use

Re: Unable to connect ignite pods in Kubernetes using Ip-finder

Guys, Thanks for reporting and sharing the resolution. We'll update Ignite Kubernetes deployment doc: https://issues.apache.org/jira/browse/IGNITE-8081 -- Denis On Tue, Mar 27, 2018 at 10:10 AM, lukaszbyjos wrote: > I have the same problem on GKE with 2.4. I found some

Re: Upgrade from 2.1.0 to 2.4.0 resulting in error within transaction block

Another update.. I changed the code (shown at the beginning of this thread) that deletes records from: SqlFieldsQuery sqlQuery = new SqlFieldsQuery("delete from EngineFragment where " + criteria()); fragmentCache.query(sqlQuery.setArgs(criteria.getArgs())); to: _fragmentCache.remove(id);

Re: how to organize groups in cluster?

Hi Andrew, Thank you for the response. 1. yes, I will try this way to build sub caches 2. yes, make sense. 3. I tested EvictionPolicy, it seemed to be not available in ignite 2.0+, please refer to my earlier discuss (with denis)

Re: how to organize groups in cluster?

Hi Val, Here's the background: I'm thinking about creating message pipelines right in ignite cluster. it's a nightmare to save data in a centralized cache and run everything on it, so my whole idea is to guarantee *none-blocking process* and scalable consumers. 1. (producer) put real-time

Re: Upgrade from 2.1.0 to 2.4.0 resulting in error within transaction block

I neglected to say that I also removed Spring's ChainedTransactionManager and used SpringTransactionManager in the annotation, which also resulted in the same stack trace.. @Transactional("igniteTxMgr") // code that deletes from cache... // Here is how the transaction manager is wired up..

Re: How to insert multiple rows/data into Cache once

Hi, Try to use DataStreamer for fast cache load [1]. If you need to use SQL, you can try to use bulk mode updated via JDBC [2] Also a COPY SQL command [3] will be available in next 2.5 release. The feature is already in master, you can try to build from it. See example [4] . [1]

Error while activating the ignite cluster.

Im trying to activate the cluster while loading data into ignite cache. It is hanging forever. Im found below logs in /Ignite_Home/work/logs/***.log Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=d8b1c981, uptime=03:22:00.946] ^-- H/N/C [hosts=2, nodes=2,

Re: Basic terms in Ignite

Thanks Dave for very informative reply. I will come back with some more questions Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

Hi Naveen, You can try a 'lazy' flag for query. It is available from ignite-2.4 that has been released recently. See SqlFieldQuery javadoc [1] and JDBC doc [2] for details. [1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/SqlFieldsQuery.html#setLazy-boolean-

How to insert multiple rows/data into Cache once

Dear all, I am trying to use the SqlFieldsQuery sdk to insert data to one cache on Ignite. I can insert one data into one cache at a time. However, I have no idea to insert multiple rows/data into the cache once. For example, I would like to insert 1000 rows/data into the cache once. Here, I

Re: how to organize groups in cluster?

Hi, 1. NodeFilter can be used [1] to bound cache to certain data nodes. 2. You can subscribe to cache updates via ContinuousQuery [2]. But keep in mind, ContinuousQuery listener is called from sensitive code and it is usually bad idea to make blocking operations in it. 3. To keep only TOP N