[
https://issues.apache.org/jira/browse/IGNITE-18533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676913#comment-17676913
]
Ignite TC Bot commented on IGNITE-18533:
----------------------------------------
{panel:title=Branch: [pull/10478/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10478/head] Base: [master] : New Tests
(22)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Queries 3 (lazy=true){color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=6999090]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
KillCommandsSQLTest.testCancelClientConnection - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
KillCommandsMXBeanTest.testCancelClientConnection - PASSED{color}
{color:#00008b}Control Utility 1{color} [[tests
18|https://ci2.ignite.apache.org/viewLog.html?buildId=6997584]]
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelUnknownService - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelUnknownSQLQuery - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelScanQuery - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelUnknownContinuousQuery - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelTx - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelConsistencyTaskSequential - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelComputeTask - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelUnknownComputeTask - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelContinuousQuery - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelService - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelSQLQuery - PASSED{color}
... and 7 new tests
{color:#00008b}Queries 3{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=6997626]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
KillCommandsSQLTest.testCancelClientConnection - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
KillCommandsMXBeanTest.testCancelClientConnection - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6997654&buildTypeId=IgniteTests24Java8_RunAll]
> [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
> Time Spent: 1h
> 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)
