RHDG Expiration reaper is not removing any expired entry when using programatic set expiration

Solution Verified - Updated -

Issue

  • Expired entries are not removed if checking the number-of-entries attribute via CLI/JMX, if the size() funtion for the cache is invoked this number is different and seems correct
  • If the API is used to set lifespan for expiration the entries are not removed from the cache until a get for this key is invoked, what is the reason for this?
  • Getting OutOfMemory problems and it seems the expired entries are not removed

Environment

  • Red Hat Data Grid (RHDG)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content