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

Ignite TC Bot commented on IGNITE-12810:
----------------------------------------

{panel:title=Branch: [pull/7555/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5152531&buildTypeId=IgniteTests24Java8_RunAll]

> [IEP-39] Management API to cancel compute tasks.
> ------------------------------------------------
>
>                 Key: IGNITE-12810
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12810
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: IEP-39
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ignite provides many API to deploy and execute user-provided code on the 
> server nodes inside the same JVM as the Ignite process runs.
> Ignite has many APIs that allocate many resources on the server nodes, also. 
> In case of some buggy code that consumes many system resources(CPU, RAM, 
> flood network) or heavy query the whole cluster can become unstable.
> We should provide to the cluster administrator the ability to stop any user 
> deployed task.
> JMX beans to cancel listed tasks should be introduced:
> * Compute task
> In the scope of IEP-35 System view API introduced.
> A new API should use the same identifier that is used in corresponding System 
> View.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to