[
https://issues.jboss.org/browse/ISPN-835?page=com.atlassian.jira.plugin.s...
]
John Ament commented on ISPN-835:
---------------------------------
Ok, to be honest, I'm a little shy to try out snapshots in code that we currently are
running in our QA environment, especially when it impacts app server builds. So for
myself, I'm just going to work under the assumption that a code change is required and
not currently in place (maybe will be in 6.0.1)? As a quick fix, could I back everything
that should be distributed via a file loader?
State transfer should not force all invocations to be synchronous
-----------------------------------------------------------------
Key: ISPN-835
URL:
https://issues.jboss.org/browse/ISPN-835
Project: Infinispan
Issue Type: Bug
Components: RPC, State transfer
Affects Versions: 4.1.0.Final, 4.2.0.CR4
Reporter: Galder ZamarreƱo
Assignee: Manik Surtani
Fix For: 5.0.0.BETA1, 5.0.0.Final
Attachments: stdout-hsqldb-node1.txt.zip, stdout-hsqldb-node2.txt.zip
Enabling state transfer is forcing even asynchronous caches to become synchronous.
A better way is needed to make sure state transfer works correctly (sync calls needed
here) while normal replication calls remain asynchronous.
See
https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
where the response mode is overridden based on whether replay is supported. And replay
support is always on when state transfer is enabled:
https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
Need to explore whether a joiner flag can be maintained based on a view change, and
replay only supported when a joiner is still "joining", and not otherwise.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira