[
https://issues.apache.org/jira/browse/IGNITE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506670#comment-16506670
]
ASF GitHub Bot commented on IGNITE-8757:
----------------------------------------
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/4162
IGNITE-8757 idle_verify utility doesn't show both update counter and …
…hash conflict
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8757
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4162.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4162
----
commit af11c6925ef5c42ebf5273e80638e162fec9f35e
Author: Ivan Rakov <irakov@...>
Date: 2018-06-08T23:02:13Z
IGNITE-8757 idle_verify utility doesn't show both update counter and hash
conflict
----
> idle_verify utility doesn't show both update counter and hash conflicts
> -----------------------------------------------------------------------
>
> Key: IGNITE-8757
> URL: https://issues.apache.org/jira/browse/IGNITE-8757
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Rakov
> Assignee: Ivan Rakov
> Priority: Major
>
> If there are two partitions in cluster, one with different update counters
> and one with different data, idle_verify will show only partition with broken
> counters. We should show both for better visibility.
> We should also show notify user about rebalancing partitions that were
> excluded from analysis.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
