[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12779:
-------------------------------------
Fix Version/s: (was: 2.10)
2.11
> 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.11
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> To make cluster deactivation through JMX without sudden erasure of 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.
> 3) Add IgniteMXBean.state(String, boolean)
> Additionally, as discussed, we should improve comments
> {code:java}
> /** If {@code true}, cluster deactivation will be forced. */
> {code}
> Let's add a link to a full description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
