[
https://issues.apache.org/jira/browse/IGNITE-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinskiy updated IGNITE-13321:
--------------------------------------
Description:
After merging [IGNITE-13123|https://issues.apache.org/jira/browse/IGNITE-13123]
{{control.sh}} doesn't work properly either in dev mode, or in release mode.
Specifically,
no output printed in stdout. However,
For example, incorrect output for {{control.sh --activate}} after commit s:
{code:sh}
Control utility [ver. 2.10.0-SNAPSHOT#20200803-sha1:DEV],
2020 Copyright(C) Apache Software Foundation,
User: ducker,
Time: 2020-08-03T14:24:33.193,
Command [BASELINE] started,
Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
--------------------------------------------------------------------------------
{code}
Correct output for {{control.sh --activate}} before commit is:
{code}
Control utility [ver. 2.8.1#20200521-sha1:86422096],
2020 Copyright(C) Apache Software Foundation,
User: ducker,
Time: 2020-08-03T14:23:55.793,
Command [BASELINE] started,
Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
--------------------------------------------------------------------------------,
Cluster state: active,
Current topology version: 3,
Baseline auto adjustment disabled: softTimeout=300000
Current topology version: 3 (Coordinator: ConsistentId=ducker02, Order=1)
Baseline nodes:
ConsistentId=ducker02, State=ONLINE, Order=1,
ConsistentId=ducker03, State=ONLINE, Order=2,
ConsistentId=ducker04, State=ONLINE, Order=3,
--------------------------------------------------------------------------------,
Number of baseline nodes: 3,
Other nodes not found.,
Command [BASELINE] finished with code: 0,
Control utility has completed execution at: 2020-08-03T14:23:57.351,
Execution time: 1558 ms
{code}
was:
After merging [IGNITE-13123|https://issues.apache.org/jira/browse/IGNITE-13123]
{{control.sh}} doesn't work properly either in dev mode, or in release mode.
Specifically,
no output printed in stdout. However,
For example, incorrect output for {{control.sh --activate}} after commit s:
{code:sh}
Control utility [ver. 2.9.0-SNAPSHOT#20200803-sha1:DEV]
2020 Copyright(C) Apache Software Foundation
User: ivandasch
Time: 2020-08-03T17:21:06.246
Command [BASELINE] started
Arguments: --baseline
--------------------------------------------------------------------------------
Failed to execute baseline command='collect'
Latest topology update failed.
Connection to cluster failed. Latest topology update failed.
Command [BASELINE] finished with code: 2
Control utility has completed execution at: 2020-08-03T17:21:09.613
Execution time: 3367 ms
{code}
Correct output for {{control.sh --activate}} before commit is:
{code}
Control utility [ver. 2.8.1#20200521-sha1:86422096],
2020 Copyright(C) Apache Software Foundation,
User: ducker,
Time: 2020-08-03T14:23:55.793,
Command [BASELINE] started,
Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
--------------------------------------------------------------------------------,
Cluster state: active,
Current topology version: 3,
Baseline auto adjustment disabled: softTimeout=300000
Current topology version: 3 (Coordinator: ConsistentId=ducker02, Order=1)
Baseline nodes:
ConsistentId=ducker02, State=ONLINE, Order=1,
ConsistentId=ducker03, State=ONLINE, Order=2,
ConsistentId=ducker04, State=ONLINE, Order=3,
--------------------------------------------------------------------------------,
"Number of baseline nodes: 3\n",
"\n",
"Other nodes not found.\n",
"Command [BASELINE] finished with code: 0\n",
"Control utility has completed execution at: 2020-08-03T14:23:57.351\n",
"Execution time: 1558 ms\n"
{code}
> Control utility doesn't print results to stdout.
> ------------------------------------------------
>
> Key: IGNITE-13321
> URL: https://issues.apache.org/jira/browse/IGNITE-13321
> Project: Ignite
> Issue Type: Bug
> Components: control.sh
> Affects Versions: 2.10
> Reporter: Ivan Daschinskiy
> Priority: Blocker
> Fix For: 2.10
>
>
> After merging
> [IGNITE-13123|https://issues.apache.org/jira/browse/IGNITE-13123]
> {{control.sh}} doesn't work properly either in dev mode, or in release mode.
> Specifically,
> no output printed in stdout. However,
> For example, incorrect output for {{control.sh --activate}} after commit s:
> {code:sh}
> Control utility [ver. 2.10.0-SNAPSHOT#20200803-sha1:DEV],
> 2020 Copyright(C) Apache Software Foundation,
> User: ducker,
> Time: 2020-08-03T14:24:33.193,
> Command [BASELINE] started,
> Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
>
> --------------------------------------------------------------------------------
> {code}
> Correct output for {{control.sh --activate}} before commit is:
> {code}
> Control utility [ver. 2.8.1#20200521-sha1:86422096],
> 2020 Copyright(C) Apache Software Foundation,
> User: ducker,
> Time: 2020-08-03T14:23:55.793,
> Command [BASELINE] started,
> Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes,
>
> --------------------------------------------------------------------------------,
>
> Cluster state: active,
> Current topology version: 3,
> Baseline auto adjustment disabled: softTimeout=300000
> Current topology version: 3 (Coordinator: ConsistentId=ducker02, Order=1)
> Baseline nodes:
> ConsistentId=ducker02, State=ONLINE, Order=1,
> ConsistentId=ducker03, State=ONLINE, Order=2,
> ConsistentId=ducker04, State=ONLINE, Order=3,
> --------------------------------------------------------------------------------,
>
> Number of baseline nodes: 3,
> Other nodes not found.,
> Command [BASELINE] finished with code: 0,
> Control utility has completed execution at: 2020-08-03T14:23:57.351,
> Execution time: 1558 ms
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
