[
https://issues.apache.org/jira/browse/IGNITE-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474056#comment-16474056
]
ASF GitHub Bot commented on IGNITE-8474:
----------------------------------------
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/3990
IGNITE-8474 skipForExchangeMerge property changed to 'true'
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8474
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3990.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 #3990
----
commit 853908d1f9eaaeea9dbbf8dbc1f63c02fc59b4a0
Author: Sergey Chugunov <sergey.chugunov@...>
Date: 2018-05-14T10:52:58Z
IGNITE-8474 skipForExchangeMerge property changed to 'true'
----
> WalStateNodeLeaveExchangeTask prevents merge exchanges on leaving many nodes
> ----------------------------------------------------------------------------
>
> Key: IGNITE-8474
> URL: https://issues.apache.org/jira/browse/IGNITE-8474
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Fix For: 2.6
>
>
> Exchange merge mechanism provides huge optimization when a lot of nodes join
> or leave cluster simultaneously.
> In IGNITE-7003 WalStateNodeLeaveExchangeTask custom exchange task was added
> which is generated for each NODE_LEFT/NODE_FAILED event.
> Because of property skipForExchangeMerge set to false on this task it
> prohibits exchange merge optimization.
> The property needs to be reconsidered and changed if it is not crucial for
> this functionality.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
