status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

website: put a note on the website re vault with 1.7.0 and 1.6.3 (#7295)

This commit is contained in:
Hans Hasselberg 2020-02-13 20:42:36 +01:00 committed by GitHub
parent 315d57bfb1
commit 4fb41ba9c0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/upgrade-specific.html.md
View File

@ -42,6 +42,16 @@ Consul has changed the semantics of query counts in its [telemetry](/docs/agent/
measure when blocking queries polled for more data. The gauge `consul.rpc.queries_blocking` has been added for a more measure when blocking queries polled for more data. The gauge `consul.rpc.queries_blocking` has been added for a more
to more precisely capture the view of *active* blocking queries. to more precisely capture the view of *active* blocking queries.
### Vault: default for `http_max_conns_per_client` to low to run Vault properly
Consul 1.7.0 introduced limiting of connections per client ((docs)[https://www.consul.io/docs/agent/options.html#http_max_conns_per_client]). The default is 100, but Vault allows up to 128 which causes problems. If you want to use Vault with Consul 1.7.0, you should change it to 200. Starting with Consul 1.7.1 this is the new default.
## Consul 1.6.3
### Vault: default for `http_max_conns_per_client` to low to run Vault properly
Consul 1.6.3 introduced limiting of connections per client ((docs)[https://www.consul.io/docs/agent/options.html#http_max_conns_per_client]). The default is 100, but Vault allows up to 128 which causes problems. If you want to use Vault with Consul 1.6.3, you should change it to 200. Starting with Consul 1.6.4 this is the new default.
## Consul 1.6.0 ## Consul 1.6.0
#### Removal of Deprecated Features #### Removal of Deprecated Features