[ https://issues.jboss.org/browse/JGRP-2167?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2167: -------------------------------- The problem with setting {{resend_last_seqno_max_time}} to a high value optimizes for a case that almost never happens, and causes unnecessary traffic and thread activity (in most cases). The last view lost will eventually be delivered, when either (1) the view sender sends another multicast or (2) STABLE kicks in. However, (1) might never happen and (2) takes time, based on STABLE's configuration. There are ways to improve this, but I'm not sure I like any of them: 1. Have the last message sender task get acks for its highest seqno from all cluster members 2. Let the receiver continue asking the sender for retransmission until it gets that last seqno, or until higher seqnos from the sender are seen #1 causes additional traffic that's a function of the cluster size and the frequency of sending. E.g. if a sender sends a multicast every 2 seconds, this most likely (depending on the xmit_interval config) causes another multicast to be sent (last-seqno), plus N unicast acks to be received. This also duplicates part of the functionality of STABLE. #2 If the last-seqno message is lost, this won't help. Also, it leads to (unicast) unnecessary traffic as well. I think the best solution in such an edge case is to reduce the timeouts in STABLE itself and let it run its course. -- This message was sent by Atlassian JIRA (v7.2.3#72005)