[
https://issues.apache.org/jira/browse/IGNITE-24216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Amelchev updated IGNITE-24216:
-------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> control.sh idle_verify --dump always creates output file on coordinator (the
> oldest server node)
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-24216
> URL: https://issues.apache.org/jira/browse/IGNITE-24216
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Korotkov
> Assignee: Sergey Korotkov
> Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After IGNITE-18312 the command like below always creates the result dump file
> on the coordinator node (on the oldest cluster node in fact) but not on the
> host specified via the
> --host parameter.
> {code:java}
> control.sh --host 10.40.7.145 --cache idle_verify --dump
> {code}
>
> Output of the control.sh says nothing about that which can confuse the user.
> {noformat}
> Control utility [ver. 2.17.0-SNAPSHOT#20241220-sha1:7f160447]
> 2024 Copyright(C) Apache Software Foundation
> User: ducker
> Time: 2025-01-13T18:58:19.980
> Command [CACHE] started
> Arguments: --host 10.40.7.145 --cache idle_verify --dump
> --------------------------------------------------------------------------------
> IdleVerifyDumpTask successfully written output to
> '/mnt/service/work/idle-dump-2025-01-13T18-58-20_557.txt'
> {noformat}
> User would expect that output file is created on localhost or at least on the
> host passed via the --host parameter as it was before transition to thin
> client in control.sh implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
