Traffic Governance and Protection: Threshold Configuration
Effective traffic governance and protection rely on properly configuring thresholds—either a fixed global limit that stays constant regardless of node count, or a per‑machine allocation that scales the total capacity as nodes are added or removed—to prevent sudden surges from overwhelming services and ensure high availability.
Resources are limited, prediction is necessary, but unexpected events can also occur. We can see that some major production accidents are often overwhelmed by sudden traffic surges, making traffic governance and protection particularly important. Prevention is better than cure, ensuring high availability of services requires attention.
This article introduces the concept of traffic governance and protection, focusing on the configuration of thresholds. There are two types of cluster threshold settings: global threshold and per-machine allocation.
Global threshold represents the total threshold traffic that the entire cluster can withstand, which does not change with the change of nodes. For example: if the global threshold is set to 500, regardless of how many nodes the application is deployed on, the total traffic threshold remains 500 unchanged.
Per-machine allocation refers to the threshold that each node can withstand. As the number of nodes increases or decreases, the threshold of the Token Server will dynamically change. For example: if the per-machine allocation is set to 100, the total flow control threshold for a 3-node cluster is 300; after expanding by two nodes, the total threshold becomes 500.
HelloTech
Official Hello technology account, sharing tech insights and developments.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.