[jira] [Commented] (IGNITE-3020) .NET: Ensure that Windows service is stopped correctly in case of forceful node stop.

["Pavel Tupitsyn (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270422#comment-15270422 ] 

Pavel Tupitsyn commented on IGNITE-3020:
----------------------------------------

* TC is fine, both suites (classpath issue fixed).
* AfterNodeStop lifecycle event fixed so it works when node is stopped from Java
* Service install/uninstall logic changed from unmanaged calls to managed installer infrastructude, which is easier to work with



> .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
>              Labels: important
>             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)