Re: slow query performance against berkley db

Hi Rajesh, Ignite is a distributed system, testing with one node is really not the way. You need to consider having multiple nodes and portion and collocate your data before. Thanks, C > On 5 Feb 2018, at 16:36, Rajesh Kishore wrote: > > Hi, > > We are in the

Re: Computation best practices

Hi Luqman, Is there a specific reason why you want to keep the data nodes separate from the compute nodes? As you say this beats the point of collocation. You should use the data nodes for compute and ensure you have a way to monitor and kill spurious tasks that may be executed on the grid.

Re: Platform updates

Luqman, do you want to update the application or the actual Ignite version? If it's your application Kara then as long as you can manage multiple versions of your app for a phased upgrade then sure. But if it's for Ignite then this is not possible to have 2 different version running in the same

Apache Flink meets Apache Ignite next week in London

ttps://www.meetup.com/Apache-Flink-London-Meetup/events/239663941/ <https://www.meetup.com/Apache-Flink-London-Meetup/events/239663941/> We hope to see you there! Cheers, Christos

Apache Ignite vs. Apache Flink - a worthy comparison?

Igniters, I'm looking at a use case where I've been challenged to position Ignite vs. Flink. I know at a high-level these technologies target different use cases and can actually compliment each other it's still possible to have overlapping functionality. Anyone care to share their views on how

Re: Distributed Closures VS Executor Service

Hi Kyriako, Thinking about your original approach of using compute tasks assigned to nodes with all CATEGORIES required by the task to be local, I believe you could use the affinity interface to figure this out. You'd need to partition your CATEGORIES cache and use the CATEGORY ID as the

Re: Distributed Closures VS Executor Service

If I understand correctly, the SQL query is executed within every task on each of the nodes and it is not set to be a local query. Correct? If so then what you are really doing is executing the SQL queries from all the nodes to all the nodes. This is bound to be inefficient. In essence what you

Re: Non-collocated distributed SQL Joins across caches over separate cluster groups

would be almost the same... Christos -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Non-collocated-distributed-SQL-Joins-across-caches-over-separate-cluster-groups-tp11734p11748.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Distributed Closures VS Executor Service

to be collocated to ensure they end up on the same server. Then you can use an affinity run or broadcast with local query enabled to only execute the query locally. Now in your case you said the data is in an external database so I’m not sure how you would ensure the data for each query is local. Christos

Non-collocated distributed SQL Joins across caches over separate cluster groups

API would not allow this and requires caches to be located on all nodes when the JOIN query is executed? Cheers, Christos

Re: Success story sharing

Hi walagi, thats great to know. Can you share more about the use case so I can understand better? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Success-story-sharing-tp11557p11614.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Distributed Closures VS Executor Service

> - The application server-side queries the DB, finds the products belonging > to the selected categories, performs calculations (applies the metrics on > them etc.) and persists the results in the database for future reference So if I understand this correctly you are not loading any data from

Re: Distributed Closures VS Executor Service

should insert data into the cache with a certain affinity and then use an affinity run compute task to send the job to the correct node. Have a read here: https://apacheignite.readme.io/docs/affinity-collocation If you share more on your use case I should be able to help you! Regards, Christos

4th Apache Ignite Meetup London hosted by IHS Markit on the 23rd of February

ache-Ignite-London/events/237189063/ <https://www.meetup.com/Apache-Ignite-London/events/237189063/> We look forward to seeing you there! Best, Christos

Re: Official Apache Ignite meetup - Sept. 22nd - London

ny new content we post. Cheers! Christos > On 16 Sep 2016, at 09:28, Christos Erotocritou <chris...@gridgain.com> wrote: > > We will try to stream the event live. But we will certainly share the video > and slides following the meetup. > > On Friday, 16 September 2

Re: Official Apache Ignite meetup - Sept. 22nd - London

We will try to stream the event live. But we will certainly share the video and slides following the meetup. On Friday, 16 September 2016, Alexey Kuznetsov <akuznet...@gridgain.com> wrote: > It is possible to see slides or even meetup video? > > 16 Сен 2016 г. 14:09 пользов

Ignite Download links broken

Hey guys, The links on the website seem to be broken, can someone check this? https://ignite.apache.org/download.html#binaries <https://ignite.apache.org/download.html#binaries> Thanks, Christos

Ignite & Kubernetes

Hi all, Is anyone working with Ignite & kubernetes? Moreover I’d like to understand how it would be possible to do auto discovery of new Ignite nodes. Thanks, Christos

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Ah, I realise now that this FAQ you are talking about is probably more of a dev one where as the one I’ve created is more product focused. Christos > On 11 Mar 2016, at 18:20, Christos Erotocritou <chris...@gridgain.com> wrote: > > We already have a basic FAQ page which

Re: Apache Ignite is how to ensure the data's consistency between multiple server？

If you use full sync mode for backups, then the client node will wait for write or commit to complete on all participating remote nodes (primary and backup). This is the most restrictive configuration but will guarantee data consistency. In addition if you use transactions for any grid