[
https://issues.apache.org/jira/browse/IGNITE-12811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12811:
-------------------------------------
Description:
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:
* Services
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.
was:
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.
> [IEP-39] Management API to cancel services.
> -------------------------------------------
>
> Key: IGNITE-12811
> URL: https://issues.apache.org/jira/browse/IGNITE-12811
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Nikolay Izhikov
> Priority: Major
>
> 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:
> * Services
> 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)
