Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Mon, 10 Jul 2017 07:26:00 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13081121.1497962462000.204897.1499671560203@Atlassian.JIRA>
In-Reply-To: <JIRA.13081121.1497962462000@Atlassian.JIRA>
References: <JIRA.13081121.1497962462000@Atlassian.JIRA> <JIRA.13081121.1497962462766@jira-lw-us.apache.org>
Subject: [jira] [Updated] (IGNITE-5560) A failed service must be redeployed
 when possible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Jul 2017 07:34:35 -0000


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

Vladimir Ozerov updated IGNITE-5560:
------------------------------------
    Fix Version/s:     (was: 2.1)
                   2.2

> 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
>             Fix For: 2.2
>
>
> 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
(v6.4.14#64029)