[
https://issues.apache.org/jira/browse/IGNITE-15683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424730#comment-17424730
]
Valentin Kulichenko commented on IGNITE-15683:
----------------------------------------------
As a side, there is one more issue with this condition: it doesn't force the
tool to kill the external process (like we do in case of a timeout). As a
short-term solution, I think we can simply remove this condition - if something
goes wrong, the tool will just wait for the timeout and kill the process if
needed.
> CLI tool says 'Can't start the node' even though the node is successfully
> started
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-15683
> URL: https://issues.apache.org/jira/browse/IGNITE-15683
> Project: Ignite
> Issue Type: Bug
> Reporter: Valentin Kulichenko
> Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite node start}} command fails with the following message even though
> the node actually starts:
> {code}
> Starting a new Ignite node...
> Can't start the node. Read logs for details:
> /Users/vkulichenko/GridGain/ignite-3/target/apache-ignite-3.0.0-alpha3/ignite-log/node-1.log
> {code}
> Looks like this happens because there is the following line in the log:
> {noformat}
> Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger
> logInternalExceptional
> {noformat}
> The tool treats it as a failure because of this condition (see
> {{NodeManager}} class):
> {code}
> else if (content.contains("Exception"))
> throw new IgniteCLIException("Can't start the node. Read logs for
> details: " + file);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
