[
https://issues.apache.org/jira/browse/IGNITE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695630#comment-16695630
]
ASF GitHub Bot commented on IGNITE-10374:
-----------------------------------------
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/5468
IGNITE-10374 if rebalance isn't restarted no need to disable already …
…disabled WAL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10374
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5468.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 #5468
----
commit 22d0ac9f0c9ae16bb9c1ce24c8c6f05b586e1073
Author: Sergey Chugunov <sergey.chugunov@...>
Date: 2018-11-22T07:56:44Z
IGNITE-10374 if rebalance isn't restarted no need to disable already
disabled WAL
----
> Node doesn't own rebalanced partitions on rebalancing finished
> --------------------------------------------------------------
>
> Key: IGNITE-10374
> URL: https://issues.apache.org/jira/browse/IGNITE-10374
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Critical
> Fix For: 2.8
>
>
> Prerequisite: flag *IGNITE_DISABLE_WAL_DURING_REBALANCING* is set to true
> (default value is false).
> Scenario:
> * Node joins the grid and starts rebalancing all cache groups from scratch
> (e.g. all db files of the node were cleaned up during its downtime);
> * One or more client nodes join topology when rebalancing is in progress.
> Expected outcome:
> Rebalance finishes, node owns all received partitions, new affinity is
> applied.
> Actual outcome:
> Rebalance finishes, but node doesn't own any of received partitions, no
> affinity changes take place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
