[IGNITE-8376] Add cluster (de)activation events

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Labels: newbie
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Igor Belyakov
• Reporter: Alexey Goncharuk
• Created: 24/Apr/18 11:46
• Updated: 21/Oct/19 13:17
• Resolved: 28/Mar/19 16:30

Description

Currently, we do not have any way to detect that a cluster got activated, which results in busy-loops polling cluster().active().

I suggest to add new events, EVT_CLUSTER_ACTIVATED, EVT_CLUSTER_DEACTIVATED, EVT_CLUSTER_ACTIVATION_FAILED which will be fired when corresponding steps are completed. The event should contain, if possible, information about the activation source (public API or auto-activation), topology version on which activation was performed. The fail event should contain information about the cause of the failure. If needed, a new class for this event should be introduced.

Issue Links

• Blocked: IGNITE-5427 Add cluster activation/deactivation lifecycle events
• is related to: IGNITE-11492 Add cluster activation to FailureHandler
• relates to: IGNITE-11651 Add cluster (de)activation events documentation
• links to: GitHub Pull Request #6235