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 2017/10/18 09:00:02 UTC

[jira] [Updated] (IGNITE-6659) Check that public API is not called in sensitive system threads

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

Alexey Goncharuk updated IGNITE-6659:
-------------------------------------
    Description: 
We need to add a check that public (or semi-public) blocking API is not called from sensitive system threads.
For example, cache operations, service deploy must not be called in disco* threads, exchange-worker, system thread pool because this will cause a cluster-wide deadlock.

Need to consider which other threads and APIs are affected.

Any invalid call must throw an exception.

  was:
We need to add a check that public (or semi-public) blocking API is not called from sensitive system threads.
For example, cache operations, service deploy must not be called in disco* threads, exchange-worker, system thread pool.

Need to consider which other threads and APIs are affected.


> Check that public API is not called in sensitive system threads
> ---------------------------------------------------------------
>
>                 Key: IGNITE-6659
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6659
>             Project: Ignite
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>    Affects Versions: 2.2
>            Reporter: Alexey Goncharuk
>             Fix For: 2.4
>
>
> We need to add a check that public (or semi-public) blocking API is not called from sensitive system threads.
> For example, cache operations, service deploy must not be called in disco* threads, exchange-worker, system thread pool because this will cause a cluster-wide deadlock.
> Need to consider which other threads and APIs are affected.
> Any invalid call must throw an exception.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)