Application-layer throttling
In the LDC architecture, application-layer throttling rules are defined by UID allocation and cell traffic ratio. The UID allocation specifies the UID fragment (00 to 99) corresponding to each regional zone group (RZoneGroup). The cell traffic ratio specifies the traffic weight of the zone group (GZoneGroup, CZoneGroup, or RZoneGroup) occupied by each cell.
The traffic allocation in the preceding figure indicates that both RZones (RZ01 and RZ02) carry traffic. Requests corresponding to the UID fragment of 0 to 19 are routed to RZ01, and requests corresponding to the UID fragment of 20 to 99 are routed to RZ02. RZ01 and RZ02 each contain one cell: RZ01A and RZ02A respectively. Therefore, each cell carries 100% of the traffic in the corresponding zone. GZ01 contains two cells: GZ01A and GZ01B. Each cell carries 50% of the traffic in the zone.
Formal traffic
Stress testing traffic and formal traffic are managed in the same way, except that stress testing traffic rules are applicable only to stress testing scenarios.
Stress testing traffic is supported only in Apsara Stack.
In the left-side navigation pane, choose Manage Traffic > Application Layer. On the Traffic tab, the system displays the last global traffic rule that is successfully pushed, that is, the global traffic snapshot that is currently in effect. During environment initialization, no information will be displayed if no traffic or global traffic rule has been pushed.
Rule configuration
Click Rule Configuration to go to the Traffic Rule Configuration page. The page displays the currently configured rules, some of which may have not taken effect.
Click a zone or UID fragment to go to the edit page, and specify the following configuration information:
For an RZone cell, configure its UID fragment and traffic weight.
For a GZone cell, configure its traffic weight.
NoteMake sure that the total traffic ratio of all cells is 100% after the adjustment. A UID fragment ranges from 00 to 99.
After you adjust the traffic weight or UID fragment, click Save for the configuration to take effect.
Traffic rule push
In the left-side navigation pane, choose Manage Traffic > Application Layer.
Click Rule Configuration to go to the Traffic Rule Configuration page.
Click Traffic Rule Push to go to the Traffic Rule Push page.
Specify the following push configurations:
Rule Details: The system automatically generates rule text in JSON format based on the current traffic rule. The text serves as a parameter for pushing traffic to applications or central services to make all applications or a specified application aware of traffic changes.
Cell: Select All Cells or Specify Cell. You can specify a cell to push the rule. The rule takes effect only for the applications in the cell.
Target Component: Select Middleware or Unified Access Gateway. In general, the two components must be notified of all changes to traffic rules, except in gray-box testing scenarios.
Target Application: Select a target application to be notified of rule changes. In general, we recommend that you choose to push the traffic rule to all applications. However, in gray-box testing scenarios, you can specify some applications to push the new traffic rule for traffic verification.
Overwrite Other Applications or Not: This option takes effect when you choose to push the traffic rule to all applications. If this option is enabled, the currently active rules of the applications are overwritten with the newly configured traffic rule. If this option is disabled, the existing rules that are separately pushed to the applications are retained.
Click Push to push the currently configured traffic rule.
Push history
You can view the records and status of the last push on the Push History tab.
Associated Application: indicates the target application selected for the push. If the traffic rule is pushed to all applications, routeClient is displayed.
Target Cell/IDC: indicates the target IDC or cell.
Rule Type: Only routing rules are supported.
Push Results: indicates whether the push is successful or fails. If the push fails, the error message will display possible causes for troubleshooting.