[ https://issues.jboss.org/browse/ISPN-4949?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-4949: ----------------------------------- {quote} I don't like your use of the word reliable; it suggests view installation is unreliable, which is not true. View installation is reliable, but failure detection itself is unreliable and will always be. There is no way to write a reliable failure detection in an asynchronous messaging system [1]. In other words, when the failure detection thinks a member has failed, a new view will be installed reliably (but without consensus).{quote} OK, poor choice of words, let's use rather 'confirmed view'. {quote} I think according to the semantics implied by your use of the term reliable view installation, you cannot install a view unless you get an ack from all members in it. So in order to install view 1-50, you'd have to get an ack from members [1..50]. If a single member, e.g. 32, doesn't ack the view, you cannot install that view. In this case, I think retrying to get 50 acks until all acks have been received or a new view is to be installed would probably be best. {quote} Sure, if 32 does not ack within the timeout, you'd send [1..31,33..50] and wait for the 49 acks. So, can we expect this in JGroups (under JGRP-1901), or should it rather be implemented in Infinispan? ([~dan.berindei], what's your status on this?) -- This message was sent by Atlassian JIRA (v6.3.8#6338)