Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-5552

ServiceProcessor recalculates all service assignments even if there is a pending topology change

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.7
    • Fix Version/s: 2.1
    • Component/s: managed services
    • Labels:
      None

      Description

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                amashenkov Andrew Mashenkov
                Reporter:
                agoncharuk Alexey Goncharuk
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: