parent
62b76c837c
commit
8601ffb98e
|
|
@ -1046,17 +1046,3 @@ Environment variable: `INFLUXDB_TLS_MIN_VERSION`
|
|||
The maximum version of the TLS protocol that will be negotiated. Valid values include: `tls1.0`, `tls1.1`, and `tls1.2`. If not specified, `max-version` is the maximum TLS version specified in the [Go `crypto/tls` package](https://golang.org/pkg/crypto/tls/#pkg-constants). In this example, `tls1.2` specifies the maximum version as TLS 1.2, which is consistent with the behavior of previous InfluxDB releases.
|
||||
|
||||
Environment variable: `INFLUXDB_TLS_MAX_VERSION`
|
||||
|
||||
|
||||
|
||||
<!-- #### max-fetch = 10
|
||||
|
||||
The maximum number of shards that a single data node will copy or repair in parallel.
|
||||
|
||||
Environment variable: `INFLUXDB_ANTI_ENTROPY_MAX_FETCH`
|
||||
|
||||
> Having `max-fetch=10` with higher numbers of shards (100+) can add significant overhead to running nodes.
|
||||
> The more shards you have, the lower this should be set.
|
||||
> If AE is left enabled while lowering your `max-fetch`, you will initially see
|
||||
> higher CPU load as new shard digest files are created.
|
||||
> The added load will drop off after shard digests are completed for existing shards. -->
|
||||
|
|
|
|||
|
|
@ -1208,15 +1208,3 @@ Environment variable: `INFLUXDB_TLS_MIN_VERSION`
|
|||
The maximum version of the TLS protocol that will be negotiated. Valid values include: `tls1.0`, `tls1.1`, and `tls1.2`. If not specified, `max-version` is the maximum TLS version specified in the [Go `crypto/tls` package](https://golang.org/pkg/crypto/tls/#pkg-constants). In this example, `tls1.2` specifies the maximum version as TLS 1.2, which is consistent with the behavior of previous InfluxDB releases.
|
||||
|
||||
Environment variable: `INFLUXDB_TLS_MAX_VERSION`
|
||||
|
||||
<!-- #### max-fetch = 10
|
||||
|
||||
The maximum number of shards that a single data node will copy or repair in parallel.
|
||||
|
||||
Environment variable: `INFLUXDB_ANTI_ENTROPY_MAX_FETCH`
|
||||
|
||||
> Having `max-fetch=10` with higher numbers of shards (100+) can add significant overhead to running nodes.
|
||||
> The more shards you have, the lower this should be set.
|
||||
> If AE is left enabled while lowering your `max-fetch`, you will initially see
|
||||
> higher CPU load as new shard digest files are created.
|
||||
> The added load will drop off after shard digests are completed for existing shards. -->
|
||||
|
|
|
|||
Loading…
Reference in New Issue