io.envoyproxy.envoy.config.filter.network.redis_proxy.v2

Interface RedisProxy.ConnPoolSettingsOrBuilder

All Superinterfaces:

com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder

All Known Implementing Classes:

RedisProxy.ConnPoolSettings, RedisProxy.ConnPoolSettings.Builder

Enclosing class:

RedisProxy

public static interface RedisProxy.ConnPoolSettingsOrBuilder
extends com.google.protobuf.MessageOrBuilder

Method Summary

Modifier and Type	Method and Description
boolean	getEnableHashtagging() Use hash tagging on every redis key to guarantee that keys with the same hash tag will be forwarded to the same upstream.
com.google.protobuf.Duration	getOpTimeout() Per-operation timeout in milliseconds.
com.google.protobuf.DurationOrBuilder	getOpTimeoutOrBuilder() Per-operation timeout in milliseconds.
boolean	hasOpTimeout() Per-operation timeout in milliseconds.

Methods inherited from interface com.google.protobuf.MessageOrBuilder

findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

isInitialized

Method Detail

hasOpTimeout

boolean hasOpTimeout()

 Per-operation timeout in milliseconds. The timer starts when the first
 command of a pipeline is written to the backend connection. Each response received from Redis
 resets the timer since it signifies that the next command is being processed by the backend.
 The only exception to this behavior is when a connection to a backend is not yet established.
 In that case, the connect timeout on the cluster will govern the timeout until the connection
 is ready.
 

.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }

getOpTimeout

com.google.protobuf.Duration getOpTimeout()

 Per-operation timeout in milliseconds. The timer starts when the first
 command of a pipeline is written to the backend connection. Each response received from Redis
 resets the timer since it signifies that the next command is being processed by the backend.
 The only exception to this behavior is when a connection to a backend is not yet established.
 In that case, the connect timeout on the cluster will govern the timeout until the connection
 is ready.
 

.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }

getOpTimeoutOrBuilder

com.google.protobuf.DurationOrBuilder getOpTimeoutOrBuilder()

 Per-operation timeout in milliseconds. The timer starts when the first
 command of a pipeline is written to the backend connection. Each response received from Redis
 resets the timer since it signifies that the next command is being processed by the backend.
 The only exception to this behavior is when a connection to a backend is not yet established.
 In that case, the connect timeout on the cluster will govern the timeout until the connection
 is ready.
 

.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }

getEnableHashtagging

boolean getEnableHashtagging()

 Use hash tagging on every redis key to guarantee that keys with the same hash tag will be
 forwarded to the same upstream. The hash key used for determining the upstream in a
 consistent hash ring configuration will be computed from the hash tagged key instead of the
 whole key. The algorithm used to compute the hash tag is identical to the `redis-cluster
 implementation <https://redis.io/topics/cluster-spec#keys-hash-tags>`_.
 Examples:
 * '{user1000}.following' and '{user1000}.followers' **will** be sent to the same upstream
 * '{user1000}.following' and '{user1001}.following' **might** be sent to the same upstream
 

bool enable_hashtagging = 2;