[
https://issues.apache.org/jira/browse/IGNITE-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534741#comment-16534741
]
Alexey Kuznetsov commented on IGNITE-8376:
------------------------------------------
[~agoncharuk] and [~DmitriyGovorukhin] Could we have not only events, but also
a kind of enum property that works the same as boolean property
cluster.active() ?
This could be smth. like (pseudo code):
{code}
ClusterStateEnum {ACTIVE, INACTIVE, ACTIVATING, DEACTIVATING};
ClusterStateEnum cluster.activeState();
{code}
One more idea - report of current progress of activation/deactivation:
{code}
/** return number of already activated/deactivated nodes */
int cluster.activeStateProgress();
{code}
What do you think?
> Add cluster (de)activation events
> ---------------------------------
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Assignee: kcheng.mvp
> Priority: Major
> Labels: newbie
> Fix For: 2.7
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
