ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kcheng.mvp (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-8376) Add cluster (de)activation events
Date Tue, 10 Jul 2018 05:08:00 GMT

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

kcheng.mvp reassigned IGNITE-8376:
----------------------------------

    Assignee:     (was: kcheng.mvp)

> 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
>            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)

Mime
View raw message