This issue is definitely web-oriented. It's about the 'Content-Disposition'
custom HTTP header which raised a big deal of concerns about security itself
over time. As far as I currently understand it affects only web part(s) of
Spring, more particularly spring-webmvc. It's not being used by Ignite.
Hi,
I don't think it's related to the discovery. In the log, before OOM you can
see the long JVM pause:
Possible too long JVM pause: 2323 milliseconds.
So, probably you used more heap memory than you had.
What version do you use? How much heap memory do you have? What do you do
with a cluster(S
Hi,
Any pointers on what the below error means.
There seems to be an out of memory on discoverySPI. what can cause this?
^-- TxLog region [used=0MB, free=100%, comm=100MB]
^-- Ignite persistence [used=50071MB]
^-- sysMemPlc region [used=0MB]
^-- default region [used=50071MB
Hi community,
Although there is a transactional cache, no transaction operation is
performed, but there is a lot of output below in the log. Why?
[2020-11-16 14:01:44,947][INFO ][sys-stripe-8-#9][IgniteTxManager]
Checking optimistic transaction state on remote nodes [tx=GridDhtTxLocal
[nearN
Thanks Ilya, for the explanation.
So, to recap,
data always resides in off heap, but it can be configured to reside to on
heap as well.
You define eviction policy on regions to evict the data from on heap, but
it won't affect the off heap.
You define expiry policy at cache level to remove data fro
Hi,
I have created a sample reproducer using examples files. I am using ignite
2.8.0 version.
Here I have updated server configurations in ExampleNodeStartup.java, and
client configurations in CacheClientBinaryPutGetExample.java files.
Server is configured with eviction-enabled, and client is co
