[
https://issues.jboss.org/browse/JGRP-1895?page=com.atlassian.jira.plugin....
]
Dennis Reed commented on JGRP-1895:
-----------------------------------
Possible fix for the specific issue in my previous comment:
When handling FLUSH_NOT_COMPLETED, if flushCompleted is true (which will never be the case
if
the FLUSH_NOT_COMPLETED is for the current flush), then just ignore it.
FLUSH_NOT_COMPLETED race condition
----------------------------------
Key: JGRP-1895
URL:
https://issues.jboss.org/browse/JGRP-1895
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.16
Reporter: Dennis Reed
Assignee: Dennis Reed
FLUSH_NOT_COMPLETED does not keep track of which FLUSH it was related to.
FLUSH_COMPLETED only keeps track of whether the FLUSH was for the current view.
If these responses are delayed (which can be caused by a long GC pause on the node
sending it) where a new FLUSH has been started, these can be interpreted as responses for
the wrong FLUSH.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)