[
https://issues.apache.org/jira/browse/IGNITE-20777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor updated IGNITE-20777:
--------------------------
Description:
*Steps to reproduce:*
# Start cluster with 2 nodes.
# Init cluster
*Expected result:*
Cluster started
*Actual result:*
Error in log and cluster shutting down.
[^ignite3db-0.log.txt] [^stderr.log.txt]
*Workaround:*
If the option *--add-opens=java.base/sun.nio.ch=ALL-UNNAMED* is added to
startup script, cluster works fine.
was:
*Steps to reproduce:*
# Start cluster with 2 nodes.
# Init cluster
*Expected result:*
Cluster started
{*}Actual result:{*}{*}{*}
Error in log and cluster shutting down.
[^ignite3db-0.log.txt] [^stderr.log.txt]
*Workaround:*
If the option *--add-opens=java.base/sun.nio.ch=ALL-UNNAMED* added to startup
script, cluster works fine.
> Exception while init cluster due to missed `add-opens` argument
> ---------------------------------------------------------------
>
> Key: IGNITE-20777
> URL: https://issues.apache.org/jira/browse/IGNITE-20777
> Project: Ignite
> Issue Type: Bug
> Components: cli, general
> Affects Versions: 3.0.0-beta2
> Reporter: Igor
> Priority: Major
> Labels: ignite-3
> Attachments: ignite3db-0.log.txt, stderr.log.txt
>
>
> *Steps to reproduce:*
> # Start cluster with 2 nodes.
> # Init cluster
> *Expected result:*
> Cluster started
> *Actual result:*
> Error in log and cluster shutting down.
> [^ignite3db-0.log.txt] [^stderr.log.txt]
> *Workaround:*
> If the option *--add-opens=java.base/sun.nio.ch=ALL-UNNAMED* is added to
> startup script, cluster works fine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)