e52b554c0b
* Add an idle timeout for the server Because tidy operations can be long-running, this also changes all tidy operations to behave the same operationally (kick off the process, get a warning back, log errors to server log) and makes them all run in a goroutine. This could mean a sort of hard stop if Vault gets sealed because the function won't have the read lock. This should generally be okay (running tidy again should pick back up where it left off), but future work could use cleanup funcs to trigger the functions to stop. * Fix up tidy test * Add deadline to cluster connections and an idle timeout to the cluster server, plus add readheader/read timeout to api server |
||
|---|---|---|
| .. | ||
| azure | ||
| cassandra | ||
| cockroachdb | ||
| consul | ||
| couchdb | ||
| dynamodb | ||
| etcd | ||
| file | ||
| gcs | ||
| inmem | ||
| manta | ||
| mssql | ||
| mysql | ||
| postgresql | ||
| s3 | ||
| spanner | ||
| swift | ||
| zookeeper | ||
| cache.go | ||
| latency.go | ||
| physical.go | ||
| physical_access.go | ||
| physical_view.go | ||
| testing.go | ||
| transactions.go | ||
| types.pb.go | ||
| types.proto | ||