Create a Pulsar namespace with retention and backlog quota policies

domain: pulsar.apache.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create a namespace under a tenant via: pulsar-admin namespaces create {tenant}/{namespace}
  2. Set a retention policy to prevent data deletion before it is consumed: pulsar-admin namespaces set-retention {tenant}/{namespace} --size 10G --time 7d (size -1 means unlimited; time -1 means unlimited duration).
  3. Set a backlog quota to limit unconsumed message accumulation: pulsar-admin namespaces set-backlog-quota {tenant}/{namespace} --limit 5G --limitTime 86400 --policy producer_request_hold (other policies: producer_exception, consumer_backlog_eviction).
  4. Verify policies via: pulsar-admin namespaces get-retention {tenant}/{namespace} and pulsar-admin namespaces get-backlog-quotas {tenant}/{namespace}
  5. Apply message TTL at the namespace level to automatically expire unconsumed messages after a period: pulsar-admin namespaces set-message-ttl {tenant}/{namespace} --messageTTL 3600 (seconds).

Known gotchas

Related routes

Configure Apache Pulsar topic-level policies for retention, TTL, and backlog quota
pulsar.apache.org · 5 steps · unrated
isolate noisy pulsar tenants using namespace resource quotas and resourcegroups
pulsar.apache.org · 5 steps · unrated
Configure Pulsar topic compaction, retention, and TTL
data-engineering · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans