Redis: One Pool per usecase

getsentry / relay

Sentry event forwarding and ingestion service.

https://docs.sentry.io/product/relay/

Other

321 stars 91 forks source link

Redis: One Pool per usecase #3829

Open Dav1dde opened 3 months ago

Dav1dde commented 3 months ago

We should split the Regex pools into multiple pools, one per usecase:

Project Config
Cardinality
Quotas
Misc (metric meta)

The configuration should accept the config we already have and use that to configure each pool with these values or share the same pool for all usecases (tbd).

Additionally the config should accept a config for each pool with different configuration values.

loewenheim commented 3 months ago

Can you reiterate which services (EnvelopeProcessor, ProjectCache, RelayStats) need access to which Redis pools?

Dav1dde commented 3 months ago

ProjectCache needs project configs
RelayStats needs all pods (it just exports pool metrics via statsd, we want these stats for all pools)
EnvelopeProcessor needs cardinality, quotas and misc (metric meta)