Hello!
This is the first time such problem is observed, so maybe your case is very
uncommon for some reason.
Ignite has a thing called "free list" which helps plug holes in Durable
Memory pages normally.
Regards,
--
Ilya Kasnacheev
пт, 28 сент. 2018 г. в 18:40, Serg :
> Hi,
>
> I have
Hi,
I have changed my data model and the problem is gone.
But look like I should be care with data which I upload and will be nice to
know which data I can use, maybe I missed smth in docs about data
preparation?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
It is still a problem for you? I can see slight decrease of fill factor on
your chart coupled with slight increase of data region usage. With regards
to fragmentation it is to be expected.
I have tried your test:
15:04:54,356 INFO [grid-timeout-worker-#23]
Metrics for local node (to
Hello Ilya,
I have found that cause of problem the objects which have different size of
data.
As result I have situation where pageFillFactor increased and offHeapSize is
decreased and this trend never end.
Grafana screen:
Hello!
So I was increasing amount of RAM in the memory model, and it turns out
that Off-Heap usage will not grow past:
2018-09-11 12:47:46,603 INFO [pub-#290] log4j.Log4JLogger
(Log4JLogger.java:566) - #
2018-09-11 12:47:56,605 INFO [pub-#292]
Hi Ilya,
I created reproducer with two tests
https://github.com/SergeyMagid/ignite-reproduce-grow-memory
Differents in this tests only is data which inserted to cache.
I have previously suppose that problem caused with BinaryObject only but I
reproduced this problem without BinaryObject too.
Hello!
There's a WAL reader somewhere in the code, it could help if you have
persistence. Note that both invocation and output of this tool is confusing.
It would be nice if you had a reproducer which would show this behavior.
The snippet that you have posted previously isn't very clear on
Hi Ilya,
Yes growing not so quick but in production we lost near 1GB every day with
15GB of data on each node.
I had simplify data classes by remove annotations and this does not help.
Is it possible debug off-heap memory? How I can understand where memory
goes?
--
Sent from:
Hello!
I have ran your test and I don't observe any off-heap growth:
[18:17:14,655][INFO ][grid-timeout-worker-#24%ignite.GrowTest0%][GrowTest0]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=23ad15f7, name=ignite.GrowTest0, uptime=00:00:40.015]
^-- H/N/C
Hi All
We have got a problem with growing off-heap on each sync data.
*Precondition *
We have ignite in memory cache. with key Integer and value Contact
Each hour we sync full data in cache via api cache.put(key, value); (cache
full load)
Also we have increment update via the api cache.put(key,
10 matches
Mail list logo