ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Pulsar's tiered storage offloads cold BookKeeper segments to S3/GCS/Azure Blob, cutting storage costs 60-80% for long-retention topics like audit logs. This guide walks through broker config, namespace policies, verification steps, and the trade-offs you'll face in production.
Architecture note on Pulsar Tiered Storage: requirements, smallest viable config, trust boundaries, operational metrics, failure modes, and design-change conditions. Includes concrete broker.conf, alerting rules, and verification checklist.
Learn how to enable Pulsar tiered storage offload, the minimal cluster design, trust boundaries, operational checks, and failure modes. This guide covers the exact configuration needed and when you should rethink the design.
Learn how Apache Pulsar’s tiered storage moves old ledger segments to S3/GCS/Azure Blob while keeping recent data hot, reducing storage costs without sacrificing ordering guarantees.
If your Pulsar cluster is running out of disk space, tiered storage can move old messages to S3 without changing consumer APIs. Learn the architecture, how to set it up, and the trade‑offs you’ll face.
How to offload older Pulsar messages to object storage using namespace‑level offload thresholds and deletion lag, with verification steps and rollback options.
Pulsar's tiered storage moves cold segments from BookKeeper to S3 or GCS automatically. Here's how offload triggers, how to configure and verify it, and the geo-replication and GC trade-offs to plan for.
Learn how to implement Apache Pulsar Tiered Storage to decouple data retention from compute costs while maintaining transparent data access via object stores.
Learn when and how to enable Apache Pulsar Tiered Storage to cut costs while keeping recent messages on low-latency tiers, with a step-by-step configuration example and validation steps.
pulsar