[ https://issues.apache.org/jira/browse/IGNITE-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003135#comment-17003135 ]
Ignite TC Bot commented on IGNITE-12478: ---------------------------------------- {panel:title=Branch: [pull/7191/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4872657&buildTypeId=IgniteTests24Java8_RunAll] > Add long running operation timeout to MXBean for manipulate in run-time > ----------------------------------------------------------------------- > > Key: IGNITE-12478 > URL: https://issues.apache.org/jira/browse/IGNITE-12478 > Project: Ignite > Issue Type: Improvement > Reporter: Kirill Tkalenko > Assignee: Kirill Tkalenko > Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Previously we can change the timeout only through property > ({{IGNITE_LONG_OPERATIONS_DUMP_TIMEOUT}} default 60_000), but in a real > environment, we do not want to stop cluster (or node) for modify this > property. > We should have a MBean's property, which allow to fluent in run-time behavior > of printing LRT/LRF (like a property > {{SqlQueryMXBeanImpl#setLongQueryWarningTimeout}} which printing long running > queries). -- This message was sent by Atlassian Jira (v8.3.4#803005)