Skip to content

Commit 4db89ff

Browse files
Add new --healthcheck-dial-concurrency flag from pr #15053
Signed-off-by: Tim Vaillancourt <tvaillancourt@slack-corp.com>
1 parent d88a238 commit 4db89ff

3 files changed

Lines changed: 3 additions & 0 deletions

File tree

content/en/docs/20.0/reference/programs/vtcombo/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -181,6 +181,7 @@ vtcombo [flags]
181181
--grpc_server_keepalive_timeout duration After having pinged for keepalive check, the server waits for a duration of Timeout and if no activity is seen even after that the connection is closed. (default 10s)
182182
--grpc_use_effective_callerid If set, and SSL is not used, will set the immediate caller id from the effective caller id's principal.
183183
--health_check_interval duration Interval between health checks (default 20s)
184+
--healthcheck-dial-concurrency int Maximum concurrency of new healthcheck connections. This should be less than the golang max thread limit of 10000. (default 1024)
184185
--healthcheck_retry_delay duration health check retry delay (default 2ms)
185186
--healthcheck_timeout duration the health check timeout period (default 1m0s)
186187
--heartbeat_enable If true, vttablet records (if master) or checks (if replica) the current time of a replication heartbeat in the sidecar database's heartbeat table. The result is used to inform the serving state of the vttablet via healthchecks.

content/en/docs/20.0/reference/programs/vtctld/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -101,6 +101,7 @@ vtctld \
101101
--grpc_server_keepalive_enforcement_policy_permit_without_stream gRPC server permit client keepalive pings even when there are no active streams (RPCs)
102102
--grpc_server_keepalive_time duration After a duration of this time, if the server doesn't see any activity, it pings the client to see if the transport is still alive. (default 10s)
103103
--grpc_server_keepalive_timeout duration After having pinged for keepalive check, the server waits for a duration of Timeout and if no activity is seen even after that the connection is closed. (default 10s)
104+
--healthcheck-dial-concurrency int Maximum concurrency of new healthcheck connections. This should be less than the golang max thread limit of 10000. (default 1024)
104105
-h, --help help for vtctld
105106
--jaeger-agent-host string host and port to send spans to. if empty, no tracing will be done
106107
--keep_logs duration keep logs for this long (using ctime) (zero to keep forever)

content/en/docs/20.0/reference/programs/vtgate/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,7 @@ vtgate \
114114
--grpc_server_keepalive_time duration After a duration of this time, if the server doesn't see any activity, it pings the client to see if the transport is still alive. (default 10s)
115115
--grpc_server_keepalive_timeout duration After having pinged for keepalive check, the server waits for a duration of Timeout and if no activity is seen even after that the connection is closed. (default 10s)
116116
--grpc_use_effective_callerid If set, and SSL is not used, will set the immediate caller id from the effective caller id's principal.
117+
--healthcheck-dial-concurrency int Maximum concurrency of new healthcheck connections. This should be less than the golang max thread limit of 10000. (default 1024)
117118
--healthcheck_retry_delay duration health check retry delay (default 2ms)
118119
--healthcheck_timeout duration the health check timeout period (default 1m0s)
119120
-h, --help help for docgen

0 commit comments

Comments
 (0)