You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Daschinskiy (Jira)" <ji...@apache.org> on 2020/08/04 11:31:00 UTC
[jira] [Resolved] (IGNITE-13321) Control utility doesn't print
results to stdout.
[ https://issues.apache.org/jira/browse/IGNITE-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Daschinskiy resolved IGNITE-13321.
---------------------------------------
Resolution: Fixed
[~kuaw26] Thank, you.
> 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
> Assignee: Alexey Kuznetsov
> Priority: Blocker
> Fix For: 2.10
>
>
> After merging [IGNITE-13262|https://issues.apache.org/jira/browse/IGNITE-13262 ] {{control.sh}} doesn't work properly either in dev mode, or in release mode. Specifically, no output printed in stdout.
> For example, incorrect output for {{control.sh -baseline set}} after commit is:
> {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 -baseline set}} 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}
> However, command seems to execute and baseline actually changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)