Oh, that is great. I wasn't aware of that. Thanks for the link!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
You can have some caches persistent and some not persistent, by having
several DataRegions some of whose have persistenceEnabled=true and some are
not, and specifying DataRegion by name in cache configuration.
Please see
Yes, we have a similar reluctance to use persistent store. Ouruse case is
that Gigs of data will be running through it with several caches that we
don't necessarily want to keep around in a docker environment. Some caches,
however, we would like persistent. Is there a plan to have persistence
Thanks. We'll give Native Persistence another try.
Our reluctance to use it stems from the fact that if something goes wrong
with the storage then there are additional production processes required to
recover - bad persistent store can cause the cluster to fail to start or
else propagate
> In my case, I have configured swap storage
> (https://apacheignite.readme.io/docs/swap-space) but *not* Ignite durable
> memory. If DataRegion maxSize is say 100GB and my physical RAM is 50GB
> then
> the swap file will be 100GB but Ignite will also use some portion (<50GB)
> of
> the
Or is it necessary to use the OS to enforce this? For example using ulimit -d
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks for the responses. To summarise:
* JVM Heap (Xmx) - Not normally used by Ignite for caching data.
* MaxDirectMemorySize - Used by Ignite for some file operations but not for
caching data. As per above, 256m is usually sufficient.
* DataRegion maxSize - Used by Ignite to determine how much
We’re actually looking into off-heap memory usage of ignite now, specifically
into the MaxDirectMemorySize needed.
So far it seems that MaxDirectMemorySize=256m should work. It may need to be
larger if you use non-default walSegmentSize.
Not limiting the direct memory size may result in
Hi summasumma,
> Means, i should have minimum 16 Gb of RAM (8 dataregion+ 8 directmem) for
> Ignite to run properly i guess.
Not quite. Actually, I am not aware that Ignite requires some special
tuning of MaxDirectMemorySize. If direct memory causes OOME then the
exception message usually points
Thanks Ivan.
This means having both configuration as follows:
xml-->
jvmption --> "-XX:MaxDirectMemorySize=8g"
Means, i should have minimum 16 Gb of RAM (8 dataregion+ 8 directmem) for
Ignite to run properly i guess.
In my current setup i have 16GB of total ram and given 12GB=maxSize
Hi summasumma,
DataRegion maxSize and jvm MaxDirectMemorySize are completely different.
Ignite DataRegion uses offheap memory allocated with help of Unsafe.
And that memory is not related to "direct memory" which jvm allocates
when direct buffers are used (e.g. ByteBuffer.allocateDirect). To
Hi collnc,
Perhaps, documentation can answer you question [1].
[1] https://apacheignite.readme.io/docs/durable-memory-tuning
2018-12-21 20:39 GMT+03:00, summasumma :
> In the above example,
>
> is setting "
> "
> in xml config file same as adding a jvmoption "-XX:MaxDirectMemorySize=8g"
> ?
>
In the above example,
is setting " "
in xml config file same as adding a jvmoption "-XX:MaxDirectMemorySize=8g" ?
or its different?
Can somone please clarify?
Thanks
...summa
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Is there any alternative way to constrain max physical RAM that Ignite uses?
My use case is to constrain physical RAM usage in a shared environment,
while allowing a relatively generous allocation of swap storage. I'm aware
of Ignite persistence, but believe that swap storage might meet our needs
Hi Ankit,
No, Ignite uses sun.misc.Unsafe for offheap memory. Direct memory may be
used in DirectBuffers used for intercommunication. Usually defaults quite
enough.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi All,
Do we require to set MaxDirectMemorySize JVM parameter on IgniteServer to
make use of OFFHEAP?
For an example to make use of 8 GB off heap should I add MaxDirectMemorySize
if yes then how much
16 matches
Mail list logo
