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

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.7
• Component/s: general
• Labels: StopCommand

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

• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: Glenn Wiebe
• Created: 15/Jan/19 15:55
• Updated: 02/Oct/19 15:46

Description

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.