[jira] [Commented] (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:comment-tabpanel=17170731#comment-17170731
]
Alexey Kuznetsov commented on IGNITE-13321:
---
[~ivandasch] I revrted my commit. Please close this issue.
I will rework my fix to not break control utility.
> 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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170716#comment-17170716
]
Ivan Daschinskiy commented on IGNITE-13321:
---
[~kuaw26] Alexey, as a PMC member, may be you can provide quick fix? Can you
revert your commit? This issue blocks ignite functional test activity
(ducktape), because control.sh in master branch is broken.
> 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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170683#comment-17170683
]
Alexey Kuznetsov commented on IGNITE-13321:
---
I'll investigate and fix this issue.
> 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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170677#comment-17170677
]
Kirill Tkalenko commented on IGNITE-13321:
--
[~kuaw26] I will assign you a ticket because you did IGNITE-13262.
> 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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170672#comment-17170672
]
Kirill Tkalenko commented on IGNITE-13321:
--
OK, you can roll back IGNITE-13262. Then do the right thing.
> 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: Kirill Tkalenko
>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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170666#comment-17170666
]
Ivan Daschinskiy commented on IGNITE-13321:
---
Yes, but if set -DQUITE=false, we see output with formatted pattern. This is
not expected behaviour. IgniteLogger is created not for CMD output, so it is
not a good choice right now for control utility.
> 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: Kirill Tkalenko
>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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170663#comment-17170663
]
Kirill Tkalenko commented on IGNITE-13321:
--
A little more analyzed, [1] returns {color:red}false{color}, but in [2]
"*cfgUrl*" is not {color:red}null{color}.
[1] - org.apache.ignite.logger.java.JavaLogger#isConfigured
[2] - org.apache.ignite.logger.java.JavaLogger#defaultConfiguration
> 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: Kirill Tkalenko
>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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170662#comment-17170662
]
Ivan Daschinskiy commented on IGNITE-13321:
---
1) Firstly, we should fix blocker.
2) When blocker is fixed, we can think about refactoring, beauty of code,
modularization, KISS, SOLID etc. etc.
> 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: Kirill Tkalenko
>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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170660#comment-17170660
]
Kirill Tkalenko commented on IGNITE-13321:
--
I think we can think a little about right decision.
> 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: Kirill Tkalenko
>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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170655#comment-17170655
]
Ivan Daschinskiy commented on IGNITE-13321:
---
Confirm, that reverting back to bare JUL works. I don't suppose, that here we
should use {{IgniteLogger}} as is. It is used for another purpose, has
additional not needed functionality, add patterns to stdout etc. Currently we
can simply partialy revert offending commit.
> 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: Kirill Tkalenko
>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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170634#comment-17170634
]
Kirill Tkalenko commented on IGNITE-13321:
--
[~ivandasch] I found that the system property is missing
"java.util.logging.config.file".
This is where it is checked:
{code:java}
org.apache.ignite.logger.java.JavaLogger#isConfigured
{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
>Assignee: Kirill Tkalenko
>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.
> 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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170620#comment-17170620
]
Ivan Daschinskiy commented on IGNITE-13321:
---
[~ktkale...@gridgain.com] Thanks for debugging this issue. And sorry for
linking your patch to it. Are you going to fix it or to reassign to other
member of community?
> 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: Kirill Tkalenko
>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.
> 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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170614#comment-17170614
]
Kirill Tkalenko commented on IGNITE-13321:
--
Hi, [~ivandasch]!
I tried to analyze code and compare it with 2.8.1 and found that problem is
changing logging in IGNITE-13262, for
{code:java}
org.apache.ignite.internal.client.impl.connection.GridClientTopology#log
org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter#log
{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
>Assignee: Kirill Tkalenko
>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.
> 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=30
>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)
[jira] [Commented] (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:comment-tabpanel=17170080#comment-17170080
]
Ivan Daschinskiy commented on IGNITE-13321:
---
[~ktkale...@gridgain.com] Could you please take a look over it?
> 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.
> 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=30
>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)
