[
https://issues.apache.org/jira/browse/IGNITE-17384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627198#comment-17627198
]
Ilya Shishkov edited comment on IGNITE-17384 at 11/1/22 2:58 PM:
-----------------------------------------------------------------
[~nizhikov], there are some updates:
It seems, that results are printed into {{idle_verify*.txt}} files *_only in
case of exceptions_* during check, eg. when some nodes leaves a cluster or
cluster is not idle. So, even if partition conflicts present on the cluster,
they will not be printed to logs or {{idle_verify*.txt}} files.
I think, that it is a bug and partition conflicts should be always printed into
logs or such text files.
was (Author: shishkovilja):
[~nizhikov], there are some updates:
It seems, that results are printed into {{idle_verify*.txt}} files only in case
of exceptions during check, eg. when some nodes leaves a cluster or cluster is
not idle. So, even if partition conflicts present on the cluster, they will not
be printed to logs or {{idle_verify*.txt}} files.
I think, that it is a bug and partition conflicts should be always printed into
logs or such text files.
> IdleVerify: print partition conflicts into control-utility.log
> --------------------------------------------------------------
>
> Key: IGNITE-17384
> URL: https://issues.apache.org/jira/browse/IGNITE-17384
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh
> Affects Versions: 2.13
> Reporter: Ilya Shishkov
> Priority: Minor
> Labels: ise
> Fix For: 2.15
>
>
> Currently, when you call {{control.sh --cache idle_verify}}, partition
> conflicts will be printed into standard output, but they are missing in the
> control-utility.log. So, if you have many conflicts, you should additionally
> redirect output to a file in order to send information for a further analysis.
> It would be more convenient to print partition conflicts in the
> control-utility.log file too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
