[
https://issues.jboss.org/browse/ISPN-4979?page=com.atlassian.jira.plugin....
]
William Burns edited comment on ISPN-4979 at 11/18/14 12:38 PM:
----------------------------------------------------------------
-Looking closer the simple serialization change won't actually work it appears that
the consistent hashes stored all have different instances of JGroupsAddress so they
don't have instance equality which is needed for serialization reuse checks. I will
also need to check why these are not the same.-
This was caused by the UPDATE_CH command sending alone the CH and it wasn't properly
serializing the addresses, so that just needed a tweak as well and it has reduced my very
simple case to half usage of memory. Note that this is not indicative of each case as the
number of caches, segments & owners increase the effect will become larger and larger.
If I can find a way to merge the Response info between then this would also scale better
with the number of nodes.
was (Author: william.burns):
Looking closer the simple serialization change won't actually work it appears that the
consistent hashes stored all have different instances of JGroupsAddress so they don't
have instance equality which is needed for serialization reuse checks. I will also need
to check why these are not the same.
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.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)