[
https://issues.apache.org/jira/browse/IGNITE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695623#comment-16695623
]
Sergey Chugunov edited comment on IGNITE-10374 at 11/22/18 7:40 AM:
--------------------------------------------------------------------
This behavior emerged after rebalancing process was optimized (in IGNITE-7165)
to tolerate client node join/leave: as clients don't affect affinity in any way
rebalancing no longer gets restarted.
was (Author: sergey-chugunov):
This behavior emerged after rebalancing process was optimized (in IGNITE-7165)
to tolerate client node join/leave: as clients don't affect affinity in any way
rebalancing no longer gets cancelled.
> 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)
