[
https://issues.apache.org/jira/browse/IGNITE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18084358#comment-18084358
]
Ignite TC Bot commented on IGNITE-28734:
----------------------------------------
{panel:title=Branch: [pull/13192/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13192/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Control Utility 1{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=9094229]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerManagementPoolTest.testManagementTasksWorksWhenClientPoolBlocked[cmdHnd=jmx]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerManagementPoolTest.testManagementTasksWorksWhenClientPoolBlocked[cmdHnd=cli]
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9094091&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9094091
rerunBuildIds=9095281,9095282{color}
> User operations can block management commands
> ---------------------------------------------
>
> Key: IGNITE-28734
> URL: https://issues.apache.org/jira/browse/IGNITE-28734
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have dedicated pool for management commands, all management tasks executed
> wihin this pool. But we've moved control.sh to thin client protocol, and when
> client-connector pool is busy (for example, by long-running SQL) management
> commands can't be processed. Recently we've also added default handshake
> timeout for thin clients, so control.sh can't even connect to cluster and got
> timeout exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
