Re: java.lang.UnsupportedOperationException: Invalid fast index type: -21

Hi, I've added the same field to one of the objects in Ignite example and everything works fine. Can you share the full reproducer or at least the whole object? Thanks, Evgenii чт, 1 нояб. 2018 г. в 15:11, Yuriy : > I have made the index on bite[] field: > @QuerySqlField (index = true,

Dependency resource injection with OpenWebBeans CDI instead of Spring

Hi, I would like to configure Ignite to use OpenWebBeans and CDI to inject fields into deserialized IgniteRunnables instead of using Spring. It looks like  org.apache.ignite.internal.processors.resource.GridResourceInjector is available for this purpose. Is there an easy way to register a custom

RE: Is there Ignite Eviction low water mark

In Ignite 1.x vs 2.x, when we get notified about an eviction (from cache events), will Ignite literally delete the entry, or can they be remain for certain period and later get wiped out. The implementation of eviction from 1.x to 2.x is a different, new one? From: Denis Mekhanikov

Security Setup

I am trying to setup basic login and password. I have coded as below but getting an error as in the Ignite documentation. IgniteConfiguration cfg = new IgniteConfiguration(); // Ignite persistence configuration. DataStorageConfiguration storageCfg = new

Slow Data Insertion On Large Cache : Spark Streaming

Hi Team, We have 6 node Ignite cluster with 72CPU, 256GB RAM and 5TB Storage . Data ingested using Spark Streaming into Ignite Cluster for SQL and Tableau Usage. I have couple of Large tables with 200ml rows with (200GB) and 800ml rows with (500GB) . The insertion is taking more than 40secs

Re: Long activation times with Ignite persistence enabled

Naveen, 40 caches is quite a lot. It means, that Ignite needs to handle 40 * (number of partitions) files. By default each cache has 1024 partitions. This is quite a lot, and a disk is the bottleneck here. Changing of thread pool sizes won't save you. If you divide your caches into cache groups,

Re: Long activation times with Ignite persistence enabled

Hello In my case of slow startup, as suggested from a member of this mailing list, I deleted the -XX:+AlwaysPreTouch command line option from JVM launch, and the cluster got back to very fast startup. Don't know if you are using this option, hope it helps. Cheers Gianluca Il giorno lun 5 nov

Re: Long activation times with Ignite persistence enabled

Hi Denis We have only 40 caches in our cluster. If we introduce grouping of caches, guess we need to reload the data from scratch, right ?? We do have very powerful machines as part of cluster, they are 128 CPU very high end boxes and huge resources available, by increasing any of the below

Re: Is there Ignite Eviction low water mark

Hi! Ignite 2.x has a mechanism called page eviction . It's configured using DataRegion#pageEvictionMode

Re: Apache Ignite - Near Cache consistency

Correct. Strong consistency is guaranteed for atomic caches as well, including near cache entries. Denis пн, 5 нояб. 2018 г. в 11:21, ales : > Thanks Denis for the answer. > > Actually i am using "ATOMIC" atomicity mode (ie no transaction). > I have been told that it may be linked to the backup

Re: Apache Ignite - Near Cache consistency

Thanks Denis for the answer. Actually i am using "ATOMIC" atomicity mode (ie no transaction). I have been told that it may be linked to the backup synchronicity mode (FULL_SYNC would ensure consistency between nodes and eliminate stale data). -- Sent from: