Skip to content

[RateLimiter] Create & use a custom cache pool #38365

@wouterj

Description

@wouterj

See #38177 (comment) :

this should indeed be a pool based on cache.app rather than using cache.app directly, to avoid key conflicts (keys must be unique inside the pool, so sharing the same pool between multiple places is a bad idea as they need to cooperate on their naming of keys)
see

->set('cache.messenger.restart_workers_signal')
->parent('cache.app')
->private()
->tag('cache.pool')
for the service definition of an existing one

In the rate limiter config, we're also using cache.app directly. This should be changed to using a custom cache pool:

->scalarNode('cache_pool')
->info('The cache pool to use for storing the current limiter state')
->defaultValue('cache.app')
->end()

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions