[
https://issues.apache.org/jira/browse/IGNITE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630894#comment-16630894
]
ASF GitHub Bot commented on IGNITE-9501:
----------------------------------------
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4860
IGNITE-9501 Backward compatibility fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-9501-compatibility-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4860.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 #4860
----
commit 88c38d0c000154735c1e1aa7c092ddb37dbf0c90
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-09-27T18:50:31Z
IGNITE-9501 Backward compatibility fix.
----
> Exclude newly joining nodes from exchange latch
> ------------------------------------------------
>
> Key: IGNITE-9501
> URL: https://issues.apache.org/jira/browse/IGNITE-9501
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.5
> Reporter: Pavel Kovalenko
> Assignee: Pavel Kovalenko
> Priority: Major
> Fix For: 2.7
>
>
> Currently, we're waiting for latch completion from newly joining nodes.
> However, such nodes don't have any updates to be synced on wait partitions
> release. Newly joining nodes may start their caches before exchange latch
> creation and this can delay exchange process.
> We should explicitly ignore such nodes and don't include them into latch
> participants.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
