As far as I know, “multi-tier” refers to the ability to store some data in
memory, the rest on disk.
You experienced “split brain,” which is a difficult problem to solve in any
distributed system. From your description my guess is that you’ve enabled
baseline auto-adjust, which is generally not
> manually specify the QueryEntity queryable fields and indexes in the
CacheConfiguration
No need to do that.
Just add those calls before ignite.GetOrCreateCache:
ignite.GetBinary().GetBinaryType(typeof(TKey));
ignite.GetBinary().GetBinaryType(typeof(TValue));
(substitute actual type names as
Hi Pavel,
Thanks for the clarification and for filing a ticket!
Yes, I'm using a CacheConfiguration with a QueryEntity, like
CacheConfigurationconfiguration= newCacheConfiguration(cacheName,
newQueryEntity(typeof(TKey), typeof(TValue)))
{
}
I tried to manually specify the QueryEntity queryab
Dear,
One of the "Core Features" listed by ignite.apache.org is the capability
of Ignite to be a Multi-Tier Storage. However, unless I have
misunderstood something, I am worried that this storage is not reliable...
I currently have an application that uses an Ignite cluster as a DB. The
clus
Hi Emilio,
This is a bug, I've filed a ticket:
https://issues.apache.org/jira/browse/IGNITE-15845
What does the config look like? You have some QueryEntity defined, am I
right?
I think a workaround is to register QueryEntity types manually before
creating the cache:
ignite.GetBinary().GetBinaryT
Hi,
Since we started using MassTransit Ignite struggles when creating or
getting a cache using ignite.GetOrCreateCacheTValue>(configuration). Ignite exits after the error has been triggered.
The relevant error I guess is
Failure in Java callback Apache.Ignite.Core.Common.IgniteException:
Inv
