[jira] [Assigned] (IGNITE-21484) Possible race in JobExecution.changePriority method
[ https://issues.apache.org/jira/browse/IGNITE-21484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov reassigned IGNITE-21484: --- Assignee: Dmitry Baranov > Possible race in JobExecution.changePriority method > --- > > Key: IGNITE-21484 > URL: https://issues.apache.org/jira/browse/IGNITE-21484 > Project: Ignite > Issue Type: Bug > Components: compute >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Dmitry Baranov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In > [https://github.com/apache/ignite-3/blob/6729811f99ad18b1490f9b7516a2af84a898e7af/modules/compute/src/main/java/org/apache/ignite/internal/compute/queue/QueueExecutionImpl.java#L115] > race is possible. > thread 1: remove task from the queue > thread 2: haven't found the same task in the queue because it is not added > yet by thread 1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21484) Possible race in JobExecution.changePriority method
Dmitry Baranov created IGNITE-21484: --- Summary: Possible race in JobExecution.changePriority method Key: IGNITE-21484 URL: https://issues.apache.org/jira/browse/IGNITE-21484 Project: Ignite Issue Type: Bug Components: compute Affects Versions: 3.0.0-beta1 Reporter: Dmitry Baranov In [https://github.com/apache/ignite-3/blob/6729811f99ad18b1490f9b7516a2af84a898e7af/modules/compute/src/main/java/org/apache/ignite/internal/compute/queue/QueueExecutionImpl.java#L115] race is possible. thread 1: remove task from the queue thread 2: haven't found the same task in the queue because it is not added yet by thread 1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21219) Write memory leak tests
[ https://issues.apache.org/jira/browse/IGNITE-21219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov reassigned IGNITE-21219: --- Assignee: Dmitry Baranov > Write memory leak tests > --- > > Key: IGNITE-21219 > URL: https://issues.apache.org/jira/browse/IGNITE-21219 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Aleksandr >Assignee: Dmitry Baranov >Priority: Major > Labels: ignite-3 > > Compute jobs handling logic is getting harder to track every reference we > have. It seems like we can easily introduce a memory leak. I wonder if we > have some microbenchmarks that prove the absence of memory leak in the > compute component. > Important note: the simulation of leaving and joining the cluster of several > nodes (candidates, workers) should be done as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21220) Worker node recovery
[ https://issues.apache.org/jira/browse/IGNITE-21220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov reassigned IGNITE-21220: --- Assignee: Dmitry Baranov > Worker node recovery > > > Key: IGNITE-21220 > URL: https://issues.apache.org/jira/browse/IGNITE-21220 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Dmitry Baranov >Priority: Major > Labels: ignite-3 > > There is a case when the worker node executing some job has left the logical > topology. This node has to identify this situation and stop all running jobs. > We must not have the situation when the worker left the topology, the > coordinator restarted the job on another node, then the first worker joined > the topology and two instances of the job are running on the cluster. > Maybe we do not allow this but we have a lack of tests here. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21220) Worker node recovery
[ https://issues.apache.org/jira/browse/IGNITE-21220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov resolved IGNITE-21220. - Resolution: Won't Fix > Worker node recovery > > > Key: IGNITE-21220 > URL: https://issues.apache.org/jira/browse/IGNITE-21220 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Dmitry Baranov >Priority: Major > Labels: ignite-3 > > There is a case when the worker node executing some job has left the logical > topology. This node has to identify this situation and stop all running jobs. > We must not have the situation when the worker left the topology, the > coordinator restarted the job on another node, then the first worker joined > the topology and two instances of the job are running on the cluster. > Maybe we do not allow this but we have a lack of tests here. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21220) Worker node recovery
[ https://issues.apache.org/jira/browse/IGNITE-21220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814163#comment-17814163 ] Dmitry Baranov commented on IGNITE-21220: - In case of network partitioning node will be removed from logical topology, to join topology again node need to be restarted, thus jobs will be canceled during restart. There is no need to process jobs on initial worker node in case of onNodeLeft event > Worker node recovery > > > Key: IGNITE-21220 > URL: https://issues.apache.org/jira/browse/IGNITE-21220 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Priority: Major > Labels: ignite-3 > > There is a case when the worker node executing some job has left the logical > topology. This node has to identify this situation and stop all running jobs. > We must not have the situation when the worker left the topology, the > coordinator restarted the job on another node, then the first worker joined > the topology and two instances of the job are running on the cluster. > Maybe we do not allow this but we have a lack of tests here. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21335) Implement JobExecutionOptions in C++ client
Dmitry Baranov created IGNITE-21335: --- Summary: Implement JobExecutionOptions in C++ client Key: IGNITE-21335 URL: https://issues.apache.org/jira/browse/IGNITE-21335 Project: Ignite Issue Type: Task Components: thin client Affects Versions: 3.0.0-beta1 Reporter: Dmitry Baranov Fix For: 3.0.0-beta2 Java part of this changes https://github.com/apache/ignite-3/pull/3050 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21334) Implement JobExecutionOptions in C# client
Dmitry Baranov created IGNITE-21334: --- Summary: Implement JobExecutionOptions in C# client Key: IGNITE-21334 URL: https://issues.apache.org/jira/browse/IGNITE-21334 Project: Ignite Issue Type: Task Components: thin client Affects Versions: 3.0.0-beta1 Reporter: Dmitry Baranov Fix For: 3.0.0-beta2 Java part of this changes https://github.com/apache/ignite-3/pull/3050 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20840) Introduce Job execution options
[
https://issues.apache.org/jira/browse/IGNITE-20840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Baranov reassigned IGNITE-20840:
---
Assignee: Dmitry Baranov
> Introduce Job execution options
> ---
>
> Key: IGNITE-20840
> URL: https://issues.apache.org/jira/browse/IGNITE-20840
> Project: Ignite
> Issue Type: Improvement
> Components: compute
>Reporter: Mikhail Pochatkin
>Assignee: Dmitry Baranov
>Priority: Major
> Labels: ignite-3
>
> Each execute method in *org.apache.ignite.compute.IgniteCompute* should have
> JobExecutionOptions argument. The structure of options class should be follow
> {code:java}
> public interface JobExecutionOptions {
> long priority();
> short maxRetries();
> }{code}
> Priority is Queue priority (default value 0). Max retries is failure retry
> counter (default is 0).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21066) Create job priority change API
[ https://issues.apache.org/jira/browse/IGNITE-21066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov reassigned IGNITE-21066: --- Assignee: Dmitry Baranov > Create job priority change API > -- > > Key: IGNITE-21066 > URL: https://issues.apache.org/jira/browse/IGNITE-21066 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Assignee: Dmitry Baranov >Priority: Major > Labels: ignite-3 > > Once a job has been accepted for execution and is in the queue, we should be > able to dynamically change its priority in order to move it up or down in the > execution queue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20516) Remove openapi.yaml spec from git repository
[ https://issues.apache.org/jira/browse/IGNITE-20516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov updated IGNITE-20516: Labels: ignite-3 (was: ) > Remove openapi.yaml spec from git repository > > > Key: IGNITE-20516 > URL: https://issues.apache.org/jira/browse/IGNITE-20516 > Project: Ignite > Issue Type: Task > Components: rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Priority: Major > Labels: ignite-3 > > Source of truth for rest api should be java code. So, generated openapi spec > should not be saved in repo (modules/rest-api/openapi/openapi.yaml) > spec should be provided as artifact in TC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20516) Remove openapi.yaml spec from git repository
[ https://issues.apache.org/jira/browse/IGNITE-20516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov updated IGNITE-20516: Description: Source of truth for rest api should be java code. So, generated openapi spec should not be saved in repo (modules/rest-api/openapi/openapi.yaml) spec should be provided as artifact in TC was: Source of truth for rest api should be java code. So, generated openapi spec should not be saved in repo spec should be provided as artifact in TC > Remove openapi.yaml spec from git repository > > > Key: IGNITE-20516 > URL: https://issues.apache.org/jira/browse/IGNITE-20516 > Project: Ignite > Issue Type: Task > Components: rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Priority: Major > > Source of truth for rest api should be java code. So, generated openapi spec > should not be saved in repo (modules/rest-api/openapi/openapi.yaml) > spec should be provided as artifact in TC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20516) Remove openapi.yaml spec from git repository
Dmitry Baranov created IGNITE-20516: --- Summary: Remove openapi.yaml spec from git repository Key: IGNITE-20516 URL: https://issues.apache.org/jira/browse/IGNITE-20516 Project: Ignite Issue Type: Task Components: rest Affects Versions: 3.0.0-beta1 Reporter: Dmitry Baranov Source of truth for rest api should be java code. So, generated openapi spec should not be saved in repo spec should be provided as artifact in TC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-20434) Provide jdbc port in NodeState REST API
[ https://issues.apache.org/jira/browse/IGNITE-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768566#comment-17768566 ] Dmitry Baranov edited comment on IGNITE-20434 at 9/25/23 7:47 AM: -- github PR link [https://github.com/apache/ignite-3/pull/2607] was (Author: JIRAUSER299704): github https://github.com/apache/ignite-3/pull/2607 > Provide jdbc port in NodeState REST API > --- > > Key: IGNITE-20434 > URL: https://issues.apache.org/jira/browse/IGNITE-20434 > Project: Ignite > Issue Type: Task > Components: cli, rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Dmitry Baranov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > To avoid extra rest call on cli connect command it is better to provide jdbc > port in node state rest call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20434) Provide jdbc port in NodeState REST API
[ https://issues.apache.org/jira/browse/IGNITE-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov updated IGNITE-20434: github https://github.com/apache/ignite-3/pull/2607 > Provide jdbc port in NodeState REST API > --- > > Key: IGNITE-20434 > URL: https://issues.apache.org/jira/browse/IGNITE-20434 > Project: Ignite > Issue Type: Task > Components: cli, rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Dmitry Baranov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > To avoid extra rest call on cli connect command it is better to provide jdbc > port in node state rest call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20434) Provide jdbc port in NodeState REST API
[ https://issues.apache.org/jira/browse/IGNITE-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov updated IGNITE-20434: Labels: ignite-3 ignite-3-cli-tool (was: ) > Provide jdbc port in NodeState REST API > --- > > Key: IGNITE-20434 > URL: https://issues.apache.org/jira/browse/IGNITE-20434 > Project: Ignite > Issue Type: Task > Components: cli, rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Dmitry Baranov >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > To avoid extra rest call on cli connect command it is better to provide jdbc > port in node state rest call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20434) Provide jdbc port in NodeState REST API
[ https://issues.apache.org/jira/browse/IGNITE-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov reassigned IGNITE-20434: --- Assignee: Dmitry Baranov > Provide jdbc port in NodeState REST API > --- > > Key: IGNITE-20434 > URL: https://issues.apache.org/jira/browse/IGNITE-20434 > Project: Ignite > Issue Type: Task > Components: cli, rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Dmitry Baranov >Priority: Major > > To avoid extra rest call on cli connect command it is better to provide jdbc > port in node state rest call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20434) Provide jdbc port in NodeState REST API
Dmitry Baranov created IGNITE-20434: --- Summary: Provide jdbc port in NodeState REST API Key: IGNITE-20434 URL: https://issues.apache.org/jira/browse/IGNITE-20434 Project: Ignite Issue Type: Task Components: cli, rest Affects Versions: 3.0.0-beta1 Reporter: Dmitry Baranov To avoid extra rest call on cli connect command it is better to provide jdbc port in node state rest call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20343) Flaky ItIgnitePicocliCommandsTest
Dmitry Baranov created IGNITE-20343:
---
Summary: Flaky ItIgnitePicocliCommandsTest
Key: IGNITE-20343
URL: https://issues.apache.org/jira/browse/IGNITE-20343
Project: Ignite
Issue Type: Bug
Components: cli
Affects Versions: 3.0.0-beta1
Reporter: Dmitry Baranov
Failure example
[test
result|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_IntegrationTests_ModuleCli/7475403?hideProblemsFromDependencies=false=false=true=true=true]
{code:java}
org.awaitility.core.ConditionTimeoutException: Lambda expression in
org.apache.ignite.internal.cli.core.repl.executor.ItIgnitePicocliCommandsTest:
expected not an empty collection but was <[]> within 10 seconds. at
app//org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
at
app//org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
at
app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
at app//org.awaitility.core.ConditionFactory.until(ConditionFactory.java:691)
at
app//org.apache.ignite.internal.cli.core.repl.executor.ItIgnitePicocliCommandsTest.nodeNameSuggested(ItIgnitePicocliCommandsTest.java:350)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20324) Implement integration tests to cover questions in CLI
Dmitry Baranov created IGNITE-20324: --- Summary: Implement integration tests to cover questions in CLI Key: IGNITE-20324 URL: https://issues.apache.org/jira/browse/IGNITE-20324 Project: Ignite Issue Type: Improvement Components: cli Affects Versions: 3.0.0-beta1 Reporter: Dmitry Baranov Currently all CLI integration tests uses bindAnswer() method to prepare answers but there are no tests to validate questions. It may hide some issues. Need to update cli test framework to check questions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20271) Error in CLI on SQL repl command
[
https://issues.apache.org/jira/browse/IGNITE-20271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Baranov reassigned IGNITE-20271:
---
Assignee: Dmitry Baranov
> Error in CLI on SQL repl command
>
>
> Key: IGNITE-20271
> URL: https://issues.apache.org/jira/browse/IGNITE-20271
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Affects Versions: 3.0.0-beta1
>Reporter: Dmitry Baranov
>Assignee: Dmitry Baranov
>Priority: Major
>
> Init ignite 3 cluster, than
> _[defaultNode]> sql_
> *Unknown error*
> {*}Expected{*}:
> enter in sql repl mode
> {*}Actual{*}:
> Cannot invoke
> "org.apache.ignite.internal.cli.core.repl.EventListeningActivationPoint.subscribe()"
> because the return value of
> "org.apache.ignite.internal.cli.core.repl.Repl.getEventListeningActivationPoint()"
> is null
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20271) Error in CLI on SQL repl command
Dmitry Baranov created IGNITE-20271:
---
Summary: Error in CLI on SQL repl command
Key: IGNITE-20271
URL: https://issues.apache.org/jira/browse/IGNITE-20271
Project: Ignite
Issue Type: Bug
Components: cli
Affects Versions: 3.0.0-beta1
Reporter: Dmitry Baranov
Init ignite 3 cluster, than
_[defaultNode]> sql_
*Unknown error*
{*}Expected{*}:
enter in sql repl mode
{*}Actual{*}:
Cannot invoke
"org.apache.ignite.internal.cli.core.repl.EventListeningActivationPoint.subscribe()"
because the return value of
"org.apache.ignite.internal.cli.core.repl.Repl.getEventListeningActivationPoint()"
is null
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19246) CLI should ask for auth settings
[ https://issues.apache.org/jira/browse/IGNITE-19246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Baranov reassigned IGNITE-19246: --- Assignee: Dmitry Baranov (was: Vadim Pakhnushev) > CLI should ask for auth settings > > > Key: IGNITE-19246 > URL: https://issues.apache.org/jira/browse/IGNITE-19246 > Project: Ignite > Issue Type: Improvement > Components: cli >Reporter: Vadim Pakhnushev >Assignee: Dmitry Baranov >Priority: Major > Labels: iep-106, ignite-3 > > Currently, a user just gets an error, if tries to connect to a node which has > authentication configured. > The CLI should ask a user to set auth settings if gets an error on a call, > save provided values to the config and repeat the call. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20171) 'Unknown error' in case of empty Problem JSON in error rest response
[
https://issues.apache.org/jira/browse/IGNITE-20171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Baranov updated IGNITE-20171:
Description:
If there is no Problem json in rest respone on some error, CLI interface shows
message like
{{Unknown error}}
{{argument "content" is null}}
The root cause of the issue it cli rest client. Rest client generated required
param validation like
// verify the required parameter 'roleName' is set
if (roleName == null) {
throw new ApiException("Missing the required parameter 'roleName' when calling
getPrivileges(Async)");
}
in this case client send 500 error without any content (by spec Problem content
should be)
it cause {{Unknown error }}in CLI console
was:
If there is no Problem json in rest respone on some error, CLI interface shows
message like
{{Unknown error}}
{{argument "content" is null}}
> 'Unknown error' in case of empty Problem JSON in error rest response
>
>
> Key: IGNITE-20171
> URL: https://issues.apache.org/jira/browse/IGNITE-20171
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Affects Versions: 3.0.0-beta1
>Reporter: Dmitry Baranov
>Assignee: Dmitry Baranov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If there is no Problem json in rest respone on some error, CLI interface
> shows message like
> {{Unknown error}}
> {{argument "content" is null}}
>
> The root cause of the issue it cli rest client. Rest client generated
> required param validation like
>
> // verify the required parameter 'roleName' is set
> if (roleName == null) {
> throw new ApiException("Missing the required parameter 'roleName' when
> calling getPrivileges(Async)");
> }
>
> in this case client send 500 error without any content (by spec Problem
> content should be)
> it cause {{Unknown error }}in CLI console
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20171) 'Unknown error' in case of empty Problem JSON in error rest response
Dmitry Baranov created IGNITE-20171:
---
Summary: 'Unknown error' in case of empty Problem JSON in error
rest response
Key: IGNITE-20171
URL: https://issues.apache.org/jira/browse/IGNITE-20171
Project: Ignite
Issue Type: Bug
Components: cli
Affects Versions: 3.0.0-beta1
Reporter: Dmitry Baranov
If there is no Problem json in rest respone on some error, CLI interface shows
message like
{{Unknown error}}
{{argument "content" is null}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-20171) 'Unknown error' in case of empty Problem JSON in error rest response
[
https://issues.apache.org/jira/browse/IGNITE-20171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Baranov reassigned IGNITE-20171:
---
Assignee: Dmitry Baranov
> 'Unknown error' in case of empty Problem JSON in error rest response
>
>
> Key: IGNITE-20171
> URL: https://issues.apache.org/jira/browse/IGNITE-20171
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Affects Versions: 3.0.0-beta1
>Reporter: Dmitry Baranov
>Assignee: Dmitry Baranov
>Priority: Major
>
> If there is no Problem json in rest respone on some error, CLI interface
> shows message like
> {{Unknown error}}
> {{argument "content" is null}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20099) IOException in CLI on node shutdown
Dmitry Baranov created IGNITE-20099:
---
Summary: IOException in CLI on node shutdown
Key: IGNITE-20099
URL: https://issues.apache.org/jira/browse/IGNITE-20099
Project: Ignite
Issue Type: Bug
Components: cli
Affects Versions: 3.0.0-beta1
Reporter: Dmitry Baranov
Attachments: 2023-07-31_08-46-39.png
On node shutdown IOException printed in CLI
Steps to reproduce:
1. Start ignite3 ./{_}bin/ignite3db start{_}
2. start CLI and invoke _connect_ command
3. shutdown ignite ./{_}bin/ignite3db stop{_}
Expected: user readable error message about connection lost
Actual:
[defaultNode]> [java.io.IOException: unexpected end of stream on
http://localhost:10300/..., java.net.SocketException: Connection reset,
java.net.SocketException: Connection reset, java.net.SocketException:
Connection reset, java.net.SocketException: Connection reset,
java.net.ConnectException: Failed to connect to localhost/127.0.0.1:10300]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20025) Command 'connect defaultNode' throws error
Dmitry Baranov created IGNITE-20025:
---
Summary: Command 'connect defaultNode' throws error
Key: IGNITE-20025
URL: https://issues.apache.org/jira/browse/IGNITE-20025
Project: Ignite
Issue Type: Bug
Components: cli
Affects Versions: 3.0.0-beta1
Reporter: Dmitry Baranov
Attachments: image-2023-07-23-16-57-58-225.png
Steps to reproduce the issue
1. from disconnected state execute
{code:java}
connect{code}
Connected to http://localhost:10300
2.
{code:java}
disconnect{code}
Disconnected from http://localhost:10300
3.
{code:java}
connect http://localhost:10300{code}
Connected to http://localhost:10300
4. [admin:defaultNode]>
{code:java}
disconnect{code}
Disconnected from http://localhost:10300
5. [disconnected]>
{code:java}
connect defaultNode{code}
*Actual:*
Invalid value for positional parameter at index 0 (): Node
defaultNode not found. Provide valid name or use URL
Usage: connect [-hv]
Connects to Ignite 3 node
URL or name of an Ignite node
-h, --help Show help for the specified command
-v, --verbose Show additional information: logs, REST calls
{*}Expected{*}:
Successful connection to the defaultNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19936) Add username and password parameters to the connect command
[
https://issues.apache.org/jira/browse/IGNITE-19936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Baranov reassigned IGNITE-19936:
---
Assignee: Dmitry Baranov
> Add username and password parameters to the connect command
> ---
>
> Key: IGNITE-19936
> URL: https://issues.apache.org/jira/browse/IGNITE-19936
> Project: Ignite
> Issue Type: Improvement
> Components: cli
>Reporter: Vadim Pakhnushev
>Assignee: Dmitry Baranov
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Connect command should have {{--username --password}} parameters which will
> override values stored in the config file.
> In the REPL mode after successful connection CLI should ask the user whether
> these values should be stored in the config file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
