Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Mon, 18 Apr 2016 08:11:25 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.12959571.1460967025000.252839.1460967085573@Atlassian.JIRA>
In-Reply-To: <JIRA.12959571.1460967025000@Atlassian.JIRA>
References: <JIRA.12959571.1460967025000@Atlassian.JIRA>
 <JIRA.12959571.1460967025029@arcas>
Subject: [jira] [Created] (IGNITE-3020) .NET: Ensure that Windows service is
 stopped correctly in case of forceful node stop.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Vladimir Ozerov created IGNITE-3020:
---------------------------------------

             Summary: .NET: Ensure that Windows service is stopped correctly in case of forceful node stop.
                 Key: IGNITE-3020
                 URL: https://issues.apache.org/jira/browse/IGNITE-3020
             Project: Ignite
          Issue Type: Task
          Components: platforms
    Affects Versions: 1.5.0.final
            Reporter: Vladimir Ozerov
            Assignee: Pavel Tupitsyn
             Fix For: 1.6


*Problem*
Node stop might be initiated from Java. E.g. from user job, or due to segmentation policy. We need to ensure that .NET service gets stopped as well in this case.

*Test case*
1) Start node A as Ignite service.
2) Start node B.
3) Send "node kill" task from B to A.
4) Wait for A to leave topology.
5) Ensure that ignite service is stopped.

Probably this could be implemented as automated unit test.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)