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 2015/09/02 09:59:46 UTC

[jira] [Commented] (IGNITE-264) Queue failover tests fail in transactional cache

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

Alexey Goncharuk commented on IGNITE-264:
-----------------------------------------

Found another issue with near enabled cache, related to ignite-910 (confirmed by Semyon, linked the ticket). Assertion happens because in one-phase commit DHT locks are released before near transaction commit and thus more than one near candidate might become marked as ready. Fixed this by releasing locks on primary node after committing transaction on near node.
After I made this fix I observed more hangs in portables test suite (added recently), need more time to investigate.

> Queue failover tests fail in transactional cache
> ------------------------------------------------
>
>                 Key: IGNITE-264
>                 URL: https://issues.apache.org/jira/browse/IGNITE-264
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: sprint-1
>            Reporter: Valentin Kulichenko
>            Assignee: Alexey Goncharuk
>             Fix For: ignite-1.4
>
>
> See {{GridCachePartitionedQueueFailoverDataConsistencySelfTest}}.



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