ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-3601) Read-only optimistic transaction shouldn't throw an exception if entry version was not changed.
Date Mon, 01 Aug 2016 14:12:20 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexei Scherbakov updated IGNITE-3601:
--------------------------------------
    Description: 
Concurrent read only transactions reading the same key throw unexpected IgniteTxOptimisticCheckedException.


They shouldn't do what because entry version was not changed.

See the reproducer in the attachment.

  was:
Read only transactions reading the same key may throw unexpected IgniteTxOptimisticCheckedException
on contending commit.

We should detect what transaction is read only and not acquire any locks in what case.

See the reproducer in the attachment.

        Summary: Read-only optimistic transaction shouldn't throw an exception if entry version
was not changed.  (was: Read-only optimistic transaction should not acquire locks.)

> Read-only optimistic transaction shouldn't throw an exception if entry version was not
changed.
> -----------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3601
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3601
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexei Scherbakov
>             Fix For: 1.8
>
>         Attachments: Test.java
>
>
> Concurrent read only transactions reading the same key throw unexpected IgniteTxOptimisticCheckedException.

> They shouldn't do what because entry version was not changed.
> See the reproducer in the attachment.



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

Mime
View raw message