|
|
|
syntax = "proto3";
|
|
|
|
|
|
|
|
package envoy.config.cluster.redis;
|
|
|
|
|
|
|
|
option java_package = "io.envoyproxy.envoy.config.cluster.redis";
|
|
|
|
option java_outer_classname = "RedisClusterProto";
|
|
|
|
option java_multiple_files = true;
|
|
|
|
|
|
|
|
import "google/protobuf/duration.proto";
|
|
|
|
import "google/protobuf/wrappers.proto";
|
|
|
|
|
|
|
|
import "validate/validate.proto";
|
|
|
|
|
|
|
|
// [#protodoc-title: Redis Cluster Configuration]
|
|
|
|
// This cluster adds support for `Redis Cluster <https://redis.io/topics/cluster-spec>`_, as part
|
|
|
|
// of :ref:`Envoy's support for Redis Cluster <arch_overview_redis>`.
|
|
|
|
//
|
|
|
|
// Redis Cluster is an extension of Redis which supports sharding and high availability (where a
|
|
|
|
// shard that loses its master fails over to a replica, and designates it as the new master).
|
|
|
|
// However, as there is no unified frontend or proxy service in front of Redis Cluster, the client
|
|
|
|
// (in this case Envoy) must locally maintain the state of the Redis Cluster, specifically the
|
|
|
|
// topology. A random node in the cluster is queried for the topology using the `CLUSTER SLOTS
|
|
|
|
// command <https://redis.io/commands/cluster-slots>`_. This result is then stored locally, and
|
|
|
|
// updated at user-configured intervals.
|
|
|
|
//
|
|
|
|
// Additionally, if
|
|
|
|
// :ref:`enable_redirection<envoy_api_field_config.filter.network.redis_proxy.v2.RedisProxy.ConnPoolSettings.enable_redirection>`
|
|
|
|
// is true, then moved and ask redirection errors from upstream servers will trigger a topology
|
|
|
|
// refresh when they exceed a user-configured error threshold.
|
|
|
|
//
|
|
|
|
// Example:
|
|
|
|
//
|
|
|
|
// .. code-block:: yaml
|
|
|
|
//
|
|
|
|
// name: name
|
|
|
|
// connect_timeout: 0.25s
|
|
|
|
// dns_lookup_family: V4_ONLY
|
|
|
|
// hosts:
|
|
|
|
// - socket_address:
|
|
|
|
// address: foo.bar.com
|
|
|
|
// port_value: 22120
|
|
|
|
// cluster_type:
|
|
|
|
// name: envoy.clusters.redis
|
|
|
|
// typed_config:
|
|
|
|
// "@type": type.googleapis.com/google.protobuf.Struct
|
|
|
|
// value:
|
|
|
|
// cluster_refresh_rate: 30s
|
|
|
|
// cluster_refresh_timeout: 0.5s
|
|
|
|
// redirect_refresh_interval: 10s
|
|
|
|
// redirect_refresh_threshold: 10
|
|
|
|
// [#extension: envoy.clusters.redis]
|
|
|
|
|
|
|
|
message RedisClusterConfig {
|
|
|
|
// Interval between successive topology refresh requests. If not set, this defaults to 5s.
|
api: protoxform tool and API reformat. (#8309)
This patch introduces a new tool, protoxform, that will be the basis of
the v2 -> v3 migration tooling. It operates as a Python protoc plugin,
within the same framework as protodoc, and provides the ability to
operate on protoc AST input and generate proto output.
As a first step, the tool is applied reflexively on v2, and functions as
a formatting tool. In later patches, this will be added to
check_format/fix_format scripts and CI.
Part of #8082.
Risk level: medium (it's possible that some inadvertent wire changes
occur, if they do, this patch should be rolled back).
Testing: manual inspection of diff, bazel test //test/..., some
grep/diff scripts to ensure we haven't lost any comments.
Signed-off-by: Harvey Tuch <htuch@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 08b123a8321d359ea66cbbc0e2926545798dabd3
6 years ago
|
|
|
google.protobuf.Duration cluster_refresh_rate = 1 [(validate.rules).duration = {gt {}}];
|
|
|
|
|
|
|
|
// Timeout for topology refresh request. If not set, this defaults to 3s.
|
api: protoxform tool and API reformat. (#8309)
This patch introduces a new tool, protoxform, that will be the basis of
the v2 -> v3 migration tooling. It operates as a Python protoc plugin,
within the same framework as protodoc, and provides the ability to
operate on protoc AST input and generate proto output.
As a first step, the tool is applied reflexively on v2, and functions as
a formatting tool. In later patches, this will be added to
check_format/fix_format scripts and CI.
Part of #8082.
Risk level: medium (it's possible that some inadvertent wire changes
occur, if they do, this patch should be rolled back).
Testing: manual inspection of diff, bazel test //test/..., some
grep/diff scripts to ensure we haven't lost any comments.
Signed-off-by: Harvey Tuch <htuch@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 08b123a8321d359ea66cbbc0e2926545798dabd3
6 years ago
|
|
|
google.protobuf.Duration cluster_refresh_timeout = 2 [(validate.rules).duration = {gt {}}];
|
|
|
|
|
|
|
|
// The minimum interval that must pass after triggering a topology refresh request before a new
|
|
|
|
// request can possibly be triggered again. Any redirection errors received during one of these
|
|
|
|
// time intervals are ignored. If not set, this defaults to 5s.
|
|
|
|
google.protobuf.Duration redirect_refresh_interval = 3;
|
|
|
|
|
|
|
|
// The number of redirection errors that must be received before
|
|
|
|
// triggering a topology refresh request. If not set, this defaults to 5.
|
|
|
|
google.protobuf.UInt32Value redirect_refresh_threshold = 4;
|
|
|
|
}
|