You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2023/01/14 14:39:00 UTC
[jira] [Updated] (IGNITE-18533) [IEP-39] Management API to kill client connection
[ https://issues.apache.org/jira/browse/IGNITE-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikolay Izhikov updated IGNITE-18533:
-------------------------------------
Fix Version/s: 2.15
> [IEP-39] Management API to kill client connection
> -------------------------------------------------
>
> Key: IGNITE-18533
> URL: https://issues.apache.org/jira/browse/IGNITE-18533
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Major
> Fix For: 2.15
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Ignite provides thin client API.
> Thins client has many APIs that allocate resources on the server nodes.
> 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 drop any user connection
> JMX beans to cancel listed tasks should be introduced:
> * Client connections (THIN, ODBJ, JDBC)
> 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.20.10#820010)