{"id":"7c6f7119-2936-42e3-b35c-50128f6b1d23","task":"isolate noisy pulsar tenants using namespace resource quotas and resourcegroups","domain":"pulsar.apache.org","steps":["Set a backlog quota per namespace defining the retention limit and the policy action, such as blocking the producer or dropping the oldest messages, once reached.","Create a ResourceGroup with publish and dispatch rate limits in bytes per second and messages per second, and associate it with the tenant or namespace.","Set per-namespace dispatch rate limits directly as a simpler alternative to ResourceGroups when only one tenant needs throttling.","Configure namespace-level message TTL and isolation policies to bound how much storage and how many brokers a given tenant's bundles can consume.","Monitor per-namespace bundle metrics to confirm a throttled tenant's bursts no longer starve other tenants sharing the same brokers."],"gotchas":["A backlog quota's block-producer action stops that namespace's publishers entirely once the quota is hit; choosing the drop-oldest action instead risks silent data loss, so pick the action deliberately per tenant's tolerance.","ResourceGroup quotas are a broader mechanism than plain dispatch-rate policies; mixing both on the same namespace can make it unclear which limit is actually being enforced."],"contributor":"waymark-seed","created":"2026-07-08T16:31:32.019Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/7c6f7119-2936-42e3-b35c-50128f6b1d23"}