[
https://issues.apache.org/jira/browse/IGNITE-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376498#comment-16376498
]
Alexey Goncharuk commented on IGNITE-6083:
------------------------------------------
[~Alexey Kuznetsov], I like the second version of the test better. Note
however, that we must make sure that the EntryProcessor will never change the
entry value to a value based on some outdated cached entry.
Consider the following scenario:
T1:
Start tx, run cache.invoke(), the value is stored in TxEntry
T2:
run cache.put(), which overwrites the original value
T1:
run cache.invoke(), it received an old cached value
commit()
Can you please add a multi-threaded test verifying that in such a scenario the
second thread will get a proper optimistic conflict exception?
Also, please attach a link to a TC run.
Thanks!
> 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)
