You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/10/08 10:23:26 UTC

[jira] [Commented] (IGNITE-582) [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction

    [ https://issues.apache.org/jira/browse/IGNITE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948262#comment-14948262 ] 

Semen Boikov commented on IGNITE-582:
-------------------------------------

This issue should be fixed when IGNITE-1607 is implemented.

> [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction
> ------------------------------------------------------------------
>
>                 Key: IGNITE-582
>                 URL: https://issues.apache.org/jira/browse/IGNITE-582
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Artem Shutak
>            Assignee: Semen Boikov
>            Priority: Blocker
>              Labels: Muted_test
>             Fix For: ignite-1.5
>
>
> Ticket is related to this issue http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions.
> I added more simple test to the GridCacheTxMultiThreadedAbstractTest. 
> Original test is also attached to the ticket. Sometimes commit fails with GridCacheTxOptimisticException, but two threads still can commit duplicated values so that increment is lost.
> see GG-8063
> Next test(s) should be unmuted on TC: testOptimisticSerializableConsistency



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)