[
https://issues.apache.org/jira/browse/IGNITE-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-12779:
--------------------------------------
Fix Version/s: 2.9
> 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
> 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) Add _IgniteMXBean#state(String state, boolean force)_.
> 2) Let _IgniteMXBean#state(String state)_ and _IgniteMXBean#active(boolean
> active)_ fail when deactivating cluster with in-memory data.
> 3) Separate implementations _Ignite_ and _IgniteMXBean_ from
> _IgniteKernal_. They have same method _void active(boolean active)_ which is
> required with different behavior. In case of _Ignite#active(boolean active)_
> it should not fail when deactivating cluster with in-memory data.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
