[
https://issues.jboss.org/browse/ISPN-2724?page=com.atlassian.jira.plugin....
]
Thomas Fromm commented on ISPN-2724:
------------------------------------
Mircea mentioned thats "Minor" issue, since L1 is filled within the 1st get() on
this key.
But I can't agree, in my case the data is stored and read directly after. (transaction
data during workflow processing) So in normal case the data is read once.
The cache is currently DIST_SYNC, to change it to DIST_ASYNC I need a working L1 to make
sure data is available shortly after put on the same node. (key affinity is not possible
there) putAsync(..) would maybe be a workaround. But I'd prefer the fix for L1.
L1 is not used for write-operations (for node affine keys)
----------------------------------------------------------
Key: ISPN-2724
URL:
https://issues.jboss.org/browse/ISPN-2724
Project: Infinispan
Issue Type: Bug
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.2.0.CR1
Reporter: Thomas Fromm
Assignee: Vladimir Blagojevic
Attachments: L1WriteTest.java
I need to make sure, that a key written on a node is present in L1, even when the owner
is a different node.
Attached an example which shows the expected behaviour.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira