[
https://issues.apache.org/jira/browse/IGNITE-13782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-13782:
-----------------------------------------
Description:
# Run {{ignite init}}
# Delete {{ignite-bin}} and {{ignite-work}} folders
# Run {{ignite node start n1}}
Steps result in the following exception:
{noformat}
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
{noformat}
{{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.
was:
# 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.
> Support re-initialization in case of manual folder removal
> ----------------------------------------------------------
>
> Key: IGNITE-13782
> URL: https://issues.apache.org/jira/browse/IGNITE-13782
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Valentin Kulichenko
> Priority: Major
> Labels: ignite-3
>
> # Run {{ignite init}}
> # Delete {{ignite-bin}} and {{ignite-work}} folders
> # Run {{ignite node start n1}}
> Steps result in the following exception:
> {noformat}
> 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
> {noformat}
> {{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)
