Struct TenantStoreConfig 

pub struct TenantStoreConfig {
    pub per_tenant: TaskStoreConfig,
    pub max_tenants: usize,
}

Configuration for TenantAwareInMemoryTaskStore.

Fields

per_tenant: TaskStoreConfig

Store configuration for every tenant without an override set via TenantAwareInMemoryTaskStore::with_tenant_override.

max_tenants: usize

Maximum number of tenants allowed. Default: 1000.

What it prevents, and what it converts the problem into

It bounds memory against tenant enumeration — that much was already written here. What was not: a tenant id is whatever the handler’s tenant resolution produced, and every bundled TenantResolver reads client-controlled input (see that module’s security section). So a caller who can send N distinct tenant ids creates N partitions, and once this cap is reached every new tenant is refused, including legitimate ones. The memory bound holds; availability for new tenants is what pays for it.

prune_empty_tenants is the reclamation path, and it is not automatic — nothing calls it — and it only removes partitions whose task count is zero. A partition created by a save holds a task until that task is evicted, so at the shipped one-hour TTL a burst of 1,000 junk tenant ids locks out new tenants for an hour even with pruning scheduled.

The mitigation is the same precondition the resolvers state: the tenant id must come from something authenticated, not from a header a client chose. Raise this only alongside that.

Trait Implementations

impl Clone for TenantStoreConfig

fn clone(&self) -> TenantStoreConfig

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for TenantStoreConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for TenantStoreConfig

fn default() -> Self

Returns the “default value” for a type.