consul/logging
Dan Upton 1c2c975b0b
xDS Load Balancing (#14397)
Prior to #13244, connect proxies and gateways could only be configured by an
xDS session served by the local client agent.

In an upcoming release, it will be possible to deploy a Consul service mesh
without client agents. In this model, xDS sessions will be handled by the
servers themselves, which necessitates load-balancing to prevent a single
server from receiving a disproportionate amount of load and becoming
overwhelmed.

This introduces a simple form of load-balancing where Consul will attempt to
achieve an even spread of load (xDS sessions) between all healthy servers.
It does so by implementing a concurrent session limiter (limiter.SessionLimiter)
and adjusting the limit according to autopilot state and proxy service
registrations in the catalog.

If a server is already over capacity (i.e. the session limit is lowered),
Consul will begin draining sessions to rebalance the load. This will result
in the client receiving a `RESOURCE_EXHAUSTED` status code. It is the client's
responsibility to observe this response and reconnect to a different server.

Users of the gRPC client connection brokered by the
consul-server-connection-manager library will get this for free.

The rate at which Consul will drain sessions to rebalance load is scaled
dynamically based on the number of proxies in the catalog.
2022-09-09 15:02:01 +01:00
..
monitor bulk rewrite using this script 2022-01-20 10:46:23 -06:00
gated_writer.go
gated_writer_test.go
grpc.go grpc: move gRPC INFO logs to be emitted as TRACE logs from Consul (#10395) 2021-06-14 15:13:58 -05:00
grpc_test.go grpc: move gRPC INFO logs to be emitted as TRACE logs from Consul (#10395) 2021-06-14 15:13:58 -05:00
log_levels.go
logfile.go
logfile_test.go
logger.go Fix incorrect severity syslog messages (#12079) 2022-04-14 15:51:00 -07:00
logger_test.go bulk rewrite using this script 2022-01-20 10:46:23 -06:00
names.go xDS Load Balancing (#14397) 2022-09-09 15:02:01 +01:00
syslog.go Fix incorrect severity syslog messages (#12079) 2022-04-14 15:51:00 -07:00
syslog_test.go Fix incorrect severity syslog messages (#12079) 2022-04-14 15:51:00 -07:00
syslog_unsupported_test.go Fix incorrect severity syslog messages (#12079) 2022-04-14 15:51:00 -07:00