You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2020/04/01 14:03:00 UTC
[jira] [Commented] (IGNITE-12813) [IEP-39] Management API to cancel
scan queries.
[ https://issues.apache.org/jira/browse/IGNITE-12813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072798#comment-17072798 ]
Anton Vinogradov commented on IGNITE-12813:
-------------------------------------------
[~nizhikov],
LGTM
> [IEP-39] Management API to cancel scan queries.
> -----------------------------------------------
>
> Key: IGNITE-12813
> URL: https://issues.apache.org/jira/browse/IGNITE-12813
> 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:
> * scan queries
> 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)