You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/06/20 09:36:00 UTC
[jira] [Created] (IGNITE-5552) ServiceProcessor recalculates all
service assignments even if there is a pending topology change
Alexey Goncharuk created IGNITE-5552:
----------------------------------------
Summary: 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
Fix For: 2.2
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)