]
William Burns commented on ISPN-4979:
-------------------------------------
Looking into jboss marshalling code closer they assume we do the object reference checks
when using a custom ObjectTable. I will need to add some logic to replicate that. I am
not sure if having a registry of long lived values like in the example Sanne gives as this
requires clearing thise periodically or having to have some kind of hook to tell it to be
cleared at some point
CacheStatusResponse map uses too much memory
--------------------------------------------
Key: ISPN-4979
URL:
https://issues.jboss.org/browse/ISPN-4979
Project: Infinispan
Issue Type: Bug
Components: Core, State Transfer
Affects Versions: 7.0.0.Final
Reporter: Dan Berindei
Assignee: William Burns
Priority: Critical
Fix For: 7.1.0.Final
When the cluster is large and there are a log of caches, the {{CacheStatusResponse}} map
on the new coordinator can get quite large. One of the problems that seems to be that the
addresses in {{DefaultConsistentHash}} are duplicated on serialization, so the
deserialized version occupies more memory.
We need to investigate why the objects are not "shared" by the River
marshaller, and maybe work around the problem by de-duplicating the addresses in the
externalizer.