You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Dmitriy Sorokin (JIRA)" <ji...@apache.org> on 2018/07/17 16:50:00 UTC

[jira] [Updated] (IGNITE-9024) Wrong usage of idxLatch in DynamicIndexAbstractConcurrentSelfTest

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

Dmitriy Sorokin updated IGNITE-9024:
------------------------------------
    Summary: Wrong usage of idxLatch in DynamicIndexAbstractConcurrentSelfTest  (was: Wrong usage of IdxLatch in DynamicIndexAbstractConcurrentSelfTest)

> Wrong usage of idxLatch in DynamicIndexAbstractConcurrentSelfTest
> -----------------------------------------------------------------
>
>                 Key: IGNITE-9024
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9024
>             Project: Ignite
>          Issue Type: Test
>    Affects Versions: 2.5
>            Reporter: Dmitriy Sorokin
>            Assignee: Dmitriy Sorokin
>            Priority: Minor
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.7
>
>
> DynamicIndexAbstractConcurrentSelfTest has BlockingIndexing inplementation which allows synchronize indexing operations with other concurrent routines. Transition to waiting for unblock indexing state being notified from awaitIndexing method by countDown() call on idxLatch, which should be awaiting on test thread, but calls of countDown() method on idxLatch instances are present in that code points too.
> Replace of countDown() calls by await() calls on idxLatch instances is needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)