[
https://issues.jboss.org/browse/ISPN-83?page=com.atlassian.jira.plugin.sy...
]
Manik Surtani edited comment on ISPN-83 at 3/19/11 5:40 AM:
------------------------------------------------------------
For 4.2.x, FLUSH will still be used and tested for (ConfigurationException thrown if FLUSH
is not in your JGroups stack) UNLESS you pass in a system property:
{{-Dinfinispan.experimental.transport.skip_flush_check=true}}
Note that this is new system property is only available in snapshots and releases *after*
4.2.1.CR4. 4.2.1.CR4 itself doesn't have this.
was (Author: manik):
For 4.2.x, FLUSH will still be used and tested for (ConfigurationException thrown if
FLUSH is not in your JGroups stack) UNLESS you pass in a system property:
{{ -Dinfinispan.experimental.transport.skip_flush_check=true }}
Note that this is new system property is only available in snapshots and releases *after*
4.2.1.CR4. 4.2.1.CR4 itself doesn't have this.
Remove dependency on JGroups FLUSH
----------------------------------
Key: ISPN-83
URL:
https://issues.jboss.org/browse/ISPN-83
Project: Infinispan
Issue Type: Task
Affects Versions: 4.2.0.Final
Reporter: Manik Surtani
Assignee: Vladimir Blagojevic
Fix For: 5.0.0.BETA1, 5.0.0.Final
FLUSH is needed to control messages not being sent when a new view is installed, as we
have observed that without this, messages get dropped by the joiner. We need to find a
better way to deal with this as FLUSH is expensive and not very scalable.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira