ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (IGNITE-5552) ServiceProcessor recalculates all service assignments even if there is a pending topology change
Date Thu, 06 Jul 2017 09:28:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Mashenkov reopened IGNITE-5552:
--------------------------------------

> 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)

Mime
View raw message