[
https://issues.apache.org/jira/browse/IGNITE-26718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-26718:
-----------------------------------------
Labels: ignite-3 (was: )
> Ignite 3: "cluster init" returns "Cluster was initialized successfully" while
> the cluster is still initializing
> ---------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-26718
> URL: https://issues.apache.org/jira/browse/IGNITE-26718
> Project: Ignite
> Issue Type: Bug
> Components: cli ai3
> Reporter: Ivan Artiukhov
> Priority: Major
> Labels: ignite-3
>
> Build under test: AI3 from {{main}} (rev.
> 0015ec4f1a1b066a12560a7739a296be94656f30)
> h1. Steps
> # Start a node using {{bin/ignite3db}}
> # Execute the following bash script to init the cluster via Ignite 3 CLI and
> to change the cluster configuration parameter:
> ##
> {noformat}
> set -x
> bin/ignite3 cluster init --url http://localhost:10300 --name=test_cluster
> bin/ignite3 cluster config update --url http://localhost:10300
> ignite.transaction.readWriteTimeoutMillis=240000
> bin/ignite3 cluster status --url http://localhost:10300
> bin/ignite3 cluster config update --url http://localhost:10300
> ignite.transaction.readWriteTimeoutMillis=240000{noformat}
> h1. Expected result
> # Both invocations of {{cluster config update}} changes the cluster parameter
> h1. Actual result
> # The first invocation of {{cluster config update}} fails with "Probably, you
> have not initialized the cluster":
> {noformat}
> Cluster was initialized successfully
> + bin/ignite3 cluster config update --url http://localhost:10300
> ignite.transaction.readWriteTimeoutMillis=240000
> Cannot update cluster config
> Probably, you have not initialized the cluster, try to run ignite cluster
> init command
> + bin/ignite3 cluster status --url http://localhost:10300
> [name: test_cluster, nodes: 1, status: active, cmgNodes: [defaultNode],
> msNodes: [defaultNode]]
> + bin/ignite3 cluster config update --url http://localhost:10300
> ignite.transaction.readWriteTimeoutMillis=240000
> Cluster configuration was updated successfully
> {noformat}
> So {{cluster init}} prints "Cluster was initialized successfully" and returns
> while the cluster is still being in the process of initialization. Such
> behaviour might be a huge UX issue for users which run Ignite 3 CLI commands
> from scripts.
> h1. Note
> Adding a pause between {{cluster init}} and {{cluster config update}} serves
> as a workaround for the issue:
> {noformat}
> + bin/ignite3 cluster init --url http://localhost:10300 --name=test_cluster
> Cluster was initialized successfully
> + sleep 1
> + bin/ignite3 cluster config update --url http://localhost:10300
> ignite.transaction.readWriteTimeoutMillis=240000
> Cluster configuration was updated successfully
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
