[IGNITE-12614] Disallow silent deactivation of cluster to prevent in-mem data loss.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9, 2.12
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Vladimir Steshin
• Reporter: Vladimir Steshin
• Created: 31/Jan/20 13:02
• Updated: 17/Feb/22 17:55
• Resolved: 17/Sep/21 11:43

Description

Currently, anyone is able to deactivate cluster with command line utility (control.sh). Probably with JMX too. That would lead to data loss when the persistence is off. In-memory data is erased during deactivation. Such behavior can be considered as unexpected to user.

Suggestions:

1) Disallow silent deactivation of cluster keeping caches. Show a warning like “Your cluster has in-memory cache configured. During deactivation all data from these caches will be cleared!”

2) Add param ‘--force’ which skips the warning message.

Issue Links

• causes: IGNITE-16579 Cluster deactivation can get stuck
• links to: GitHub Pull Request #7358
• links to: Link to discussion.

Sub-Tasks

• Disallow silent deactivation in CLI and REST.: Resolved
• Split implementations of Ignite and IgniteMXBean, make behavior of their active(boolean) different: Resolved
• Fix cluster deactivation documentation for the MXBean: Resolved