[
https://issues.apache.org/jira/browse/IGNITE-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378680#comment-16378680
]
Alexey Kuznetsov edited comment on IGNITE-6083 at 2/27/18 5:27 PM:
-------------------------------------------------------------------
[~agoncharuk] Hi!
In current master branch I came across odd behavior, consider the following
scenario:
T1:
Start optimistic READ_COMMITTED tx, run cache.invoke(); // This cache invoke
fetches the key from primary node and stores into tx entry. This Invoke doesn't
change the value.
T2:
run cache.put();// which overwrites the original value;
T1:
run cache.read();// Here and futher old value will be returned, because of
invoke() called above.
commit();
In this scenario we have no Non-Repeatable Reads, which seems incorrect for
READ_COMMITTED isolation mode.
Do you agree ? If yes, I will file another new ticket, fixing it.
Also, I run the test in PESSIMISTIC mode, it fails. Need more fixes
was (Author: alexey kuznetsov):
[~agoncharuk] Hi!
In current master branch I came across odd behavior, consider the following
scenario:
T1:
Start optimistic READ_COMMITTED tx, run cache.invoke(); // This cache invoke
fetches the key from primary node and stores into tx entry. This Invoke doesn't
change the value.
T2:
run cache.put();// which overwrites the original value;
T1:
run cache.read();// Here and futher old value will be returned, because of
invoke() called above.
commit();
In this scenario we have no Non-Repeatable Reads, which seems incorrect for
READ_COMMITTED isolation mode.
Do you agree ? If yes, I will file another new ticket, fixing it.
> Null value have appear in the entry processor, but the entry is existing
> ------------------------------------------------------------------------
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.1
> Reporter: Vladislav Pyatkov
> Assignee: Alexey Kuznetsov
> Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}}
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at
> second.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
