You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2021/04/16 14:14:00 UTC

[jira] [Created] (IGNITE-14576) Ignite command-line tool cannot stop already running ignite instance

Vyacheslav Koptilin created IGNITE-14576:
--------------------------------------------

             Summary: Ignite command-line tool cannot stop already running ignite instance
                 Key: IGNITE-14576
                 URL: https://issues.apache.org/jira/browse/IGNITE-14576
             Project: Ignite
          Issue Type: Bug
         Environment: 

            Reporter: Vyacheslav Koptilin


Ignite command-line tool cannot stop already running ignite instance.

Steps to reproduce:
1. start Ignite node 
{code:bash}
PS C:\projects\ignite-3\modules\cli\target> ./ignite node start consistent-id=xxxx
Starting a new Ignite node...

Node is successfully started. To stop, type ignite node stop consistent-id=xxxx

+---------------+---------------------------------------------------------------------------+
| Consistent ID | consistent-id=xxxx                                                        |
+---------------+---------------------------------------------------------------------------+
| PID           | 17476                                                                     |
+---------------+---------------------------------------------------------------------------+
| Log File      | C:\projects\ignite-3\modules\cli\target\ignite-log\consistent-id=xxxx.log |
+---------------+---------------------------------------------------------------------------+
{code}

2. make sure that Ignite node has been started

{code:bash}
PS C:\projects\ignite-3\modules\cli\target> ./ignite node list
Currently, there are 1 locally running nodes.

+--------------------+-------+---------------------------------------------------------------------------+
| Consistent ID      | PID   | Log File                                                                  |
+--------------------+-------+---------------------------------------------------------------------------+
| consistent-id=xxxx | 17476 | C:\projects\ignite-3\modules\cli\target\ignite-log\consistent-id=xxxx.log |
+--------------------+-------+---------------------------------------------------------------------------+
{code}

3 try to stop the node

{code:bash}
PS C:\projects\ignite-3\modules\cli\target> ./ignite node stop consistent-ids=xxxx
Can't find node with consistent id consistent-ids=xxxx
{code}

The root cause is obvious. The tool tries to find {{consistentId*s*=xxxx_...pid}} file instead of {{consistent-id=xxxx_...pid}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)