You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2019/04/05 15:30:00 UTC
[jira] [Commented] (IGNITE-11684)
CacheSerializableTransactionsTest#testGetRemoveTxNearCache2 (and 1) is
flaky
[ https://issues.apache.org/jira/browse/IGNITE-11684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810938#comment-16810938 ]
Alexey Goncharuk commented on IGNITE-11684:
-------------------------------------------
[~ibessonov], the change looks legit to me, good job on finding this one! Is the TC bot happy with the changes?
> CacheSerializableTransactionsTest#testGetRemoveTxNearCache2 (and 1) is flaky
> ----------------------------------------------------------------------------
>
> Key: IGNITE-11684
> URL: https://issues.apache.org/jira/browse/IGNITE-11684
> Project: Ignite
> Issue Type: Test
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4876515758596068461&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
>
> Problem occurs when two optimistic&serializable transactions are being executed from the same client with near cache, when one of transaction removes key and another updates.
> In this scenario near node can be removed from "readers" list if "remove" transaction was completed before "update" transaction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)