You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Glenn Wiebe (JIRA)" <ji...@apache.org> on 2019/01/15 15:56:00 UTC

[jira] [Created] (IGNITE-10948) Ignition.Stop() methods (named, all, etc.) fail to Stop cluster nodes

Glenn Wiebe created IGNITE-10948:
------------------------------------

             Summary: Ignition.Stop() methods (named, all, etc.) fail to Stop cluster nodes
                 Key: IGNITE-10948
                 URL: https://issues.apache.org/jira/browse/IGNITE-10948
             Project: Ignite
          Issue Type: Bug
          Components: general
    Affects Versions: 2.7
         Environment: [08:32:01] __________ ________________
[08:32:01] / _/ ___/ |/ / _/_ __/ __/
[08:32:01] _/ // (7 7 // / / / / _/
[08:32:01] /___/\___/_/|_/___/ /_/ /___/
[08:32:01]
[08:32:01] ver. 2.7.1#20181210-sha1:a39dbf0f
[08:32:01] 2018 Copyright(C) Apache Software Foundation
[08:32:01]
[08:32:01] Ignite documentation: http://ignite.apache.org
[08:32:01]
[08:32:01] Quiet mode.
[08:32:01] ^-- Logging to file 'C:\apps\gridgain-ultimate-8.7.1\work\log\ignite-55082e2d.0.log'
[08:32:01] ^-- Logging by 'JavaLogger [quiet=true, config=null]'
[08:32:01] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or "-v" to ignite.\{sh|bat}
[08:32:01]
[08:32:01] OS: Windows 10 10.0 amd64
[08:32:01] VM information: Java(TM) SE Runtime Environment 1.8.0_162-b12 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.162-b12
            Reporter: Glenn Wiebe
             Fix For: 3.0, 2.8


The Ignition singleton stop() or stopAll() methods do not respond by stopping any or all of the cluster nodes.

Unlike the ignite.cluster().stop() methods, the Ignition.stop() methods ignore the requested stop command, simply returning the following warning: "(wrn) Ignoring stopping Ignite instance that was already stopped or never started: MyServerName"

This fails whether the cluster was active() = true or false.

This fails whether the command was issued from a Server or Client node.

Maybe this method should be deprecated, but currently documented method does not work.

 



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