集群&集群发现

Last updated 5 years ago

Was this helpful?

集群&集群发现

Cluster

{
  "name": "...",
  "type": "...",
  "eds_cluster_config": "{...}",
  "connect_timeout": "{...}",
  "per_connection_buffer_limit_bytes": "{...}",
  "lb_policy": "...",
  "hosts": [],
  "health_checks": [],
  "max_requests_per_connection": "{...}",
  "circuit_breakers": "{...}",
  "tls_context": "{...}",
  "http_protocol_options": "{...}",
  "http2_protocol_options": "{...}",
  "dns_refresh_rate": "{...}",
  "dns_lookup_family": "...",
  "dns_resolvers": [],
  "outlier_detection": "{...}",
  "cleanup_interval": "{...}",
  "upstream_bind_config": "{...}",
  "lb_subset_config": "{...}",
  "ring_hash_lb_config": "{...}",
  "transport_socket": "{...}"
}

只能设置http_protocol_options和http2_protocol_options其中一个配置。
只能设置http_protocol_options和http2_protocol_options其中一个配置。

Cluster.EdsClusterConfig

只有当集群发现类型是EDS时才有效。

{
  "eds_config": "{...}",
  "service_name": "..."
}

Cluster.OutlierDetection

{
  "consecutive_5xx": "{...}",
  "interval": "{...}",
  "base_ejection_time": "{...}",
  "max_ejection_percent": "{...}",
  "enforcing_consecutive_5xx": "{...}",
  "enforcing_success_rate": "{...}",
  "success_rate_minimum_hosts": "{...}",
  "success_rate_request_volume": "{...}",
  "success_rate_stdev_factor": "{...}",
  "consecutive_gateway_failure": "{...}",
  "enforcing_consecutive_gateway_failure": "{...}"
}

Cluster.LbSubsetConfig

（可选）将此群集中的端口划分为由端口元数据定义的子集，并按路由和加权群集元数据进行选择。

{
  "fallback_policy": "...",
  "default_subset": "{...}",
  "subset_selectors": []
}

```
{ "subset_selectors": [
  { "keys": [ "version" ] },
  { "keys": [ "stage", "hardware_type" ] }
]}
```
当来自所选路由和加权群集的元数据包含与子集的元数据相同的key和value时，匹配子集。相同的主机可能出现在多个子集中。

Cluster.LbSubsetConfig.LbSubsetSelector

子集的规格

{
  "keys": []
}

keys

Cluster.LbSubsetConfig.LbSubsetFallbackPolicy (Enum)

如果选择NO_FALLBACK，则会报告等效于没有健康主机的结果。如果选择了ANY_ENDPOINT，则可能会返回任何群集端点（取决于策略，健康检查等）。如果选择DEFAULT_SUBSET，则在匹配来自default_subset字段的值的端口上执行负载平衡。

NO_FALLBACK
(DEFAULT)
ANY_ENDPOINT
DEFAULT_SUBSET

Cluster.RingHashLbConfig

{
  "minimum_ring_size": "{...}",
  "deprecated_v1": "{...}"
}

Cluster.RingHashLbConfig.DeprecatedV1

{
  "use_std_hash": "{...}"
}

use_std_hash

Cluster.DiscoveryType (Enum)

STATIC (DEFAULT) 静态发现类型
STRICT_DNS 严格的DNS发现类型
LOGICAL_DNS 逻辑DNS发现类型
EDS 服务发现类型
ORIGINAL_DST 原始目标发现类型

Cluster.LbPolicy (Enum)

ROUND_ROBIN (DEFAULT) 轮循负载平衡策略
LEAST_REQUEST 最小请求负载平衡策略
RING_HASH 环形散列负载平衡策略
RANDOM 随机负载平衡策略
ORIGINAL_DST_LB 原始目标负载平衡策略

Cluster.DnsLookupFamily (Enum)

当选择V4_ONLY时，DNS解析器将仅执行IPv4系列中的地址查找。如果选择V6_ONLY，则DNS解析程序将仅执行IPv6系列中的地址查找。如果指定了AUTO，则DNS解析器将首先执行IPv6系列中的地址查找，然后回退到IPv4系列中的地址查找。对于STRICT_DNS和LOGICAL_DNS以外的集群类型，此设置将被忽略。

AUTO
(DEFAULT)
V4_ONLY
V6_ONLY

UpstreamBindConfig

包含Envoy的可扩展地址结构，在与上游建立连接时绑定。

{
  "source_address": "{...}"
}

source_address

CircuitBreakers

可以为每个定义的优先级单独指定断路设置。

{
  "thresholds": []
}

thresholds

CircuitBreakers.Thresholds

为RoutingPriority定义断路阈值设置。

{
  "priority": "...",
  "max_connections": "{...}",
  "max_pending_requests": "{...}",
  "max_requests": "{...}",
  "max_retries": "{...}"
}

Previous监听&监听发现 Next服务发现

Last updated 5 years ago

Was this helpful?