ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Isaeed Mohanna <isae...@gmail.com>
Subject Re: Cache Memory Behavior \ GridDhtLocalPartition
Date Wed, 23 Nov 2016 13:20:43 GMT
Hi Again,
In addition to the datastructures_0 that is growing which is not a cache
that i have created.

Through JMX to my EventsCache mentioned above where retained memory reside
i can see using the CacheLocalMetricsMXBeanImpl the following attributes:
KeySize 403
Size 403
TxCommittedVersionsSize 129819
TxRolledbackVersionsSize 129819

They keysize and size attributes seem to be changing correctly up and down
according to the generated and processed events, however
the TxCommittedVersionsSize & TxRolledbackVersionsSize seem to be accumulating.
could you please elaborate on what are these attributes from the name i
assume they are related to transactions but my cache is atomic (not
transactional) is it possible that removed entries are remembered for some
reason in some transaction log?


On Wed, Nov 23, 2016 at 3:00 PM, Isaeed Mohanna <isaeedm@gmail.com> wrote:

> Hi
> i did call the name method and i got "datastructures_0" which is not a
> cache that i have created.
> the size count now is at 13.5k, I am using an ignite queue, is it possible
> that this is created internally by ignite for the queue or some internal
> ignite cache?
> Thanks
> On Wed, Nov 23, 2016 at 2:40 PM, dkarachentsev <dkarachentsev@gridgain.com
> > wrote:
>> Hi,
>> To get to know what cache represents CacheMetricsMXBean you can call
>> name()
>> method of it. And yes, it's worth to check if that entries cause your
>> problem.
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Cache-Memory-Behavior-GridDhtLocalPartition
>> -tp8835p9149.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message