[infinispan-issues] [JBoss JIRA] (ISPN-3518) 1PC can cause a window of inconsistency with L1 invalidation

[William Burns (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930412#comment-12930412 ] 

William Burns commented on ISPN-3518:
-------------------------------------

[~rvansa], the problem this was solving was more an issue where the same user could see a different value in a new tx even though their old one committed it.  I believe the use case was more around when a user could find invalid data if it executes another tx on a different node right after.  I think I discussed this with [~mircea.markus], he may remember more.
                
> 1PC can cause a window of inconsistency with L1 invalidation
> ------------------------------------------------------------
>
>                 Key: ISPN-3518
>                 URL: https://issues.jboss.org/browse/ISPN-3518
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache
>    Affects Versions: 5.3.0.Final
>            Reporter: William Burns
>            Assignee: William Burns
>            Priority: Critical
>              Labels: 620
>             Fix For: 6.0.0.Final
>
>
> The L1TxInterceptor currently doesn't block on L1 invalidations during a 1PC.  This can cause an inconsistent view of data across non owner nodes.
> Example:
> {quote}
> Node A owns k with value of v1
> Node B has k in L1 with value of v1
> tx1 started
> Node A put k -> v2
> Node A sends invalidation
> Node A commits
> tx1 completed
> tx2 started
> Node B get k returns v1 from L1
> tx2 completed
> Node B gets invalidation for k
> tx3 started
> Node B get k remotely retrieves v2 from Node A
> tx3 completed
> {quote}
> We need to make sure that all L1 invalidations in Tx mode are completed before completing the transaction.

--
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