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 2020/12/01 00:19:00 UTC
[jira] [Created] (IGNITE-13782) [CLI Tool] Manual folder removal
causes exceptions
Valentin Kulichenko created IGNITE-13782:
--------------------------------------------
Summary: [CLI Tool] Manual folder removal causes exceptions
Key: IGNITE-13782
URL: https://issues.apache.org/jira/browse/IGNITE-13782
Project: Ignite
Issue Type: Bug
Reporter: Valentin Kulichenko
# Run {{ignite init}}
# Delete {{ignite-bin}} and {{ignite-work}} folders
# Run {{ignite node start n1}}
Steps result in the following exception:
{nofomat}
Exception in thread "main" java.lang.RuntimeException: java.nio.file.NoSuchFileException: /Users/vkulichenko/GridGain/cli-demo/ignite-bin/2.9.0/cli
at org.apache.ignite.internal.v2.builtins.SystemPathResolver.list(SystemPathResolver.java:39)
at org.apache.ignite.internal.v2.spec.IgniteCliSpec.loadSubcommands(IgniteCliSpec.java:81)
at org.apache.ignite.internal.v2.spec.IgniteCliSpec.lambda$main$0(IgniteCliSpec.java:64)
at java.base/java.util.Optional.ifPresent(Optional.java:176)
at org.apache.ignite.internal.v2.spec.IgniteCliSpec.main(IgniteCliSpec.java:64)
Caused by: java.nio.file.NoSuchFileException: /Users/vkulichenko/GridGain/cli-demo/ignite-bin/2.9.0/cli
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
at java.base/sun.nio.fs.UnixFileSystemProvider.newDirectoryStream(UnixFileSystemProvider.java:412)
at java.base/java.nio.file.Files.newDirectoryStream(Files.java:476)
at java.base/java.nio.file.Files.list(Files.java:3765)
at org.apache.ignite.internal.v2.builtins.SystemPathResolver.list(SystemPathResolver.java:28)
... 4 more
{nofomat}
{{ignite init}} fails with the same exception as well, so the only way to fix this is to manually delete the {{.ignitecfg}} file, which the user is not aware of.
We should have the support for re-initialization, and suggest to do that in case the described scenario occures.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)