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

Posted to issues@ignite.apache.org by "Vyacheslav Daradur (JIRA)" <ji...@apache.org> on 2018/07/31 15:45:00 UTC

[jira] [Assigned] (IGNITE-8365) Introduce service failure events

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

Vyacheslav Daradur reassigned IGNITE-8365:
------------------------------------------

    Assignee: Vyacheslav Daradur

> Introduce service failure events
> --------------------------------
>
>                 Key: IGNITE-8365
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8365
>             Project: Ignite
>          Issue Type: Improvement
>          Components: managed services
>            Reporter: Denis Mekhanikov
>            Assignee: Vyacheslav Daradur
>            Priority: Major
>              Labels: iep-17
>
> When a deployed service is propagated to a new node, and it fails to initialize, then a corresponding system event should be triggered in the cluster.
> This way a user will be able to handle situations, when services can't be deployed on joining nodes.
> Also, exceptions thrown from {{Service#execute}} method should trigger corresponding events.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)