Re: slow query performance against berkley db

Further to this, I am re-framing what I have , pls correct me if my approach is correct or not. As of now, using only node as local cache and using native persistence file system. The system has less number of records around *.1 M *in main table and 2 M in supporting table. Using sql to retrieve

Re: How to identify stale ignite client in case of data grid restart and auto reconnect to cluster

Hi, This exception says that client node was stopped, but by default it should wait for servers. In other words, wait for reconnect, in this case it throws IgniteClientDisconnectedException that contains future on which you may wait for reconnect event. You may locally listen for EventType.EVT_CLI

Join us for the inaugural gathering of the London In-Memory Computing Meetup!

https://www.meetup.com/London-In-Memory-Computing-Meetup/events/246875000/ Wednesday, February 7, 2018 6:30 PM to 9:00 PM Bloomsbury House 74-77 Great Russell Street WC1B 3DA

Re: Design help implementing custom counter on ignite

Hi, Transaction here might be a not optimal solution, as it by default optimistic and may throw optimistic transaction exception. I believe the best solution would be to use EntryProcessor [1], it will atomically modify entry as on TRANSACTIONAL as on ATOMIC cache on affinity data node (that actua

Apache Ignite Transactions Architecture: Failover and Recovery

Igniters, Akmal Chaudhri has a new blog post headlined, "Apache Ignite Transactions Architecture: Failover and Recovery .” Summary: Various types of cluster failures can occur at a number o

Re: Get TTL of the specific (K,V) entry

Created a ticket for this improvement: https://issues.apache.org/jira/browse/IGNITE-7641 -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Design help implementing custom counters on ignite

I would also recommend to take a look at EntryProcessor [1]. It allows to do co-located atomic updates, so it doesn't require transaction and reduces the amount of data transferred across network, so it should give best performance results. [1] https://apacheignite.readme.io/docs/jcache#entryproce

Re: slow query performance against berkley db

Hi All Please help me in getting the pointers, this is deciding factor for us to further evaluate ignite. Somehow we are not convinced with just . 1 m records it's not responsive as that of Berkley db. Let me know the strategy to be adopted, pointers where I am doing wrong. Thanks Rajesh On 6 Fe

Ignite survey: contribute to the project evolvement and win gift cards

Igniters, Please take part in the survey prepared by a couple of community members: https://www.surveymonkey.com/r/IgniteSurvey18 What’s the purpose? We want to know how Ignite is used, what it’s loved for and how we can make it better. Some of y

Re: slow query performance against berkley db

Hi Rajesh, Please allow the community some time to test your code. As far as testing single node vs. distributed, when you have more than one node, Ignite will split your data set evenly across multiple nodes. This means that when running the query, it will be executed on each node on smaller dat

Re: slow query performance against berkley db

Hi Dmitry, Thanks a ton. What is not convincing to me is with just *.1 M in main table and* *2 M records in other table * , sql query is taking around 24 sec, that is worrisome. In local cache mode , I tried both using partitioned and non partitioned mode , the result is same. All I wanted to kn

Enable Kerberos on Ignite Kafka streamer / support for new consumer config

Hi, We are trying to enable Kerberos in our Ignite-Kafka env. Kerberos is supported in Kafka consumers using the newer consumer configs. As per Kafka documentation, Kerberos is only supported on the newer KAfka consumers. It seems the Ignite KafkaStreamer only supports using the old consumer conf

Text Query question

Hi, I'm using Ignite Persistence and Text Query in my project. but I got a problem. here is the steps: 1. put some data into IgniteCache, and with Persistence opened, then use TextQuery to get result。 2. restart the system, after Ignite is ready, use TextQuery to get the same resul