ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5560) A failed service must be redeployed when possible
Date Tue, 28 Aug 2018 07:46:00 GMT

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

Alexey Goncharuk updated IGNITE-5560:
-------------------------------------
    Fix Version/s:     (was: 2.7)
                   2.8

> A failed service must be redeployed when possible
> -------------------------------------------------
>
>                 Key: IGNITE-5560
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5560
>             Project: Ignite
>          Issue Type: Improvement
>          Components: managed services
>    Affects Versions: 1.7
>            Reporter: Alexey Goncharuk
>            Priority: Major
>             Fix For: 2.8
>
>
> I observed the following behavior: when a service deployment (or run) fails with an unexpected
exception, Ignite just outputs a warning to the console and does not attempt anything to recover.

> In our deployment, we rely on a cluster singleton to be always present in a cluster.

> If a service fails, Ignite should attempt to failover this service to some other node,
if possible



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

Mime
View raw message