Hi Maxim,
we are facing the exact same problem :(
Is it ok/safe to remove cacheGroupName from the code that is already been
created on nodes? If so, when we start our applications from the updated
code will we be still have access to same caches or new caches will be
created on nodes?
-
Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-11953
вт, 2 июл. 2019 г. в 11:17, Maxim Pudov :
> There is a known issue with cache groups which lead to
> CorruptedTreeException. Try to remove
> cacheCfg.setGroupName(groupName);
> from your configuration. I'll check whether JIRA
There is a known issue with cache groups which lead to
CorruptedTreeException. Try to remove
cacheCfg.setGroupName(groupName);
from your configuration. I'll check whether JIRA ticket was created or not
for this problem.
ср, 26 июн. 2019 г. в 04:17, SamsonLai :
> Yes they are created using JAVA
Yes they are created using JAVA API. The JAVA version is 1.8 and please find
below the code we used to create and get the caches. Thanks.
private IgniteCache getIgniteCache(String cacheName, String
groupName){
CacheConfiguration cacheCfg = new CacheConfiguration();
I don't see cacheConfiguration in the provided snippet. Do you create it
dynamically? What is your usage pattern? How do you use your cache? SQL,
cache API?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
>From the stacktrace I can tell that there is a problem with an index in your
cache. It's hard to tell more from the stacktrace itself. Could you share
the cache config as well?
In the next release (probably 2.8) such exceptions will be better explained
in the logs
Hello
We are using Apache Ignite 2.7.5 and we encountered the following in our
ignite. After this error occurred, it seems that the cache have been
corrupted and when we try to access this cache, the same errors occurred. We
also encountered this error with Apache Ignite 2.7.0.
The errors seems
