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] [Commented] (IGNITE-8376) Add cluster (de)activation events
Date Mon, 09 Jul 2018 02:41:00 GMT

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

kcheng.mvp commented on IGNITE-8376:

Thank you all very much for your comments. Right now I am working on it, once it's ready I
will raise PR.

> 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

View raw message