You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Belyakov (JIRA)" <ji...@apache.org> on 2019/03/21 08:51:00 UTC
[jira] [Comment Edited] (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=16796918#comment-16796918 ]
Igor Belyakov edited comment on IGNITE-8376 at 3/21/19 8:50 AM:
----------------------------------------------------------------
[~ilyak] [~agoncharuk]
Recording cluster activation event moved to ExchangeFuture listener. Tests implemented.
was (Author: ibelyakov):
[~ilyak] Recording cluster activation event moved to ExchangeFuture listener. Tests implemented.
> 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
> 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)