[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061681#comment-17061681
]
Ignite TC Bot commented on IGNITE-12779:
----------------------------------------
{panel:title=Branch: [pull/7531/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=5124971&buildTypeId=IgniteTests24Java8_RunAll]
> Split implementations of Ignite and IgniteMXBean, make behavior of their
> active(boolean) different
> ---------------------------------------------------------------------------------------------------
>
> Key: IGNITE-12779
> URL: https://issues.apache.org/jira/browse/IGNITE-12779
> Project: Ignite
> Issue Type: Sub-task
> Affects Versions: 2.8
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure in-memory
> data we should:
> 1) Set IgniteMXBean.active(false) and IgniteMXBean.state("inactive") throwing
> an exception if deactivation would clear in-memory data.
> 2) Extract IgniteMXBean from IgniteKernal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
