L1 inconsistency in tx caches when backup owner replies to remote get --------------------------------------------------------------------- Key: ISPN-3426 URL: https://issues.jboss.org/browse/ISPN-3426 Project: Infinispan Issue Type: Bug Affects Versions: 6.0.0.Alpha2 Reporter: Pedro Ruivo Assignee: William Burns Labels: jdg620_dm, jdg62GAblocker Consider the following scenario {noformat}node1: performs a remote get node2 (backup owner): receives and replies to the remote get with v1 node1: receives the repli and store in L1_ key => v1 node2 (backup owner): commits a new value (v2) for the key (i.e. processes a commit command) node3 (primary owner): sends the invalidation (but not for node1 because it hasn't received the remote get yet) and commits a new value (v2) for the key (i.e. processes a commit command) node3 (primary owner): replies to the remote get with v2 node1: ignores the reply because it used the node2 reply {noformat} *conclustion*: node1 keeps the old value stored in L1. Possible solutions described here: [L1 consistency for transactional caches|http://markmail.org/thread/ckbihuj5ch7qtdzj] Could also be interesting: [Staggered get question|http://markmail.org/thread/qun2frj2u5a2hnj2] and [ISPN-825|https://issues.jboss.org/browse/ISPN-825]