Hi Aaron,
I was wrong saying that copyOnRead=false consumes heap, it's not.
> if Reside in heap queue and more than batchSize, will those data be
lost before DB recover?
Yes, if your store throwing exceptions, and flushQueue is full you may
start losing updates, but there will be warning in logs.
There should not be so many GridLocalCacheEntry instances. Could you
find the neares roots for them in dump?
Thanks!
-Dmitry.
25.08.2017 12:21, [email protected] пишет:
Thanks Dmitry!
At very begin we did not specify the copyOnRead; I remember in another
thread you suggest us to set to false to save memory?
JavaDoc: "Also if this flag is set copies are created for values
passed to {@link CacheInterceptor} and to {@link CacheEntryProcessor}."
Also if set this flag to true will the read have to read from
off-heap? will this meaning be slower?
if Reside in heap queue and more than batchSize, will those data be
lost before DB recover?
Thanks for your time!
Reards
Aaron
------------------------------------------------------------------------
[email protected]
*From:* dkarachentsev <mailto:[email protected]>
*Date:* 2017-08-25 15:33
*To:* user <mailto:[email protected]>
*Subject:* Re: Re: In which scenario the ignite nodes will
shutdown by itself
Hi Aaron,
If data could not be stored to DB, they will reside in heap queue,
but no
more than batchSize.
I see you set copyOnRead to false, this property forces ignite to keep
object on-heap, why do you need it?
Thanks!
-Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/In-which-scenario-the-ignite-nodes-will-shutdown-by-itself-tp16192p16418.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
