You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/21 13:18:00 UTC

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

     [ https://issues.apache.org/jira/browse/IGNITE-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Muzafarov updated IGNITE-8376:
------------------------------------
    Ignite Flags: Docs Required,Release Notes Required

> 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: Igor Belyakov
>            Priority: Major
>              Labels: newbie
>             Fix For: 2.8
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)