[
https://issues.jboss.org/browse/JGRP-1638?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1638:
--------------------------------
I changed this in 3.4: I reverted to sending STABILITY message unreliably, but clearing
the 'votes' set before sending that message. This has the advantage that we
don't need NAKACK{2,3} to retransmit STABILITY messages, reduces the number of STABLE
and STABILITY messages (measured ca. 10% less), and we don't possibly block on
reception of a STABILITY message if that message was the last message sent.
Memory leak when STABLE.send_stable_msg_to_coord_only=true
----------------------------------------------------------
Key: JGRP-1638
URL:
https://issues.jboss.org/browse/JGRP-1638
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Critical
Fix For: 3.3.1, 3.4
Running MPerf with conf/fast-local.xml (2 members on the same host, 20 million messages
each) creates a memory leak in 3.4.x.
This runs perfectly 3.2.8.Final, so it must be something that was introduced in 3.3.x
(3.4.x at this time has almost no diffs to 3.3.0.Final).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira