You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/03/12 08:52:00 UTC

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

    [ https://issues.apache.org/jira/browse/IGNITE-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790366#comment-16790366 ] 

Ignite TC Bot commented on IGNITE-8376:
---------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3288856&amp;buildTypeId=IgniteTests24Java8_RunAll]

> 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: 0.5h
>  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
(v7.6.3#76005)