ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A concise architecture note on Pulsar geo‑replication: requirements, minimal primary‑standby design, trust boundaries, operational verification, failure modes, and triggers for redesign.
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.
Explains how Pulsar separates stateless brokers from stateful BookKeeper storage, outlines trust boundaries, operational checks, failure modes, and when the design might be altered.
Learn how to diagnose and fix stalled topic compaction in Apache Pulsar, including identifying I/O bottlenecks, misaligned retention policies, and ledger storage issues.
pulsar