21e8fcad25
* feat: rework cache refresh logic Instead of issuing a single refresh when a GET request for a cached key comes in, start a background job (using some efficient logic to not overload tokio) per key that refreshes the key using some exponential backoff. The timer is reset a new GET request comes in. This has the following advantages: - our backoff logic decorrelates the requests - the longer a key was not used, the less often it will be updated All test (esp. integration tests) as adjusted accordingly, mostly to account for the fact that no extra GET is required to start the refresh timer. Closes #5720. * docs: improve Co-authored-by: Andrew Lamb <alamb@influxdata.com> * refactor: simplify rng overwrite Co-authored-by: Andrew Lamb <alamb@influxdata.com> |
||
|---|---|---|
| .. | ||
| cache | ||
| chunk | ||
| ingester | ||
| namespace | ||
| system_tables | ||
| table | ||
| database.rs | ||
| handler.rs | ||
| lib.rs | ||
| poison.rs | ||
| query_log.rs | ||
| server.rs | ||
| tombstone.rs | ||