]
Bela Ban reopened JGRP-2167:
----------------------------
OK, I'll take another look.
Highest seqno is not resent nor recorded on receivers
-----------------------------------------------------
Key: JGRP-2167
URL:
https://issues.jboss.org/browse/JGRP-2167
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Radim Vansa
Assignee: Bela Ban
Fix For: 4.0.3
I am investigating an issue in a stress test which leads me to a situation where in a
TCP-based configuration a {{GMS[VIEW]}} is broadcast to all nodes, but it is not received
by some of them. Soon after that there's a {{NAKACK2.HIGHEST_SEQNO}} that causes the
node that is missing the last seqno to resend it, but the retransmit is not received
either. There are no further retries, and generally no NAKACK2 activity until about 30
seconds later (when another node leaves after some timeout in the test).
The receiver does not keep asking for retransmissions until it gets them, but it seems
that {{NAKACK2.handleHighestSeqno}} doesn't update {{Table.hr}} (not sure if having
highest received set to non-received msg would be legal, though).
The sender uses default value {{NAKACK2.resend_last_seqno_max_times=1}}, and as there are
no further mcast messages, the highest sent seqno does not change on sender.