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

2018-08-28 Thread Alexey Goncharuk (JIRA)


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

Alexey Goncharuk updated IGNITE-6659:
-
Fix Version/s: (was: 2.7)
   2.8

> 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
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> 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
(v7.6.3#76005)


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

2018-06-26 Thread Dmitriy Pavlov (JIRA)


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

Dmitriy Pavlov updated IGNITE-6659:
---
Fix Version/s: (was: 2.6)
   2.7

> 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
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7
>
>
> 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
(v7.6.3#76005)


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

2018-04-09 Thread Alexey Goncharuk (JIRA)

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

Alexey Goncharuk updated IGNITE-6659:
-
Fix Version/s: (was: 2.5)
   2.6

> 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
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.6
>
>
> 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
(v7.6.3#76005)


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

2018-01-17 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov updated IGNITE-6659:

Fix Version/s: (was: 2.4)
   2.5

> 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
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> 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
(v7.6.3#76005)


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

2017-10-18 Thread Alexey Goncharuk (JIRA)

 [ 
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)