[
https://issues.jboss.org/browse/JGRP-1461?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1461:
--------------------------------
No, I don't think so: SeqnoTable.Entry maintained next_to_receive, which was set to
the first seqno received if entry was null. This means, if we deliver 7,5,6,
next_to_receive would be set to 7, and therefore, 5 and 6 would be discarded.
I think the only thing we can do here is to maintain a hashset of capacity N that is used
to check for dupes.
SEQUENCER leaks sequence numbers
--------------------------------
Key: JGRP-1461
URL:
https://issues.jboss.org/browse/JGRP-1461
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.9, 3.1
Reporter: David Hotham
Assignee: Bela Ban
Fix For: 3.0.10, 3.1
As noted in JGRP-1458, it looks as though SEQUENCER always thinks that sequence numbers
must start at zero. But a member who joins a group after some messages have already been
broadcast may never receive sequence number zero. So, I think, his SeqnoTable will grow
indefinitely.
Note that this one's mostly through code reading. I think I'm right; but I'm
happy to be told otherwise!
Pull request to follow shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira