[
https://issues.apache.org/jira/browse/IGNITE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605531#comment-16605531
]
ASF GitHub Bot commented on IGNITE-9479:
----------------------------------------
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/4691
IGNITE-9479 Fixed spontaneous rebalance during cache start
…ed logging level
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9479
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4691.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 #4691
----
commit 554e787133991c8f4993b1df5cae9d9e870c4957
Author: Alexey Goncharuk <alexey.goncharuk@...>
Date: 2018-09-06T09:29:12Z
IGNITE-9479 Fixed spontaneous rebalance during cache start and improved
logging level
----
> Spontaneous rebalance may be triggered after a cache start
> ----------------------------------------------------------
>
> Key: IGNITE-9479
> URL: https://issues.apache.org/jira/browse/IGNITE-9479
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Priority: Critical
> Fix For: 2.7
>
>
> As an optimization, we do not run two-phase exchange latch release and do not
> validate partition counters during cache start.
> This can lead to a situation, when rebalance is mistakenly triggered under
> load after a cache start.
> We should treat cache start event the same way as other exchange events that
> need counters sync.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
