Re: Spring Data native Query support

It’s possible to pass an Ignite native query to a method but you might need to configure the repository differently. Please check this documentation: https://apacheignite-mix.readme.io/docs/spring-data Denis On Wednesday, October 30, 2019, niamin wrote: > Does Ignite provide native Query suppo

Re: Cluster in AWS can not have more than 100 nodes?

There is no hard limit of this kind, here is the source code of the IP finder: https://github.com/apache/ignite/blob/master/modules/aws/src/main/java/org/apache/ignite/spi/discovery/tcp/ipfinder/s3/TcpDiscoveryS3IpFinder.java You can enable DEBUG level for Discovery and the IP Finder to collect mo

Re: High CPU(70-80%) utilization with single Ignite node

Hello, There might be many reasons that cause the CPU utilization spikes. I would approach it debugging from bottom-up - by checking application, virtual machine, and OS levels: - Application: - Are there any blocking calls, do clients create similar keys or compete for shared reso

Re: TransactionOptimisticException: Failed to prepare transaction, read/write conflict

This is not supposed to happen if a record is not updated in parallel. Could you prepare a reproducer? In general, an optimistic transaction fails if any of the records within a transaction gets modified concurrently. - Denis On Thu, Oct 31, 2019 at 8:46 AM Prasad Bhalerao < prasadbhalerao1...@

Re: Ignite cache partition size

It's best to have the number of partitions being a power of two, so better to go with 32768 I think. There are big clusters with hundreds of nodes out there, and they do use large partition numbers sometimes - as large as 16k or 32k. Note that it will bring some overhead on the metadata being stor

Re: Query execution in ignite

This is not exactly correct. When you do an SQL query with only PARTITIONED tables, or with a mix of PARTITIONED and REPLICATED, the data will be taken from the primary partions of PARTITIONED tables and *all* partitions of REPLICATED tables. When you do an SQL query with only REPLICATED tables, th

Re: Throttling getAll

The right answer to this is probably not to use getAll in such cases. If you want to load data in batches then you should either split the keys yourself or use Query APIs, like ScanQuery or SqlQuery. Stan On Mon, Oct 28, 2019 at 10:36 PM Abhishek Gupta (BLOOMBERG/ 919 3RD A) < agupta...@bloomberg

Re: Drop index do not release memory used ?

Hi, What version do you use? There was an issue with recycling pages between data and indexes which has been fixed in 2.7 https://issues.apache.org/jira/browse/IGNITE-4958. In AI 2.7 and later this should be working fine. Stan On Sat, Oct 26, 2019 at 5:22 PM yann Blazart wrote: > Yes the data

Apache Ignite on Apache Con

Hi, Igniters, I've presented a new topic "Ensembles of ML algorithms and Distributed Online Machine Learning with Apache Ignite" on ApacheCon in Berlin this year. Video is here https://www.youtube.com/watch?v=3CmnV6IQtTw Slides are here https://speakerdeck.com/zaleslaw/ensembles-of-ml-algorithms-a

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

Hi, Sounds like a bug. Would be great to have a ticket with reproducer. пт, 1 нояб. 2019 г. в 03:25, mvkarp : > > > > I've attached an Eclipse MAT heap analysis. As you can see MVCC is disabled > (there are no TRANSAC

Re: Issue with adding nested index dynamically

Hi Hemambara, I appologize but I will be able to share a problematic example only on next week. чт, 31 окт. 2019 г. в 19:49, Hemambara : > > I did not face any issue. Its working fine for me. Can you share your code > and exception that you are getting > > I tried like below and it worked for me.

Re:

That is up to you, you can use anything you want, the most obvious choice would be the built in attributes feature in Ignite configuration:                   You will find a lot of information under the "Affinity Function" and "Affinity Key