Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo #9388

Merged
merged 1 commit into from
Dec 18, 2019
Merged

Fix typo #9388

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/root/intro/arch_overview/upstream/aggregate_cluster.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ policy to cluster using MAGLEV, from cluster with 0.1s connection timeout to clu
connection timeout, etc. Aggregate cluster loosely couples multiple clusters by referencing their
name in the :ref:`configuration <envoy_api_msg_config.cluster.aggregate.v2alpha.ClusterConfig>`. The
fallback priority is defined implicitly by the ordering in the :ref:`clusters list <envoy_api_field_config.cluster.aggregate.v2alpha.ClusterConfig.clusters>`.
Aggregate cluster uses tiered load balancing. The load balancer chooses cluster and piority first
Aggregate cluster uses tiered load balancing. The load balancer chooses cluster and priority first
and then delegates the load balancing to the load balancer of the selected cluster. The top level
load balancer reuses the existing load balancing algorithm by linearizing the priority set of
multiple clusters into one.
Expand Down