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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/01/11 16:09:39 UTC

[jira] [Updated] (IGNITE-1321) Revisit PlatformAbstractTask locking logic.

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

Vladimir Ozerov updated IGNITE-1321:
------------------------------------
    Fix Version/s:     (was: 1.6)

> Revisit PlatformAbstractTask locking logic.
> -------------------------------------------
>
>                 Key: IGNITE-1321
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1321
>             Project: Ignite
>          Issue Type: Task
>          Components: interop
>    Affects Versions: 1.1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>
> Currently it is implemented with RW lock to ensure that task cannot be cancelled/completed concurrently when notie platform process job result. 
> This was done when we were dealing with non-unique native pointers.
> Now this is not a problem because we use "handle registry" approach and all "pointers" are guaranteed to be unique. Therefore, probably we can get rid of this lock at all.



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