[
https://issues.jboss.org/browse/JGRP-1461?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1461:
--------------------------------
No, we cannot remove seqnos: multiple threads in C could forward seqnos 1,4,3,5,2 to A and
A would likely send the broadcasts in that order.
So either we order the received seqnos (but how do we know which seqno is the first?), or
we have the coordinator assign a global seqno (but how does the sender re-send if the
coord crashes ?)
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