[
https://issues.apache.org/jira/browse/IGNITE-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060659#comment-16060659
]
ASF GitHub Bot commented on IGNITE-5552:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2182
IGNITE-5552: ServiceProcessor recalculates all service assignments even if
there is a pending topology change
Fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5552
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2182.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 #2182
----
commit 3464a79b560106d47dd5cf0bae4b21dce7778e9d
Author: Andrey V. Mashenkov <[email protected]>
Date: 2017-06-21T16:30:27Z
IGNITE-5552: ServiceProcessor recalculates all service assignments even if
there is a pending topology change.
----
> ServiceProcessor recalculates all service assignments even if there is a
> pending topology change
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-5552
> URL: https://issues.apache.org/jira/browse/IGNITE-5552
> Project: Ignite
> Issue Type: Improvement
> Components: managed services
> Affects Versions: 1.7
> Reporter: Alexey Goncharuk
> Assignee: Andrew Mashenkov
> Fix For: 2.1
>
>
> This behavior was observed in a real cluster of hundreds of nodes and
> hundreds of services.
> After a ~30 new nodes startup, we expected node singletons to be deployed
> immediately, but the services were deployed with ~4hr delay on last nodes.
> The reason for this is the fact that ALL service deployments are recalculated
> on ALL discovery events. In this case, a single discovery event was processed
> in a time span of 2-5 minutes, which with the lateAffinityAssignment=true
> yielded a 4hr delay for the last node.
> The quick change that may improve things a lot is aborting current assignment
> calculations if there is a pending discovery event needs to be processed.
> The rest of the optimizations are put to
> https://issues.apache.org/jira/browse/IGNITE-5551
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
