Details
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.
Attachments
Issue Links
- is a clone of
-
IGNITE-12810 [IEP-39] Management API to cancel compute tasks.
- Resolved
- links to