Valentin Kulichenko created IGNITE-13783:
--------------------------------------------

             Summary: Prevent starting nodes with the same consistent ID
                 Key: IGNITE-13783
                 URL: https://issues.apache.org/jira/browse/IGNITE-13783
             Project: Ignite
          Issue Type: Sub-task
            Reporter: Valentin Kulichenko


Currently, it is possible to start two or more nodes with the same consistent 
ID. Trying to stop using that ID succeeds for all the nodes, but an error 
appears in the output: {{Stop of node n1 was failed}}.

Here is the full output:
{noformat}
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node start 
n1
Started ignite node.
PID: 40644
Consistent Id: n1
Log file: /Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node start 
n1
Started ignite node.
PID: 40648
Consistent Id: n1
Log file: /Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node list
+-------+---------------+---------------------------------------------------------+
| PID   | Consistent Id | Log                                                   
  |
+-------+---------------+---------------------------------------------------------+
| 40644 | n1            | 
/Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log |
+-------+---------------+---------------------------------------------------------+
| 40648 | n1            | 
/Users/vkulichenko/GridGain/cli-demo/ignite-work/n1.log |
+-------+---------------+---------------------------------------------------------+
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node stop n1
Stop of node n1 was failed
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ ./ignite node list
No running nodes
Valentin-Kulichenko-MacBook-Pro-1772:cli-demo vkulichenko$ 
{noformat}

We should have a mechanism that prevents starting multiple nodes with the same 
ID.



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

Reply via email to