You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (Jira)" <ji...@apache.org> on 2021/07/23 18:30:00 UTC
[jira] [Created] (IGNITE-15190) Ignite 3 CLI: if a node start takes
longer than the timeout, it does not appear in the list
Valentin Kulichenko created IGNITE-15190:
--------------------------------------------
Summary: Ignite 3 CLI: if a node start takes longer than the timeout, it does not appear in the list
Key: IGNITE-15190
URL: https://issues.apache.org/jira/browse/IGNITE-15190
Project: Ignite
Issue Type: Bug
Affects Versions: 3.0.0-alpha2
Reporter: Valentin Kulichenko
The {{node start}} command has a timeout, after which it treats the startup process as failed, and exits, without including the node in the list shown by the {{node list}} command.
It is possible that the node actually manages to start after the timeout, in which case the CLI tool and the user are not aware of the running node.
We need to revisit the node management approach in the CLI, so that we can avoid issues like this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)