Hi All,
When setting the defaultDataRegionConfiguration parameter in the
IgniteConfiguration, are the maxSize and initialSize values per-node or
cluster-wide?
Ex: specifying 16GB for the Default_Region.
Is the 16GB reserved on the node or reserved across the entire cluster?
The above error appears to be an issue in
org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot in a
mismatch between the readExternal() and writeExternal() methods.
I've made a change locally and it fixed the error and also the testing so
far seems to show that the queries return the c
Thanks Vlad / Dmitry, I was able to download the nightly build from teamcity
as a guest.
However I'm now getting the following error when trying to add data to the
cache. Any ideas?
class org.apache.ignite.IgniteException: Failed to get affinity mapping from
node: TcpDiscoveryNode [id=eeef1e32-db
The issue you mention doesn't seem to be related to the issue we are having
as,
- The entire grid does not lock up as in the situation described in the bug
- There are no threads blocked or locked when our key lock occurs
- The bug seems to occur on Optimistic locking whereas our scenario occurs
on
Hi,
We've had the multiple instances where a 16 node grid completely crashes
with the following error.
we use all our caches OFF HEAP caches in our configuration.
We are running Ignite 1.7 and running Java 1.8u60-b27 on Linux
Has anyone seen a similar issue?
Thanks
Yohan
I've attached a few
Unfortunately iam unable to send the full logs files but they contain the
following exceptions
[14 Sep 2016 11:14:30.290 EDT] [pub-#16%DataGridServer-Development%] ERROR
11223 (OrderHolderSaveRunnable.java:273) exception ocurred while generating
Trade Order for Order: OrderKey [traderId=5
207, or
No, the node that failed was a server node.
About the rollback, yes indeed. A few times that grid has hung, we have seen
a similar lock on rollback. Why would a transaction rollback impact the
topology?
This thread dump was taken at least 10 minutes after the node died so in an
ideal world, the g
Thanks for your reply Anmol. Do you know if there is a bug logged against
this which we can track?
Also it's not clear why the nodes would require to GC because all the caches
are held off-heap and we have a 10G heap running G1GC.
--
View this message in context:
http://apache-ignite-users.70
Hi Denis,
We have been able to reproduce this situation where a node failure freezes
the entire grid.
Please find the full thread dumps of the 5 nodes that are locked up.
The memoryMode of the caches are configured to be OFFHEAP_TIERED
The cacheMode is PARTITIONED
The atomicityMode is TRANSACTIO
