com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Scale Up In-flight Request Count Workflow

Owned by Former user (Deleted)
May 28, 2014
1 min read

The workflow involved in creating a tenant is illustrated in the diagram below:

The workflow involved in scaling up based on the in-flight request count is as follows:

  1. In the scale-up workflow based on the value of requests-in flight, Load Balancer (LB) sends the in-flight request count to Complex Event Processor (CEP) using the thrift protocol.
  2. The CEP will aggregate the in-flight request count continuously and will publish the summarized health statistics to the Message broker (MB). 
  3. The Auto-scaler (AS), which will be subscribed to the Summarized Health Stats topic on MB will obtain the values and using the Drools engine, and it will check the auto-scaling and deployment policies for the functionality required based on the count and the threshold values defined. 
  4. When it is required to scale up, AS will send the scale up and create instance information to the Cloud Controller (CC). 
  5. The CC creates the additional new instances accordingly and sends the details about the created instances to the IaaS.
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.