[{"data":1,"prerenderedAt":2078},["ShallowReactive",2],{"active-banner":3,"navbar-featured-partner-blog":24,"navbar-pricing-featured":306,"blog-\u002Fblog\u002Fpulsar-isolation-part-iv-single-cluster-isolation":1086,"blog-authors-\u002Fblog\u002Fpulsar-isolation-part-iv-single-cluster-isolation":2043,"related-\u002Fblog\u002Fpulsar-isolation-part-iv-single-cluster-isolation":2059},{"id":4,"title":5,"date":6,"dismissible":7,"extension":8,"link":9,"link2":10,"linkText":11,"linkText2":12,"meta":13,"stem":21,"variant":22,"__hash__":23},"banners\u002Fbanners\u002Flakestream-ufk-launch.md","StreamNative Introduces Lakestream Architecture and Launches Native Kafka Service","2026-04-07",true,"md","\u002Fblog\u002Ffrom-streams-to-lakestreams","https:\u002F\u002Fconsole.streamnative.cloud\u002Fsignup?from=banner_lakestream-launch","Read Announcement","Sign Up Now",{"body":14},{"type":15,"value":16,"toc":17},"minimark",[],{"title":18,"searchDepth":19,"depth":19,"links":20},"",2,[],"banners\u002Flakestream-ufk-launch","default","zRueBGutATZB0ZnFFHwaEV7F0Di4tnZUHhgOiI4cu6k",{"id":25,"title":26,"authors":27,"body":29,"canonicalUrl":289,"category":290,"createdAt":289,"date":291,"description":292,"extension":8,"featured":7,"image":293,"isDraft":294,"link":289,"meta":295,"navigation":7,"order":296,"path":297,"readingTime":298,"relatedResources":289,"seo":299,"stem":300,"tags":301,"__hash__":305},"blogs\u002Fblog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025.md","StreamNative Recognized as a Contender in The Forrester Wave™: Streaming Data Platforms, Q4 2025",[28],"David Kjerrumgaard",{"type":15,"value":30,"toc":276},[31,39,47,51,67,73,78,81,87,102,109,115,118,124,127,134,140,143,146,157,163,169,172,175,178,184,191,194,197,204,207,210,224,229,233,237,241,245,249,251,268,270],[32,33,35],"h3",{"id":34},"receives-highest-possible-scores-in-both-the-messaging-and-resource-optimization-criteria",[36,37,38],"em",{},"Receives Highest Possible Scores in BOTH the Messaging and Resource Optimization Criteria",[40,41,43],"h2",{"id":42},"introduction",[44,45,46],"strong",{},"Introduction",[48,49,50],"p",{},"Real-time data has become the backbone of modern innovation. As artificial intelligence (AI) and digital services demand instantaneous insights, organizations are realizing that streaming data is no longer optional – it's essential for delivering timely, context-rich experiences. StreamNative's data streaming platform is built precisely for this reality, ensuring data is immediate, reliable, and ready to power critical applications.",[48,52,53,54,63,64],{},"Today, we're excited to announce that Forrester Research has named StreamNative as a Contender in its evaluation, ",[55,56,58],"a",{"href":57},"\u002Freports\u002Frecognized-in-the-forrester-wave-tm-streaming-data-platforms-q4-2025",[36,59,60],{},[44,61,62],{},"The Forrester Wave™: Streaming Data Platforms, Q4 2025",". This report evaluated 15 top streaming data platform providers, and we're proud to share that ",[44,65,66],{},"StreamNative received the highest scores possible—5 out of 5—in both the Messaging and Resource Optimization criteria.",[48,68,69,70],{},"***Forrester's Take: ***",[36,71,72],{},"\"StreamNative is a good fit for enterprises that want an Apache Pulsar implementation that is also compatible with Kafka APIs.\"",[48,74,75],{},[36,76,77],{},"— The Forrester Wave™: Streaming Data Platforms, Q4 2025",[48,79,80],{},"Being recognized in the Forrester Wave is a proud milestone, and for us, it highlights how far StreamNative has come in enabling enterprises to unlock the power of real-time data. In the sections below, we'll dive into what we believe sets StreamNative apart—from our modern architecture and cloud-native design to our open-source foundation and real-time use cases—and how we see these strengths aligning with Forrester's findings.",[40,82,84],{"id":83},"trusted-by-industry-leaders",[44,85,86],{},"Trusted by Industry Leaders",[48,88,89,90,93,94,97,98,101],{},"Companies across industries are already leveraging StreamNative to drive real-time outcomes. Global enterprises like ",[44,91,92],{},"Cisco"," rely on StreamNative to handle massive IoT telemetry, supporting 245 million+ connected devices. Martech leaders such as ",[44,95,96],{},"Iterable"," process billions of events per day with StreamNative for hyper-personalized customer engagement. And in financial services, ",[44,99,100],{},"FICO"," trusts StreamNative to power its real-time fraud detection and analytics pipelines with a secure, scalable streaming backbone.",[48,103,104,105,108],{},"The Forrester report notes that, “",[36,106,107],{},"Customers appreciate the lower infrastructure costs that result from StreamNative’s cost-efficient, Kafka-compatible architecture. Customers note excellent support responsiveness…","”",[40,110,112],{"id":111},"modern-cloud-native-architecture-built-for-scale",[44,113,114],{},"Modern, Cloud-Native Architecture Built for Scale",[48,116,117],{},"From day one, StreamNative was designed with a modern architecture to meet the demanding scale and flexibility requirements of real-time data. Unlike legacy streaming systems that often rely on tightly coupled storage and compute, StreamNative's platform takes a cloud-native approach: it decouples these layers to enable elastic scalability and efficient resource utilization across any environment. The core is powered by Apache Pulsar—a distributed messaging and streaming engine—enhanced with multi-protocol support (including native Apache Kafka API compatibility) to unify diverse data streams under one roof. This means organizations can consolidate siloed messaging systems and handle both high-volume event streams and traditional message queues on a single platform, without sacrificing performance or reliability.",[48,119,120,121,108],{},"Forrester's evaluation described that “",[36,122,123],{},"StreamNative aims to provide a high-performance, multi-protocol streaming data platform: It uses Apache Pulsar with Kafka API compatibility to deliver cost-efficient, real-time applications for enterprises. It appeals to organizations that want a flexible, low-cost streaming solution, due to its focus on scalability and resource optimization, while its investments in Pulsar’s open-source ecosystem and performance optimization make it the primary platform for enterprises wishing to implement Pulsar.",[48,125,126],{},"Our cloud-first, leaderless architecture (with no single broker bottlenecks) and tiered storage model were built to maximize throughput and cost-efficiency for real-time workloads. By separating compute from storage and leveraging distributed object storage, StreamNative can retain huge volumes of event data indefinitely while keeping compute costs in check—effectively providing a flexible, low-cost streaming solution.",[48,128,129,130,133],{},"This modern design not only delivers high performance, but also ensures fault tolerance and geo-distribution out of the box, so enterprises can trust their streaming data is always available and durable. As Forrester’s evaluation noted, StreamNative ",[36,131,132],{},"\"excels at messaging and resource optimization\" and “Its platform supports use cases like real-time analytics and event-driven architectures with robust scalability.","” Our architecture provides the strong foundation that today's real-time applications demand, from ultra-fast data ingestion to seamless scale-out across hybrid and multi-cloud environments.",[40,135,137],{"id":136},"open-source-foundation-and-pulsar-expertise",[44,138,139],{},"Open Source Foundation and Pulsar Expertise",[48,141,142],{},"StreamNative's DNA is rooted in open source innovation. Our founders are the original creators of Apache Pulsar, and we've built our platform with the same open principles: freedom, flexibility, and community-driven innovation. For developers and data teams, this means adopting StreamNative comes with no proprietary lock-in—instead, you get a platform built on open standards and a thriving ecosystem. We offer broad API compatibility (Pulsar, Kafka, JMS, MQTT, and more) so that teams can work with familiar interfaces and integrate StreamNative into existing systems with ease.",[48,144,145],{},"StreamNative is the primary commercial contributor to the Apache Pulsar project and its surrounding ecosystem. We invest heavily in Pulsar's ongoing improvements our investments in Pulsar's open-source ecosystem and performance optimization bolster StreamNative's value. We also foster a vibrant community through initiatives like the Data Streaming Summit and free training resources.",[48,147,148,149,152,153,156],{},"Forrester's assessment noted that StreamNative’s “",[36,150,151],{},"events-driven agents, extensibility, and performance architecture are solid,","” and we're continuing to build on that foundation. ",[44,154,155],{},"We're actively investing in expanding our tooling for observability, governance, schema management, and developer productivity","—areas we recognize as critical for enterprise adoption and where we're committed to accelerating our roadmap.",[48,158,159,160],{},"Being open also means embracing an open ecosystem of technologies. StreamNative actively integrates with the tools and platforms that matter most to our users. We partner with industry leaders like Snowflake, Databricks, Google, and Ververica to ensure our streaming platform works seamlessly with data warehouses, lakehouse storage, and stream processing frameworks. Forrester’s evaluation observed that StreamNative’s ",[36,161,162],{},"\"investments in Pulsar’s open-source ecosystem and performance optimization make it the primary platform for enterprises wishing to implement Pulsar.\"",[40,164,166],{"id":165},"powering-real-time-use-cases-across-industries",[44,167,168],{},"Powering Real-Time Use Cases Across Industries",[48,170,171],{},"One of the greatest validations of StreamNative's approach is the success our customers are achieving with real-time data. StreamNative's platform is versatile and use-case agnostic—if an application demands high-volume, low-latency data movement, we can power it. This flexibility is why our customer base spans industries from finance and IoT to major automobile manufacturers and online gaming. The common thread is that these organizations need to process and react to data in milliseconds, and StreamNative is delivering the capabilities to make that possible.",[48,173,174],{},"Cisco uses StreamNative to underpin an IoT telemetry system of colossal scale, connecting hundreds of millions of devices and thousands of enterprise clients with real-time data streams. The platform's multi-tenant design and proven reliability allow Cisco to offer its customers a live feed of device data with unwavering confidence. In the financial sector, FICO has built streaming pipelines on StreamNative to detect fraud as transactions happen and to monitor systems in real time. With StreamNative's strong guarantees around message durability and ordering, FICO can catch anomalies or suspicious patterns within seconds. And in digital customer engagement, Iterable relies on StreamNative to process billions of events every day—clicks, views, purchases—so that marketers can trigger personalized campaigns instantly based on user behavior.",[48,176,177],{},"Our customers uniformly deal with mission-critical data streams, where downtime or delays are unacceptable. StreamNative's fault-tolerant, scalable infrastructure has proven equal to the task, handling scenarios like bursting to millions of events per second or seamlessly spanning multiple cloud regions. Forrester's report recognized StreamNative for supporting event-driven architectures with robust scalability—which for us is a reflection of our platform's ability to meet the most demanding enterprise requirements.",[40,179,181],{"id":180},"continuing-to-innovate-ursa-orca-and-the-road-ahead",[44,182,183],{},"Continuing to Innovate: Ursa, Orca, and the Road Ahead",[48,185,186,187,190],{},"While we are thrilled to be recognized in Forrester's Streaming Data Platforms Wave, we view this as just the beginning. StreamNative's vision has always been bold: to ",[44,188,189],{},"provide a unified platform that not only handles today's streaming needs but also anticipates the emerging requirements of tomorrow",".",[48,192,193],{},"One key area of focus is the convergence of streaming data with advanced analytics and AI. As Forrester points out in the report, technology leaders should look for platforms that natively integrate messaging, stream processing, and analytics to provide AI agents with real-time, contextualized information. We couldn't agree more. Our award-winning Ursa Engine and Orca Agent Engine are aimed at extending our platform up the stack—bridging the gap between data streams and data lakes, and between event streams and intelligent processing.",[48,195,196],{},"Our new Ursa Engine introduces a lakehouse-native approach to streaming: it can write events directly to table formats like Iceberg on cloud storage, eliminating entire classes of ETL jobs and making fresh data instantly available for analytics queries. By integrating streaming and lakehouse technologies, we help customers collapse data silos and accelerate their AI\u002FML pipelines.",[48,198,199,200,203],{},"Beyond analytics integration, we are also enhancing StreamNative with more out-of-the-box processing and governance capabilities. In the coming months, we plan to introduce new features for lightweight stream processing and transformation, making it easier to build reactive applications directly on the platform. We're also expanding our ecosystem of connectors and integrations, so that whether your data lands in Snowflake, Databricks, or an AI model, StreamNative will seamlessly feed it. ",[44,201,202],{},"We're investing significantly in enterprise features including security, schema registry, governance, and monitoring tooling","—capabilities that are essential for mission-critical deployments and where we're committed to continued improvement.",[48,205,206],{},"This recognition from Forrester energizes us to keep innovating at full speed. We're sharing this honor with our amazing customers, community, and partners who drive us forward every day. Your feedback and real-world challenges have helped shape StreamNative into what it is today, and together, we will shape the future of streaming data. Thank you for joining us on this journey—we're just getting started, and we can't wait to deliver even more value as we continue to evolve our platform. Onward to real-time everything!",[208,209],"hr",{},[32,211,213],{"id":212},"streamnative-in-the-forrester-wave-evaluation-findings",[44,214,215,216,223],{},"StreamNative in ",[44,217,218],{},[55,219,220],{"href":57},[44,221,222],{},"The Forrester Wave™",": Evaluation Findings",[225,226,228],"h5",{"id":227},"recognized-as-a-contender-among-15-streaming-data-platform-providers","• Recognized as a Contender among 15 streaming data platform providers",[225,230,232],{"id":231},"received-the-highest-scores-possible-50-in-both-the-messaging-and-resource-optimization-criteria","* Received the highest scores possible (5.0) in both the Messaging and Resource Optimization criteria",[225,234,236],{"id":235},"cited-as-the-primary-platform-for-enterprises-wishing-to-implement-pulsar","• Cited as the primary platform for enterprises wishing to implement Pulsar",[225,238,240],{"id":239},"noted-for-excelling-at-messaging-and-resource-optimization","• Noted for excelling at messaging and resource optimization",[225,242,244],{"id":243},"customers-cited-lower-infrastructure-costs-and-excellent-support-responsiveness","• Customers cited lower infrastructure costs and excellent support responsiveness",[225,246,248],{"id":247},"recognized-for-supporting-event-driven-architectures-with-robust-scalability","• Recognized for supporting event-driven architectures with robust scalability",[208,250],{},[252,253,255,256,259,260,190],"h6",{"id":254},"forrester-disclaimer-forrester-does-not-endorse-any-company-product-brand-or-service-included-in-its-research-publications-and-does-not-advise-any-person-to-select-the-products-or-services-of-any-company-or-brand-based-on-the-ratings-included-in-such-publications-information-is-based-on-the-best-available-resources-opinions-reflect-judgment-at-the-time-and-are-subject-to-change-for-more-information-read-about-forresters-objectivity-here","**Forrester Disclaimer: **",[36,257,258],{},"Forrester does not endorse any company, product, brand, or service included in its research publications and does not advise any person to select the products or services of any company or brand based on the ratings included in such publications. Information is based on the best available resources. Opinions reflect judgment at the time and are subject to change",". *For more information, read about Forrester’s objectivity *",[55,261,265],{"href":262,"rel":263},"https:\u002F\u002Fwww.forrester.com\u002Fabout-us\u002Fobjectivity\u002F",[264],"nofollow",[36,266,267],{},"here",[208,269],{},[252,271,273],{"id":272},"apache-apache-pulsar-apache-kafka-apache-flink-and-other-names-are-trademarks-of-the-apache-software-foundation-no-endorsement-by-apache-or-other-third-parties-is-implied",[36,274,275],{},"Apache®, Apache Pulsar®, Apache Kafka®, Apache Flink® and other names are trademarks of The Apache Software Foundation. No endorsement by Apache or other third parties is implied.",{"title":18,"searchDepth":19,"depth":19,"links":277},[278,280,281,282,283,284,285],{"id":34,"depth":279,"text":38},3,{"id":42,"depth":19,"text":46},{"id":83,"depth":19,"text":86},{"id":111,"depth":19,"text":114},{"id":136,"depth":19,"text":139},{"id":165,"depth":19,"text":168},{"id":180,"depth":19,"text":183,"children":286},[287],{"id":212,"depth":279,"text":288},"StreamNative in The Forrester Wave™: Evaluation Findings",null,"Company","2025-12-16","StreamNative is recognized in The Forrester Wave™: Streaming Data Platforms, Q4 2025. Discover why Forrester highlights StreamNative's high-performance messaging, efficient resource use, and cost-effective Kafka API compatibility for real-time innovation.","\u002Fimgs\u002Fblogs\u002F693bd36cf01b217dcb67278f_Streamnative_blog_thumbnail.png",false,{},0,"\u002Fblog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025","10 mins read",{"title":26,"description":292},"blog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025",[302,303,304],"Announcements","Real-Time","Forrester","5Nr1vAcqlQ7yFQfdL0a3MLsNFerVmEOQJXD9Twz5lx8",{"id":307,"title":308,"authors":309,"body":314,"canonicalUrl":289,"category":1073,"createdAt":289,"date":1074,"description":1075,"extension":8,"featured":7,"image":1076,"isDraft":294,"link":289,"meta":1077,"navigation":7,"order":296,"path":1078,"readingTime":1079,"relatedResources":289,"seo":1080,"stem":1081,"tags":1082,"__hash__":1085},"blogs\u002Fblog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour.md","How We Run a 5 GB\u002Fs Kafka Workload for Just $50 per Hour",[310,311,312,313],"Matteo Meril","Neng Lu","Hang Chen","Penghui Li",{"type":15,"value":315,"toc":1043},[316,319,322,325,328,331,335,338,348,354,357,365,370,374,381,384,387,395,399,402,407,411,414,417,420,423,432,436,439,450,453,457,460,463,474,477,481,485,493,496,500,508,537,541,544,549,553,556,560,563,566,571,580,585,588,591,602,606,609,620,624,627,630,635,638,667,671,673,679,682,687,692,695,699,713,717,728,732,747,756,767,770,773,777,780,783,794,797,800,803,808,813,817,821,838,842,856,861,865,876,879,895,899,910,915,920,928,932,935,939,946,950,953,962,967,976,982,991,1000,1009,1018,1027,1035],[48,317,318],{},"The rise of DeepSeek has shaken the AI infrastructure market, forcing companies to confront the escalating costs of training and deploying AI models. But the real pressure point isn’t just compute—it’s data acquisition and ingestion costs.",[48,320,321],{},"As businesses rethink their AI cost-containment strategies, real-time data streaming is emerging as a critical enabler. The growing adoption of Kafka as a standard protocol has expanded cost-efficient options, allowing companies to optimize streaming analytics while keeping expenses in check.",[48,323,324],{},"Ursa, the data streaming engine powering StreamNative’s managed Kafka service, is built for this new reality. With its leaderless architecture and native lakehouse storage integration, Ursa eliminates costly inter-zone network traffic for data replication and client-to-broker communication while ensuring high availability at minimal operational cost.",[48,326,327],{},"In this blog post, we benchmarked the infrastructure cost and total cost of ownership (TCO) for running a 5GB\u002Fs Kafka workload across different Kafka vendors, including Redpanda, Confluent WarpStream, and AWS MSK. Our benchmark results show that Ursa can sustain 5GB\u002Fs Kafka workloads at just 5% of the cost of traditional streaming engines like Redpanda—making it the ideal solution for high-performance, cost-efficient ingestion and data streaming for data lakehouses and AI workloads.",[48,329,330],{},"Note: We also evaluated vanilla Kafka in our benchmark; however, for simplicity, we have focused our cost comparison on vendor solutions rather than self-managed deployments. That said, it is important to highlight that both Redpanda and vanilla Kafka use a leader-based data replication approach. In a data-intensive, network-bound workload like 5GB\u002Fs streaming, with the same machine type and replication factor, Redpanda and vanilla Kafka produced nearly identical cost profiles.",[40,332,334],{"id":333},"key-benchmark-findings","Key Benchmark Findings",[48,336,337],{},"Ursa delivered 5 GB\u002Fs of sustained throughput at an infrastructure cost of just $54 per hour. For comparison:",[339,340,341,345],"ul",{},[342,343,344],"li",{},"MSK: $303 per hour → 5.6x more expensive compared to Ursa",[342,346,347],{},"Redpanda: $988 per hour → 18x more expensive compared to Ursa",[48,349,350],{},[351,352],"img",{"alt":18,"src":353},"\u002Fimgs\u002Fblogs\u002F679c71b67d9046f26edc7977_AD_4nXfvTqyBNUBu2lObdkKAx-5UNkpNP8UYULLZyOcixE6z99VMZUUEsUqWjzexI7vjyNGRNSAUoM9smYvdTP55ctAhIbrs5lmQgcSVMWdaoigbWouCl95DVSQsxooY-qqfGcYqS4g4zA.png",[48,355,356],{},"Beyond infrastructure costs, when factoring in both storage pricing, vendor pricing and operational expenses, Ursa’s total cost of ownership (TCO) for a 5GB\u002Fs workload with a 7-day retention period is:",[339,358,359,362],{},[342,360,361],{},"50% cheaper than Confluent WarpStream",[342,363,364],{},"85% cheaper than MSK and Redpanda",[48,366,367],{},[351,368],{"alt":18,"src":369},"\u002Fimgs\u002Fblogs\u002F679c602d77e9c706de5343b8_AD_4nXeDv8rrv_C1CTCCiqYo1zpvlGYbdBk1r0VEqovAPu22iFMQZgh54Hfw9PBMLzM7jDFxKwAFDxbdG0np4XVk_tGsWhEKMloLRcmmea7lvueCx-0cFsyaE3Mya4Mxc1Dox95A6JEc.png",[40,371,373],{"id":372},"ursa-highly-cost-efficient-data-streaming-at-scale","Ursa: Highly Cost-Efficient Data Streaming at Scale",[48,375,376,380],{},[55,377,379],{"href":378},"\u002Fblog\u002Fursa-reimagine-apache-kafka-for-the-cost-conscious-data-streaming","Ursa"," is a next-generation data streaming engine designed to deliver high performance at a fraction of the cost of traditional disk-based solutions. It is fully compatible with Apache Kafka and Apache Pulsar APIs, while leveraging a leaderless, lakehouse-native architecture to maximize scalability, efficiency, and cost savings.",[48,382,383],{},"Ursa’s key innovation is separating storage from compute and decoupling metadata\u002Findex operations from data operations by utilizing cloud object storage (e.g., AWS S3) instead of costly inter-zone disk-based replication. It also employs open lakehouse formats (Iceberg and Delta Lake), enabling columnar compression to significantly reduce storage costs while maintaining durability and availability.",[48,385,386],{},"In contrast, traditional streaming systems—like Kafka and Redpanda—depend on leader-based architectures, which drive up inter-zone traffic costs due to replication and client communication. Ursa mitigates these costs by:",[339,388,389,392],{},[342,390,391],{},"Eliminating inter-zone traffic costs via a leaderless architecture.",[342,393,394],{},"Replacing costly inter-zone replication with direct writes to cloud storage using open lakehouse formats.",[40,396,398],{"id":397},"how-ursa-eliminates-inter-zone-traffic","How Ursa Eliminates Inter-Zone Traffic",[48,400,401],{},"Ursa minimizes inter-zone traffic by leveraging a leaderless architecture, which eliminates inter-zone communication between clients and brokers, and lakehouse-native storage, which removes the need for inter-zone data replication. This approach ensures high availability and scalability while avoiding unnecessary cross-zone data movement.",[48,403,404],{},[351,405],{"alt":18,"src":406},"\u002Fimgs\u002Fblogs\u002F679c602e21b3571bb7117dca_AD_4nXd7Oahc77NjRLNvA9clLt0tsyU6MrIqVibFYv5pW5giTIcCHPr3EA_yTGzfVEUIVO3VXK56qWK8zmBCp5lY0E_4nmlWIPFrHjtHylA5NhwELjn-UB0fLG2h_kbrxrc7Cs_edvveNA.png",[32,408,410],{"id":409},"leaderless-architecture","Leaderless architecture",[48,412,413],{},"Traditional streaming engines such as Kafka, Pulsar, or RedPanda rely on a leader-based model, where each partition is assigned to a single leader broker that handles all writes and reads.",[48,415,416],{},"Pros of Leader-Based Architectures:\n✔ Maintains message ordering via local sequence IDs\n✔ Delivers low latency and high performance through message caching",[48,418,419],{},"Cons of Leader-Based Architectures:\n✖ Throughput bottlenecked by a single broker per partition\n✖ Inter-zone traffic required for high availability in multi-AZ deployments",[48,421,422],{},"While Kafka and Pulsar offer partial solutions (e.g., reading from followers, shadow topics) to reduce read-related inter-zone traffic, producers still send data to a single leader.",[48,424,425,426,431],{},"Ursa removes the concept of topic ownership, allowing any broker in the cluster to handle reads or writes for any partition. The primary challenge—ensuring message ordering—is solved with ",[55,427,430],{"href":428,"rel":429},"https:\u002F\u002Fgithub.com\u002Fstreamnative\u002Foxia",[264],"Oxia",", a scalable metadata and index service created by StreamNative in 2022.",[32,433,435],{"id":434},"oxia-the-metadata-layer-enabling-leaderless-architecture","Oxia: The Metadata Layer Enabling Leaderless Architecture",[48,437,438],{},"Ensuring message ordering in a leaderless architecture is complex, but Ursa solves this with Oxia:",[339,440,441,444,447],{},[342,442,443],{},"Handles millions of metadata\u002Findex operations per second",[342,445,446],{},"Generates sequential IDs to maintain strict message ordering",[342,448,449],{},"Optimized for Kubernetes with horizontal scalability",[48,451,452],{},"Producers and consumers can connect to any broker within their local AZ, eliminating inter-zone traffic costs while maintaining performance through localized caching.",[32,454,456],{"id":455},"zero-interzone-data-replication","Zero interzone data replication",[48,458,459],{},"In most distributed systems, data replication from a leader (primary) to followers (replicas) is crucial for fault tolerance and availability. However, replication across zones can inflate infrastructure expenses substantially.",[48,461,462],{},"Ursa avoids these costs by writing data directly to cloud storage (e.g., AWS S3, Google GCS):",[339,464,465,468,471],{},[342,466,467],{},"Built-In Resilience: Cloud storage inherently offers high availability and fault tolerance without inter-zone traffic fees.",[342,469,470],{},"Tradeoff: Slightly higher latency (sub-second, with p99 at 500 milliseconds) compared to local disk\u002FEBS (single-digit to sub-100 milliseconds), in exchange for significantly lower costs (up to 10x lower).",[342,472,473],{},"Flexible Modes: Ursa is an addition to the classic BookKeeper-based engine, providing users with the flexibility to optimize for either cost or low latency based on their workload requirements.",[48,475,476],{},"By foregoing conventional replication, Ursa slashes inter-zone traffic costs and associated complexities—making it a compelling option for organizations seeking to balance high-performance data streaming with strict budget constraints.",[40,478,480],{"id":479},"how-we-ran-a-5-gbs-test-with-ursa","How We Ran a 5 GB\u002Fs Test with Ursa",[32,482,484],{"id":483},"ursa-cluster-deployment","Ursa Cluster Deployment",[339,486,487,490],{},[342,488,489],{},"9 brokers across 3 availability zones, each on m6i.8xlarge (Fixed 12.5 Gbps bandwidth, 32 vCPU cores, 128 GB memory).",[342,491,492],{},"Oxia cluster (metadata store) with 3 nodes of m6i.8xlarge, distributed across three availability zones (AZs).",[48,494,495],{},"During peak throughput (5 GB\u002Fs), each broker’s network usage was about 10 Gbps.",[32,497,499],{"id":498},"openmessaging-benchmark-workers-configuration","OpenMessaging Benchmark Workers & Configuration",[48,501,502,503,507],{},"The OpenMessaging Benchmark(OMB) Framework is a suite of tools that make it easy to benchmark distributed messaging systems in the cloud. Please check ",[55,504,505],{"href":505,"rel":506},"https:\u002F\u002Fopenmessaging.cloud\u002Fdocs\u002Fbenchmarks\u002F",[264]," for details.",[339,509,510,525,534],{},[342,511,512,513,518,519,524],{},"12 OMB workers: 6 for ",[55,514,517],{"href":515,"rel":516},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002Fd1094122270775e4f1580947f80c5055",[264],"producers",", 6 for ",[55,520,523],{"href":521,"rel":522},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002F06bada89381fb77a7862e1b4c1d8963d",[264],"consumers"," across 3 availability zones, on m6i.8xlarge instances. Each worker is configured with 12 CPU cores and 48 GB memory.",[342,526,527,528,533],{},"Sample YAML ",[55,529,532],{"href":530,"rel":531},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002F204c1f26c4d44a218ae235bf2de99904",[264],"scripts"," provided for Kafka-compatible configuration and rate limits.",[342,535,536],{},"Achieved consistent 5 GB\u002Fs publish\u002Fsubscribe throughput.",[40,538,540],{"id":539},"ursa-benchmark-tests-results","Ursa Benchmark Tests & Results",[48,542,543],{},"The following diagram demonstrates that Ursa can consistently handle 5 GB\u002Fs of traffic, fully saturating the network across all broker nodes.",[48,545,546],{},[351,547],{"alt":18,"src":548},"\u002Fimgs\u002Fblogs\u002F679c602d7b261bac1113f7d6_AD_4nXdDPsRc3koXICiFF0bqSmGWbJt_RlUy4FE3ruuWOfbCfpcqZ1dejjqGbkaCJv2hQFL1nirRouBVRW2l5uMWBvY9naMqGB_wHcLI14dBM0f85TXhmdm3UxEv1yGX9Y4hf5FttSkZew.png",[40,550,552],{"id":551},"comparing-infrastructure-cost","Comparing Infrastructure Cost",[48,554,555],{},"This benchmark first evaluates infrastructure costs of running a 5 GB\u002Fs streaming workload (1:1 producer-to-consumer ratio) across different data streaming engines, including Ursa, Redpanda, and AWS MSK, with a focus on multi-AZ deployments to ensure a fair comparison.",[32,557,559],{"id":558},"test-setup-key-assumptions","Test Setup & Key Assumptions",[48,561,562],{},"All tests use multi-AZ configurations, with clusters and clients distributed across three AWS availability zones (AZs). Cluster size scales proportionally to the number of AZs, and rack-awareness is enabled for all engines to evenly distribute topic partitions and leaders.",[48,564,565],{},"To ensure a fair comparison, we selected the same machine type capable of fully utilizing both network and storage bandwidth for Ursa and Redpanda in this 5GB\u002Fs test:",[339,567,568],{},[342,569,570],{},"9 × m6i.8xlarge instances",[48,572,573,574,579],{},"However, MSK's storage bandwidth limits vary depending on the selected instance type, with the highest allowed limit capped at 1000 MiB\u002Fs per broker, according to",[55,575,578],{"href":576,"rel":577},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fmsk\u002Flatest\u002Fdeveloperguide\u002Fmsk-provision-throughput-management.html#throughput-bottlenecks",[264]," AWS documentation",". Given this constraint, achieving 5 GB\u002Fs throughput with a replication factor of 3 required the following setup:",[339,581,582],{},[342,583,584],{},"15 × kafka.m7g.8xlarge (32 vCPUs, 128 GB memory, 15 Gbps network, 4000 GiB EBS).",[48,586,587],{},"This configuration was necessary to work around MSK's storage bandwidth limitations, ensuring a comparable cost basis to other evaluated streaming engines.",[48,589,590],{},"Additional key assumptions include:",[339,592,593,596,599],{},[342,594,595],{},"Inter-AZ producer traffic: For leader-based engines, two-thirds of producer-to-broker traffic crosses AZs due to leader distribution.",[342,597,598],{},"Consumer optimizations: Follower fetch is enabled across all tests, eliminating inter-AZ consumer traffic.",[342,600,601],{},"Storage cost exclusions: This benchmark only evaluates streaming costs, assuming no long-term data retention.",[32,603,605],{"id":604},"inter-broker-replication-costs","Inter-Broker Replication Costs",[48,607,608],{},"Inter-broker (cross-AZ) replication is a major cost driver for data streaming engines:",[339,610,611,614,617],{},[342,612,613],{},"RedPanda: Inter-broker replication is not free, leading to substantial costs when data must be copied across multiple availability zones.",[342,615,616],{},"AWS MSK: Inter-broker replication is free, but MSK instance pricing is significantly higher (e.g., $3.264 per hour for kafka.m7g.8xlarge vs $1.306 per hour for an on-demand m7g.8xlarge). The storage price of MSK is $0.10 per GB-month which is significantly higher than st1, which costs $0.045 per GB-month. Even though replication is free, client-to-broker traffic still incurs inter-AZ charges.",[342,618,619],{},"Ursa: No inter-broker replication costs due to its leaderless architecture, eliminating inter-zone replication costs entirely.",[32,621,623],{"id":622},"zone-affinity-reducing-inter-az-costs","Zone Affinity: Reducing Inter-AZ Costs",[48,625,626],{},"We evaluated zone affinity mechanisms to further reduce inter-AZ data transfer costs.",[48,628,629],{},"Consumers:",[339,631,632],{},[342,633,634],{},"Follower fetch is enabled across all tests, ensuring consumers fetch data from replicas in their local AZ—eliminating inter-zone consumer traffic except for metadata lookups",[48,636,637],{},"Producers:",[339,639,640,649,658],{},[342,641,642,643,648],{},"Kafka protocol lacks an easy way to enforce producer AZ affinity (though ",[55,644,647],{"href":645,"rel":646},"https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FKAFKA\u002FKIP-1123:+Rack-aware+partitioning+for+Kafka+Producer",[264],"KIP-1123"," aims to address this). And it only works with the default partitioner (i.e., when no record partition or record key is specified).",[342,650,651,652,657],{},"Redpanda recently introduced ",[55,653,656],{"href":654,"rel":655},"https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-cloud\u002Fdevelop\u002Fproduce-data\u002Fleader-pinning\u002F",[264],"leader pinning",", but this only benefits setups where producers are confined to a single AZ—not applicable to our multi-AZ benchmark.",[342,659,660,661,666],{},"Ursa is the only system in this test with ",[55,662,665],{"href":663,"rel":664},"https:\u002F\u002Fdocs.streamnative.io\u002Fdocs\u002Fconfig-kafka-client#eliminate-cross-az-networking-traffic",[264],"built-in zone affinity for both producers and consumers",". It achieves this by embedding producer AZ information in client.id, allowing metadata lookups to route clients to local-AZ brokers, eliminating inter-AZ producer traffic.",[32,668,670],{"id":669},"cost-comparison-results","Cost Comparison Results",[48,672,337],{},[339,674,675,677],{},[342,676,344],{},[342,678,347],{},[48,680,681],{},"Ursa’s leaderless architecture, zone affinity, and native cloud storage integration deliver unparalleled cost efficiency, making it the most cost-effective choice for high-throughput data streaming workloads.",[48,683,684],{},[351,685],{"alt":18,"src":686},"\u002Fimgs\u002Fblogs\u002F679c72208198ca36a352f228_AD_4nXeeZuM8T-xBlD4Vf3j67K618n08qh8wIDLLtiLJG0ssA1Wj1V26u7wIDTX9sqLrtw8mB2c299dwzarGen62CG0Vh7nWstn5qbPGFcBaKJYEepTsLr5fHWv1U8uqbg8Y0UOK6fJ7.png",[48,688,689],{},[351,690],{"alt":18,"src":691},"\u002Fimgs\u002Fblogs\u002F679c625978031f40229de484_AD_4nXdLkLLJ30KKr-_A_rN1j8akVwBYacAWIPzWHoOReJF421890kfByZoQQxkLczihVSmiw5Q9J51-V9I2SEKITbwsYnANDDTlAVL5nQ_jfaHNTe9VEWhSoa7DZooCnilDYL6l6msmJg.png",[48,693,694],{},"The detailed infrastructure cost calculations for each data streaming engine are listed below:",[32,696,698],{"id":697},"streamnative-ursa","StreamNative - Ursa",[339,700,701,704,707,710],{},[342,702,703],{},"Server EC2 costs: 9 * $1.536\u002Fhr = $14",[342,705,706],{},"Client EC2 costs: 9 * $1.536\u002Fhr =$14",[342,708,709],{},"S3 write requests costs: 1350 r\u002Fs * $0.005\u002F1000r * 3600s = $24",[342,711,712],{},"S3 read requests costs: 1350 r\u002Fs * $0.0004\u002F1000r * 3600s = $2",[32,714,716],{"id":715},"aws-msk","AWS MSK",[339,718,719,722,725],{},[342,720,721],{},"Server EC2 costs: 15 * $3.264\u002Fhr = $49",[342,723,724],{},"Client side EC2 costs: 9 * $1.536\u002Fhr =$14",[342,726,727],{},"Interzone traffic - producer to broker: 5GB\u002Fs * ⅔ * $0.02\u002FG(in+out) * 3600 = $240",[32,729,731],{"id":730},"redpanda","RedPanda",[339,733,734,736,738,741,744],{},[342,735,703],{},[342,737,706],{},[342,739,740],{},"Interzone traffic - producer to broker: 5GB\u002Fs * ⅔ * $0.02\u002FGB(in+out) * 3600 = $240",[342,742,743],{},"Interzone traffic - replication: 10GB\u002Fs * $0.02\u002FGB(in+out) * 3600 = $720",[342,745,746],{},"Interzone traffic - broker to consumer: $0 (fetch from local zone)",[48,748,749,750,755],{},"Please note that we were unable to test ",[55,751,754],{"href":752,"rel":753},"https:\u002F\u002Fwww.redpanda.com\u002Fblog\u002Fcloud-topics-streaming-data-object-storage",[264],"Redpanda with Cloud Topics",", as it remains an announced but unreleased feature and is not yet available for evaluation. Based on the limited information available, while Cloud Topics may help optimize inter-zone data replication costs, producers still need to traverse inter-availability zones to connect to the topic partition owners and incur inter-zone traffic costs of up to $240 per hour.",[339,757,758,764],{},[342,759,760,763],{},[55,761,647],{"href":645,"rel":762},[264]," (when implemented) will help mitigate producer-to-broker inter-zone traffic, but it is not yet available. And it only works with the default partitioner (no record partition or key is specified).",[342,765,766],{},"Redpanda’s leader pinning helps only when all producers for the pinned topic are confined to a single AZ. In multi-AZ environments (like our benchmark), inter-zone producer traffic remains unavoidable.",[48,768,769],{},"Additionally, Redpanda’s Cloud Topics architecture is not documented publicly. Their blog mentions \"leader placement rules to optimize produce latency and ingress cost,\" but it is unclear whether this represents a shift away from a leader-based architecture or if it uses techniques similar to Ursa’s zone-aware approach.",[48,771,772],{},"We may revisit this comparison as more details become available.",[40,774,776],{"id":775},"comparing-total-cost-of-ownership","Comparing Total Cost of Ownership",[48,778,779],{},"As highlighted earlier, with a BYOC Ursa setup, you can achieve 5 GB\u002Fs throughput at just 5% of the infrastructure cost of a traditional leader-based data streaming engine, such as Kafka or RedPanda, while managing the infrastructure yourself. This significant cost reduction is enabled by Ursa’s leaderless architecture and lakehouse-native storage design, which eliminate overhead costs such as inter-zone traffic and leader-based data replication. By leveraging a lakehouse-native, leaderless architecture, Ursa reduces resource requirements, enabling you to handle high data throughput efficiently and at a fraction of the cost of RedPanda.",[48,781,782],{},"Now, let’s examine the total cost comparison, evaluating Ursa alongside other vendors, including those that have adopted a leaderless architecture (e.g., Confluent WarpStream). This comparison is based on a 5GB\u002Fs workload with a 7-day retention period, factoring in both storage cost and vendor costs Here are the key findings:",[339,784,785,788,791],{},[342,786,787],{},"Ursa ($164,353\u002Fmonth) is: 50% cheaper than Confluent WarpStream ($337,068\u002Fmonth)",[342,789,790],{},"85% cheaper than AWS MSK ($1,115,251\u002Fmonth)",[342,792,793],{},"86% cheaper than Redpanda ($1,202,853\u002Fmonth)",[48,795,796],{},"In addition to Ursa’s architectural advantages—eliminating most inter-AZ traffic and leveraging lakehouse storage for cost-effective data retention—it also adopts a more fair and cost-efficient pricing model: Elastic Throughput-based pricing. This approach aligns costs with actual usage, avoiding unnecessary overhead.",[48,798,799],{},"Unlike WarpStream, which charges for both storage and throughput, Ursa ensures that customers only pay for the throughput they actively use. Ursa’s pricing is based on compressed data sent by clients, meaning the more data compressed on the client side, the lower the cost. In contrast, WarpStream prices are based on uncompressed data, unfairly inflating expenses and failing to incentivize customers to optimize their client applications.",[48,801,802],{},"This distinction is crucial, as compressed data reduces both storage and network costs, making Ursa’s pricing model not only more cost-effective but also more transparent and predictable.",[48,804,805],{},[351,806],{"alt":18,"src":807},"\u002Fimgs\u002Fblogs\u002F679c602d194800c9206d9d58_AD_4nXcFlf755xgyz7htxhMhBV5fGrsxy642mQNodt61DTok_z1dwkw5A6lkO5hatXVneCaB0anbZPAyvLI3MlIMuQEYLEACHHvQMOr5UfaB37dfzkdqewDEvcT-20VGd_zzvJsuA00zGA.png",[48,809,810],{},[351,811],{"alt":18,"src":812},"\u002Fimgs\u002Fblogs\u002F679c62594e9c2e629fae73aa_AD_4nXeU6cOgItnjLsEZCOf13TEvMY_SHWWIxYP2OYUj-B1GUPyWO78OG08K_v03hwYSVcg06f9dqDiGmdwy76vynjmiDGL5bluZ5_XF4nSU_r59oOZdfViXndXt6s11vVOY7qwfZN8v.png",[32,814,816],{"id":815},"cost-breakdown","Cost Breakdown",[818,819,820],"h4",{"id":697},"StreamNative – Ursa",[339,822,823,826,829,832,835],{},[342,824,825],{},"EC2 (Server): 9 × $1.536\u002Fhr × 24 hr × 30 days = $9,953.28",[342,827,828],{},"S3 Write Requests: 1,350 r\u002Fs × $0.005\u002F1,000 r × 3,600 s × 24 hr × 30 days = $17,496",[342,830,831],{},"S3 Read Requests: 1,350 r\u002Fs × $0.0004\u002F1,000 r × 3,600 s × 24 hr × 30 days = $1,400",[342,833,834],{},"S3 Storage Costs: 5 GB\u002Fs × $0.021\u002FGB × 3,600 s × 24 hr × 7 days = $63,504",[342,836,837],{},"Vendor Cost: 200 ETU × $0.50\u002Fhr × 24 hr × 30 days = $72,000",[818,839,841],{"id":840},"warpstream","WarpStream",[339,843,844,847],{},[342,845,846],{},"Based on WarpStream’s pricing calculator (as of January 29, 2025), we assume a 4:1 client data compression ratio, meaning 20 GB\u002Fs of uncompressed data translates to 5 GB\u002Fs of compressed data.",[342,848,849,850,855],{},"It's important to note that WarpStream’s pricing structure has fluctuated frequently throughout January. We observed the cost reported by their calculator changing from $409,644 per month to $337,068 per month. This variability has been previously highlighted in the blog post “",[55,851,854],{"href":852,"rel":853},"https:\u002F\u002Fbigdata.2minutestreaming.com\u002Fp\u002Fthe-brutal-truth-about-apache-kafka-cost-calculators",[264],"The Brutal Truth About Kafka Cost Calculators","”. To ensure transparency, we have documented the pricing as of January 29, 2025.",[48,857,858],{},[351,859],{"alt":18,"src":860},"\u002Fimgs\u002Fblogs\u002F679c602e42713e0028e9af5e_AD_4nXcu5_VWTLu9jRYs6zX1MBAOtLQEo5gyfNSWPcbpnQHXTa8qNCFAXezRR2E8daygzYTTwd4dhJjaLaLM8C6y_3OGbu2NS7pdvEv3a8-ptNKOg7AeKnYqPQCAYvQ5EuxzuI3JYIvY.png",[818,862,864],{"id":863},"msk","MSK",[339,866,867,870,873],{},[342,868,869],{},"EC2 (Server): 15 * $3.264\u002Fhr × 24 hr × 30 days = $35,251",[342,871,872],{},"Interzone Traffic (Client-Server): 5 GB\u002Fs × ⅔ × $0.02\u002FGB (in+out) × 3,600 s × 24 hr × 30 days = $172,800",[342,874,875],{},"Storage: 5 GB\u002Fs × $0.1\u002FGB-month × 3,600 s × 24 hr × 7 days * 3 replicas = $907,200",[818,877,731],{"id":878},"redpanda-1",[339,880,881,884,886,889,892],{},[342,882,883],{},"EC2 (Server): 9 × $1.536\u002Fhr × 24 hr × 30 days = $9953",[342,885,872],{},[342,887,888],{},"Interzone Traffic (Replication): 5 GB\u002Fs × 2 × $0.02\u002FGB (in+out) × 3,600 s × 24 hr × 30 days = $518,400",[342,890,891],{},"Storage: 5 GB\u002Fs × $0.045\u002FGB-month(st1) × 3,600 s × 24 hr × 7 days * 3 replicas = $408,240",[342,893,894],{},"Vendor Cost: $93,333 per month (based on limited information. See additional notes below).",[818,896,898],{"id":897},"additional-notes","Additional Notes",[339,900,901],{},[342,902,903,904,909],{},"Redpanda does not publicly disclose its BYOC pricing, making it difficult to accurately assess its total costs. We refer to information from the whitepaper “",[55,905,908],{"href":906,"rel":907},"https:\u002F\u002Fwww.redpanda.com\u002Fresources\u002Fredpanda-vs-confluent-performance-tco-benchmark-report#form",[264],"Redpanda vs. Confluent: A Performance and TCO Benchmark Report by McKnight Consulting Group.","” for estimation purposes. Based on the Tier-8 pricing model in the whitepaper,  the estimated cost to support a 5GB\u002Fs workload would be $1.12 million per year ($93,333 per month). However, since this calculation is based on an estimation, we will revisit and refine the cost assessment once Redpanda publishes its BYOC pricing.",[48,911,912],{},[351,913],{"alt":18,"src":914},"\u002Fimgs\u002Fblogs\u002F679c602dc8a9859eed89a0ef_AD_4nXdbcO8vsNNPy4GtkNLlmNKf22fjxRvzLzH7CtOna1L08sTbvnZx3HhufeFqc1w4K2gEF7lxO2IR5supotxebAiGnA07Qa8Yr3Rd1pVK2LYKK4WurlJGwgdwwucZIFoF-N_2oBjY.png",[48,916,917],{},[351,918],{"alt":18,"src":919},"\u002Fimgs\u002Fblogs\u002F679c602d6bc1c2287e012540_AD_4nXfcHZnLfjbjIr3ZAgoQXT9dwP3aQCOQPmGZZJUtpNZSwE6qY6M3yehIaBxCwxEIeu5PVdUPY0zhyjnow26YfgjdYgSG4GnV9ibxu0YWTIpwng6z_F6FUGJMpERMKtpsFESzXSN_Sw.png",[339,921,922,925],{},[342,923,924],{},"When estimating the storage costs for Kafka and Redpanda, we assume the use of HDD storage at $0.045\u002FGB, based on the premise that both systems can fully utilize disk bandwidth without incurring the higher costs associated with GP2 or GP3 volumes. However, in practice, many users opt for GP2 or GP3, significantly increasing the total storage cost for Kafka and Redpanda.",[342,926,927],{},"Unlike disk-based solutions, S3 storage does not require capacity preallocation—Ursa only incurs costs for the actual data stored. This contrasts with Kafka and Redpanda, where preallocating storage can drive up expenses. As a result, the real-world storage costs for Kafka and Redpanda are often 50% higher than the estimates above.",[40,929,931],{"id":930},"conclusion","Conclusion",[48,933,934],{},"Ursa represents a transformative shift in streaming data infrastructure, offering cost efficiency, scalability, and flexibility without compromising durability or reliability. By leveraging a leaderless architecture and eliminating inter-zone data replication, Ursa reduces total cost of ownership by over 90% compared to traditional leader-based streaming engines like Kafka and Redpanda. Its direct integration with cloud storage and scalable metadata & index management via Oxia ensure high availability and simplified infrastructure management.",[32,936,938],{"id":937},"balancing-latency-and-cost","Balancing Latency and Cost",[48,940,941,945],{},[55,942,944],{"href":943},"\u002Fblog\u002Fcap-theorem-for-data-streaming","Ursa trades off slightly higher latency for ultra low cost",", making it an ideal choice for the majority of streaming workloads, especially those that prioritize throughput and cost savings over ultra-low latency. Meanwhile, StreamNative’s BookKeeper-based engine remains the preferred solution for real-time, latency-sensitive applications. By combining these two approaches, StreamNative empowers customers with the flexibility to choose the right engine for their specific needs—whether it's maximizing cost savings or achieving ultra low-latency real-time performance.",[32,947,949],{"id":948},"the-future-of-streaming-infrastructure","The Future of Streaming Infrastructure",[48,951,952],{},"In an era where data fuels AI, analytics, and real-time decision-making, managing infrastructure costs is critical to sustaining innovation. Ursa is not just a cost-cutting alternative—it is a forward-thinking, lakehouse-native platform that redefines how modern data streaming infrastructure should be built and operated.",[48,954,955,956,961],{},"Whether your priority is reducing costs, improving flexibility, or ingesting massive data into lakehouses, Ursa delivers a future-proof solution for the evolving demands of real-time data streaming. ",[55,957,960],{"href":958,"rel":959},"https:\u002F\u002Fconsole.streamnative.cloud\u002F",[264],"Get started"," with StreamNative Ursa today!",[963,964,966],"h1",{"id":965},"references","References",[48,968,969,972,973],{},[970,971,430],"span",{}," ",[55,974,975],{"href":975},"\u002Fblog\u002Fintroducing-oxia-scalable-metadata-and-coordination",[48,977,978,972,980],{},[970,979,379],{},[55,981,378],{"href":378},[48,983,984,972,987],{},[970,985,986],{},"StreamNative pricing",[55,988,989],{"href":989,"rel":990},"https:\u002F\u002Fdocs.streamnative.io\u002Fdocs\u002Fbilling-overview",[264],[48,992,993,972,996],{},[970,994,995],{},"WarpStream pricing",[55,997,998],{"href":998,"rel":999},"https:\u002F\u002Fwww.warpstream.com\u002Fpricing#pricingfaqs",[264],[48,1001,1002,972,1005],{},[970,1003,1004],{},"AWS S3 pricing",[55,1006,1007],{"href":1007,"rel":1008},"https:\u002F\u002Faws.amazon.com\u002Fs3\u002Fpricing\u002F",[264],[48,1010,1011,972,1014],{},[970,1012,1013],{},"AWS EBS pricing",[55,1015,1016],{"href":1016,"rel":1017},"https:\u002F\u002Faws.amazon.com\u002Febs\u002Fpricing\u002F",[264],[48,1019,1020,972,1023],{},[970,1021,1022],{},"AWS MSK pricing",[55,1024,1025],{"href":1025,"rel":1026},"https:\u002F\u002Faws.amazon.com\u002Fmsk\u002Fpricing\u002F",[264],[48,1028,1029,972,1032],{},[970,1030,1031],{},"The Brutal Truth about Kafka Cost Calculators",[55,1033,852],{"href":852,"rel":1034},[264],[48,1036,1037,972,1040],{},[970,1038,1039],{},"Redpanda vs. Confluent: A Performance and TCO Benchmark Report by McKnight Consulting Group",[55,1041,906],{"href":906,"rel":1042},[264],{"title":18,"searchDepth":19,"depth":19,"links":1044},[1045,1046,1047,1052,1056,1057,1066,1069],{"id":333,"depth":19,"text":334},{"id":372,"depth":19,"text":373},{"id":397,"depth":19,"text":398,"children":1048},[1049,1050,1051],{"id":409,"depth":279,"text":410},{"id":434,"depth":279,"text":435},{"id":455,"depth":279,"text":456},{"id":479,"depth":19,"text":480,"children":1053},[1054,1055],{"id":483,"depth":279,"text":484},{"id":498,"depth":279,"text":499},{"id":539,"depth":19,"text":540},{"id":551,"depth":19,"text":552,"children":1058},[1059,1060,1061,1062,1063,1064,1065],{"id":558,"depth":279,"text":559},{"id":604,"depth":279,"text":605},{"id":622,"depth":279,"text":623},{"id":669,"depth":279,"text":670},{"id":697,"depth":279,"text":698},{"id":715,"depth":279,"text":716},{"id":730,"depth":279,"text":731},{"id":775,"depth":19,"text":776,"children":1067},[1068],{"id":815,"depth":279,"text":816},{"id":930,"depth":19,"text":931,"children":1070},[1071,1072],{"id":937,"depth":279,"text":938},{"id":948,"depth":279,"text":949},"StreamNative Cloud","2025-01-31","Discover how Ursa achieves 5GB\u002Fs Kafka workloads at just 5% of the cost of traditional streaming engines like Redpanda and AWS MSK. See our benchmark results comparing infrastructure costs, total cost of ownership (TCO), and performance across leading Kafka vendors.","\u002Fimgs\u002Fblogs\u002F679c6593d25099b1cdcec4ca_image-31.png",{},"\u002Fblog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour","30 min",{"title":308,"description":1075},"blog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour",[1083,1084,303],"TCO","Apache Kafka","CDUawvFKTs_AD8usvmIcTleU3mbfA0QAoPZM6xfVuo8",{"id":1087,"title":1088,"authors":1089,"body":1091,"canonicalUrl":289,"category":2032,"createdAt":289,"date":2033,"description":2034,"extension":8,"featured":294,"image":289,"isDraft":294,"link":289,"meta":2035,"navigation":7,"order":296,"path":2036,"readingTime":2037,"relatedResources":289,"seo":2038,"stem":2039,"tags":2040,"__hash__":2042},"blogs\u002Fblog\u002Fpulsar-isolation-part-iv-single-cluster-isolation.md","Pulsar Isolation Part IV: Single Cluster Isolation",[1090],"Ran Gao",{"type":15,"value":1092,"toc":2018},[1093,1095,1098,1130,1133,1137,1145,1151,1157,1167,1172,1178,1183,1189,1192,1196,1201,1207,1215,1221,1226,1232,1237,1243,1248,1254,1259,1265,1271,1276,1282,1287,1290,1296,1302,1307,1313,1317,1320,1326,1331,1337,1341,1344,1349,1354,1357,1362,1367,1372,1378,1383,1389,1394,1400,1404,1407,1413,1417,1421,1426,1429,1435,1437,1443,1449,1454,1460,1465,1471,1475,1481,1486,1491,1495,1498,1504,1508,1513,1518,1522,1527,1532,1538,1542,1548,1552,1557,1561,1566,1572,1577,1580,1586,1591,1597,1602,1608,1613,1619,1624,1630,1635,1641,1649,1655,1660,1666,1670,1675,1680,1686,1693,1699,1702,1708,1712,1717,1722,1727,1733,1737,1743,1747,1752,1757,1762,1767,1773,1780,1786,1790,1793,1798,1804,1809,1815,1820,1826,1832,1837,1843,1847,1853,1857,1862,1867,1872,1877,1883,1886,1892,1895,1900,1905,1910,1916,1921,1927,1932,1938,1943,1949,1954,1960,1965,1971,1975],[40,1094,46],{"id":42},[48,1096,1097],{},"This is the fourth blog in our four-part blog series on how to achieve resource isolation in Apache Pulsar. Before we dive in, let’s review what was covered in Parts I, II, and III.",[339,1099,1100,1107,1110,1113,1116,1123],{},[342,1101,1102,1106],{},[55,1103,1105],{"href":1104},"\u002Fen\u002Fblog\u002Ftech\u002F2021-03-02-taking-an-in-depth-look-at-how-to-achieve-isolation-in-pulsar\u002F","Pulsar Isolation Part I: Taking an In-Depth Look at How to Achieve Isolation in Pulsar"," This blog provides an introduction to three approaches to implement isolation in Pulsar. These include:",[342,1108,1109],{},"leveraging separate Pulsar clusters that use separate BookKeeper clusters,",[342,1111,1112],{},"leveraging separate Pulsar clusters that share one BookKeeper cluster, and",[342,1114,1115],{},"using a single Pulsar cluster with a single BookKeeper cluster. Each of these approaches and their specific use cases are discussed at length in the subsequent blogs.",[342,1117,1118,1122],{},[55,1119,1121],{"href":1120},"\u002Fblog\u002Ftech\u002F2021-06-03-pulsar-isolation-for-dummies-separate-pulsar-clusters\u002F","Pulsar Isolation Part II: Separate Pulsar Clusters"," shows you how to achieve isolation between separate Pulsar clusters that use separate BookKeeper clusters. This shared-nothing approach offers the highest level of isolation and is suitable for storing highly sensitive data, such as personally identifiable information or financial records.",[342,1124,1125,1129],{},[55,1126,1128],{"href":1127},"\u002Fblog\u002Fengineering\u002F2022-01-12-pulsar-isolation-part-3-separate-pulsar-clusters-sharing-a-single-bookkeeper-cluster\u002F","Pulsar Isolation Part III: Separate Pulsar Clusters Sharing a Single BookKeeper Cluster"," demonstrates how to achieve Pulsar isolation using separate Pulsar clusters that share one BookKeeper cluster. This approach uses separate Pulsar broker clusters in order to isolate the end-users from one another and allows you to use different authentication methods based on the use case. As a result, you gain the benefits of using a shared storage layer, such as a reduced hardware footprint and the associated hardware and maintenance costs.",[48,1131,1132],{},"In this fourth and final blog of the series, we provide a step-by-step tutorial on how to use a single cluster to achieve broker and bookie isolation. This more traditional approach takes advantage of Pulsar’s built-in multi-tenancy and removes the need to manage multiple broker and bookie clusters.",[40,1134,1136],{"id":1135},"preparation","Preparation",[48,1138,1139,1140,190],{},"In this tutorial we use the docker-compose to establish a Pulsar cluster. First, we need to ",[55,1141,1144],{"href":1142,"rel":1143},"https:\u002F\u002Fdocs.docker.com\u002Fget-docker\u002F",[264],"install the docker environment",[1146,1147,1148],"blockquote",{},[48,1149,1150],{},"This tutorial is based on docker 20.10.10, docker-compose 1.29.2, and MacOS 12.3.1.",[1152,1153,1154],"ol",{},[342,1155,1156],{},"Get the docker-compose configuration files.",[1158,1159,1164],"pre",{"className":1160,"code":1162,"language":1163},[1161],"language-text","\ngit clone https:\u002F\u002Fgithub.com\u002Fgaoran10\u002Fpulsar-docker-compose\ncd pulsar-docker-compose\n\n","text",[1165,1166,1162],"code",{"__ignoreMap":18},[1152,1168,1169],{},[342,1170,1171],{},"Start the cluster.",[1158,1173,1176],{"className":1174,"code":1175,"language":1163},[1161],"\ndocker-compose up\n\n",[1165,1177,1175],{"__ignoreMap":18},[1152,1179,1180],{},[342,1181,1182],{},"Check the pods.",[1158,1184,1187],{"className":1185,"code":1186,"language":1163},[1161],"\ndocker-compose ps\n   Name                  Command                State                         Ports\n--------------------------------------------------------------------------------------------------------\nbk1           bash -c export dbStorage_w ...   Up\nbk2           bash -c export dbStorage_w ...   Up\nbk3           bash -c export dbStorage_w ...   Up\nbk4           bash -c export dbStorage_w ...   Up\nbroker1       bash -c bin\u002Fapply-config-f ...   Up\nbroker2       bash -c bin\u002Fapply-config-f ...   Up\nbroker3       bash -c bin\u002Fapply-config-f ...   Up\nproxy1        bash -c bin\u002Fapply-config-f ...   Up         0.0.0.0:6650->6650\u002Ftcp, 0.0.0.0:8080->8080\u002Ftcp\npulsar-init   bin\u002Finit-cluster.sh              Exit 0\nzk1           bash -c bin\u002Fapply-config-f ...   Up\n\n",[1165,1188,1186],{"__ignoreMap":18},[48,1190,1191],{},"After the cluster initiation completes, we can begin setting the broker isolation policy.",[40,1193,1195],{"id":1194},"broker-isolation","Broker Isolation",[1152,1197,1198],{},[342,1199,1200],{},"Download a Pulsar release package to execute the pulsar-admin command.",[1158,1202,1205],{"className":1203,"code":1204,"language":1163},[1161],"\nwget https:\u002F\u002Farchive.apache.org\u002Fdist\u002Fpulsar\u002Fpulsar-2.10.0\u002Fapache-pulsar-2.10.0-bin.tar.gz\ntar -txvf apache-pulsar-2.10.0-bin.tar.gz\n\u002F\u002F we can execute pulsar-admin command in this directory\ncd apache-pulsar-2.10.0\n\n",[1165,1206,1204],{"__ignoreMap":18},[1152,1208,1209,1212],{},[342,1210,1211],{},"Get the broker list.",[342,1213,1214],{},"Create a namespace.",[1158,1216,1219],{"className":1217,"code":1218,"language":1163},[1161],"\nbin\u002Fpulsar-admin namespaces create public\u002Fns-isolation\nbin\u002Fpulsar-admin namespaces set-retention -s 1G -t 3d public\u002Fns-isolation\n\n",[1165,1220,1218],{"__ignoreMap":18},[1152,1222,1223],{},[342,1224,1225],{},"Set the namespace isolation policy.",[1158,1227,1230],{"className":1228,"code":1229,"language":1163},[1161],"\nbin\u002Fpulsar-admin ns-isolation-policy set \\\n--auto-failover-policy-type min_available \\\n--auto-failover-policy-params min_limit=1,usage_threshold=80 \\\n--namespaces public\u002Fns-isolation \\\n--primary \"broker1:*\" \\\n--secondary \"broker2:*\" \\\ntest ns-broker-isolation\n\n",[1165,1231,1229],{"__ignoreMap":18},[1152,1233,1234],{},[342,1235,1236],{},"Get the namespace isolation policies.",[1158,1238,1241],{"className":1239,"code":1240,"language":1163},[1161],"\nbin\u002Fpulsar-admin ns-isolation-policy list test\n# output\nns-broker-isolation    NamespaceIsolationDataImpl(namespaces=[public\u002Fns-isolation], primary=[broker1:*], secondary=[broker2:*], autoFailoverPolicy=AutoFailoverPolicyDataImpl(policyType=min_available, parameters={min_limit=1, usage_threshold=80}))\n\n",[1165,1242,1240],{"__ignoreMap":18},[1152,1244,1245],{},[342,1246,1247],{},"Create a partitioned topic.",[1158,1249,1252],{"className":1250,"code":1251,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics create-partitioned-topic -p 10 public\u002Fns-isolation\u002Ft1\n\n",[1165,1253,1251],{"__ignoreMap":18},[1152,1255,1256],{},[342,1257,1258],{},"Do a partitioned lookup.",[1158,1260,1263],{"className":1261,"code":1262,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics partitioned-lookup public\u002Fns-isolation\u002Ft1\n# output\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-0    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-1    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-2    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-3    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-4    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-5    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-6    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-7    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-8    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-9    pulsar:\u002F\u002Fbroker1:6650\n\n",[1165,1264,1262],{"__ignoreMap":18},[48,1266,1267],{},[351,1268],{"alt":1269,"src":1270},"illustration of brokers with arrow to broker 1","\u002Fimgs\u002Fblogs\u002F63bf2b8ade20fa9586bacffc_image2.png",[1152,1272,1273],{},[342,1274,1275],{},"Stop broker1.",[1158,1277,1280],{"className":1278,"code":1279,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose stop broker1\n# output\nStopping broker1 ... done\n\n",[1165,1281,1279],{"__ignoreMap":18},[1152,1283,1284],{},[342,1285,1286],{},"Check the partitioned lookup.",[48,1288,1289],{},"After broker1 stop, the topics will be owned by secondary broker broker2:*.",[1158,1291,1294],{"className":1292,"code":1293,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics partitioned-lookup public\u002Fns-isolation\u002Ft1\n# output\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-0    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-1    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-2    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-3    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-4    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-5    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-6    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-7    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-8    pulsar:\u002F\u002Fbroker2:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-9    pulsar:\u002F\u002Fbroker2:6650\n\n",[1165,1295,1293],{"__ignoreMap":18},[48,1297,1298],{},[351,1299],{"alt":1300,"src":1301},"illustration of broker","\u002Fimgs\u002Fblogs\u002F63bf2bb5f884416e148c9c61_mayiso2.png",[1152,1303,1304],{},[342,1305,1306],{},"Stop broker2.",[1158,1308,1311],{"className":1309,"code":1310,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose stop broker2\n# output\nStopping broker2 ... done\n\n",[1165,1312,1310],{"__ignoreMap":18},[1152,1314,1315],{},[342,1316,1286],{},[48,1318,1319],{},"After stopping broker2, there are no available brokers for namespace public\u002Fns-isolation-broker.",[1158,1321,1324],{"className":1322,"code":1323,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics partitioned-lookup public\u002Fns-isolation\u002Ft1\n# output\nHTTP 503 Service Unavailable\n\nReason: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable\n\n",[1165,1325,1323],{"__ignoreMap":18},[1152,1327,1328],{},[342,1329,1330],{},"Restart broker1 and broker2.",[1158,1332,1335],{"className":1333,"code":1334,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose start broker1\n# output\nStarting broker1 ... done\n\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose start broker2\n# output\nStarting broker2 ... done\n\n",[1165,1336,1334],{"__ignoreMap":18},[32,1338,1340],{"id":1339},"migrate-the-namespace-between-brokers","Migrate the Namespace between Brokers",[48,1342,1343],{},"Because the Pulsar broker is stateless, we can migrate the namespace between broker groups by simply changing the namespace isolation policy.",[1152,1345,1346],{},[342,1347,1348],{},"Check the namespace isolation policies.",[1158,1350,1352],{"className":1351,"code":1240,"language":1163},[1161],[1165,1353,1240],{"__ignoreMap":18},[48,1355,1356],{},"We could find that the primary and secondary brokers of the namespace public\u002Fns-isolation are broker1:* and broker2:*.",[1152,1358,1359],{},[342,1360,1361],{},"Check the topic partitioned lookup results.",[1158,1363,1365],{"className":1364,"code":1262,"language":1163},[1161],[1165,1366,1262],{"__ignoreMap":18},[1152,1368,1369],{},[342,1370,1371],{},"Modify a new namespace isolation policy.",[1158,1373,1376],{"className":1374,"code":1375,"language":1163},[1161],"\nbin\u002Fpulsar-admin ns-isolation-policy set \\\n--auto-failover-policy-type min_available \\\n--auto-failover-policy-params min_limit=1,usage_threshold=80 \\\n--namespaces public\u002Fns-isolation \\\n--primary \"broker3:*\" \\\n--secondary \"broker2:*\" \\\ntest ns-broker-isolation\n\n",[1165,1377,1375],{"__ignoreMap":18},[1152,1379,1380],{},[342,1381,1382],{},"Check the namespace isolation policy.",[1158,1384,1387],{"className":1385,"code":1386,"language":1163},[1161],"\nbin\u002Fpulsar-admin ns-isolation-policy list test\n# output\nns-broker-isolation    NamespaceIsolationDataImpl(namespaces=[public\u002Fns-isolation], primary=[broker3:*], secondary=[broker2:*], autoFailoverPolicy=AutoFailoverPolicyDataImpl(policyType=min_available, parameters={min_limit=1, usage_threshold=80}))\n\n",[1165,1388,1386],{"__ignoreMap":18},[1152,1390,1391],{},[342,1392,1393],{},"Unload the namespace to make the namespace isolation policy take effect.",[1158,1395,1398],{"className":1396,"code":1397,"language":1163},[1161],"\nbin\u002Fpulsar-admin namespaces unload public\u002Fns-isolation\n\n",[1165,1399,1397],{"__ignoreMap":18},[1152,1401,1402],{},[342,1403,1286],{},[48,1405,1406],{},"We could find that topics are already owned by the primary broker(broker3).",[1158,1408,1411],{"className":1409,"code":1410,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics partitioned-lookup public\u002Fns-isolation\u002Ft1\n# output\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-0    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-1    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-2    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-3    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-4    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-5    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-6    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-7    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-8    pulsar:\u002F\u002Fbroker3:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-9    pulsar:\u002F\u002Fbroker3:6650\n\n",[1165,1412,1410],{"__ignoreMap":18},[32,1414,1416],{"id":1415},"scale-up-and-down-brokers","Scale up and down Brokers",[818,1418,1420],{"id":1419},"scale-up","Scale up",[1152,1422,1423],{},[342,1424,1425],{},"Start broker4.",[48,1427,1428],{},"Add broker4 configurations in the docker-compose file.",[1158,1430,1433],{"className":1431,"code":1432,"language":1163},[1161],"\n  broker4:\n    hostname: broker4\n    container_name: broker4\n    image: apachepulsar\u002Fpulsar:latest\n    restart: on-failure\n    command: >\n      bash -c \"bin\u002Fapply-config-from-env.py conf\u002Fbroker.conf && \\\n               bin\u002Fapply-config-from-env.py conf\u002Fpulsar_env.sh && \\\n               bin\u002Fwatch-znode.py -z $$zookeeperServers -p \u002Finitialized-$$clusterName -w && \\\n               exec bin\u002Fpulsar broker\"\n    environment:\n      clusterName: test\n      zookeeperServers: zk1:2181\n      configurationStore: zk1:2181\n      webSocketServiceEnabled: \"false\"\n      functionsWorkerEnabled: \"false\"\n      managedLedgerMaxEntriesPerLedger: 100\n      managedLedgerMinLedgerRolloverTimeMinutes: 0\n    volumes:\n      - .\u002Fapply-config-from-env.py:\u002Fpulsar\u002Fbin\u002Fapply-config-from-env.py\n    depends_on:\n      - zk1\n      - pulsar-init\n      - bk1\n      - bk2\n      - bk3\n      - bk4\n    networks:\n      pulsar:\n\n",[1165,1434,1432],{"__ignoreMap":18},[48,1436,1425],{},[1158,1438,1441],{"className":1439,"code":1440,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose create\n# output\nzk1 is up-to-date\nbk1 is up-to-date\nbk2 is up-to-date\nbk3 is up-to-date\nbroker1 is up-to-date\nbroker2 is up-to-date\nbroker3 is up-to-date\nCreating broker4 ... done\nproxy1 is up-to-date\n\n",[1165,1442,1440],{"__ignoreMap":18},[1158,1444,1447],{"className":1445,"code":1446,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose start broker4\n# output\nStarting broker4 ... done\n\n",[1165,1448,1446],{"__ignoreMap":18},[1152,1450,1451],{},[342,1452,1453],{},"Check the broker list.",[1158,1455,1458],{"className":1456,"code":1457,"language":1163},[1161],"\nbin\u002Fpulsar-admin brokers list test\n# output\nbroker4:8080\nbroker1:8080\nbroker2:8080\nbroker3:8080\n\n",[1165,1459,1457],{"__ignoreMap":18},[1152,1461,1462],{},[342,1463,1464],{},"Set a namespace isolation policy.",[1158,1466,1469],{"className":1467,"code":1468,"language":1163},[1161],"\nbin\u002Fpulsar-admin ns-isolation-policy set \\\n--auto-failover-policy-type min_available \\\n--auto-failover-policy-params min_limit=1,usage_threshold=80 \\\n--namespaces public\u002Fns-isolation \\\n--primary \"broker1:*,broker4:*\" \\\n--secondary \"broker2:*\" \\\ntest ns-broker-isolation\n\n",[1165,1470,1468],{"__ignoreMap":18},[1152,1472,1473],{},[342,1474,1236],{},[1158,1476,1479],{"className":1477,"code":1478,"language":1163},[1161],"\nbin\u002Fpulsar-admin ns-isolation-policy list test\n# output\nns-broker-isolation    NamespaceIsolationDataImpl(namespaces=[public\u002Fns-isolation], primary=[broker1:*, broker4:*], secondary=[broker2:*], autoFailoverPolicy=AutoFailoverPolicyDataImpl(policyType=min_available, parameters={min_limit=1, usage_threshold=80}))\n\n",[1165,1480,1478],{"__ignoreMap":18},[1152,1482,1483],{},[342,1484,1485],{},"Unload the namespace.",[1158,1487,1489],{"className":1488,"code":1397,"language":1163},[1161],[1165,1490,1397],{"__ignoreMap":18},[1152,1492,1493],{},[342,1494,1286],{},[48,1496,1497],{},"The topic should be owned by broker1 and broker4.",[1158,1499,1502],{"className":1500,"code":1501,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics partitioned-lookup public\u002Fns-isolation\u002Ft1\n# output\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-0    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-1    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-2    pulsar:\u002F\u002Fbroker4:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-3    pulsar:\u002F\u002Fbroker4:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-4    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-5    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-6    pulsar:\u002F\u002Fbroker4:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-7    pulsar:\u002F\u002Fbroker4:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-8    pulsar:\u002F\u002Fbroker1:6650\npersistent:\u002F\u002Fpublic\u002Fns-isolation\u002Ft1-partition-9    pulsar:\u002F\u002Fbroker1:6650\n\n",[1165,1503,1501],{"__ignoreMap":18},[818,1505,1507],{"id":1506},"scale-down","Scale down",[1152,1509,1510],{},[342,1511,1512],{},"Remove broker4 from the namespace isolation policy.",[1158,1514,1516],{"className":1515,"code":1229,"language":1163},[1161],[1165,1517,1229],{"__ignoreMap":18},[1152,1519,1520],{},[342,1521,1382],{},[1158,1523,1525],{"className":1524,"code":1240,"language":1163},[1161],[1165,1526,1240],{"__ignoreMap":18},[1152,1528,1529],{},[342,1530,1531],{},"Stop broker4.",[1158,1533,1536],{"className":1534,"code":1535,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose stop broker4\n# output\nStopping broker4 ... done\n\n",[1165,1537,1535],{"__ignoreMap":18},[1152,1539,1540],{},[342,1541,1453],{},[1158,1543,1546],{"className":1544,"code":1545,"language":1163},[1161],"\nbin\u002Fpulsar-admin brokers list test\n# output\nbroker1:8080\nbroker2:8080\nbroker3:8080\n\n",[1165,1547,1545],{"__ignoreMap":18},[1152,1549,1550],{},[342,1551,1286],{},[1158,1553,1555],{"className":1554,"code":1262,"language":1163},[1161],[1165,1556,1262],{"__ignoreMap":18},[40,1558,1560],{"id":1559},"bookkeeper-isolation","BookKeeper Isolation",[1152,1562,1563],{},[342,1564,1565],{},"Get the bookie list.",[1158,1567,1570],{"className":1568,"code":1569,"language":1163},[1161],"\nbin\u002Fpulsar-admin bookies list-bookies\n# output\n{\n  \"bookies\" : [ {\n    \"bookieId\" : \"bk2:3181\"\n  }, {\n    \"bookieId\" : \"bk4:3181\"\n  }, {\n    \"bookieId\" : \"bk3:3181\"\n  }, {\n    \"bookieId\" : \"bk1:3181\"\n  } ]\n}\n\n",[1165,1571,1569],{"__ignoreMap":18},[1152,1573,1574],{},[342,1575,1576],{},"Set the bookie rack.",[48,1578,1579],{},"The default value of the configuration bookkeeperClientRackawarePolicyEnabled is true, so the RackawareEnsemblePlacementPolicy is the default bookie isolation policy, we'll set the rack name like this \u002Frack.",[1158,1581,1584],{"className":1582,"code":1583,"language":1163},[1161],"\nbin\u002Fpulsar-admin bookies set-bookie-rack \\\n--bookie bk1:3181 \\\n--hostname bk1:3181 \\\n--group group1 \\\n--rack \u002Frack1\n\nbin\u002Fpulsar-admin bookies set-bookie-rack \\\n--bookie bk3:3181 \\\n--hostname bk3:3181 \\\n--group group1 \\\n--rack \u002Frack1\n\nbin\u002Fpulsar-admin bookies set-bookie-rack \\\n--bookie bk2:3181 \\\n--hostname bk2:3181 \\\n--group group2 \\\n--rack \u002Frack2\n\nbin\u002Fpulsar-admin bookies set-bookie-rack \\\n--bookie bk4:3181 \\\n--hostname bk4:3181 \\\n--group group2 \\\n--rack \u002Frack2\n\n",[1165,1585,1583],{"__ignoreMap":18},[1152,1587,1588],{},[342,1589,1590],{},"Check the bookie racks placement.",[1158,1592,1595],{"className":1593,"code":1594,"language":1163},[1161],"\nbin\u002Fpulsar-admin bookies racks-placement\ngroup1    {bk1:3181=BookieInfoImpl(rack=\u002Frack1, hostname=bk1:3181), bk3:3181=BookieInfoImpl(rack=\u002Frack1, hostname=bk3:3181)}\ngroup2    {bk2:3181=BookieInfoImpl(rack=\u002Frack2, hostname=bk2:3181), bk4:3181=BookieInfoImpl(rack=\u002Frack2, hostname=bk4:3181)}\n\n",[1165,1596,1594],{"__ignoreMap":18},[1152,1598,1599],{},[342,1600,1601],{},"Set the bookie affinity group for the namespace.",[1158,1603,1606],{"className":1604,"code":1605,"language":1163},[1161],"\nbin\u002Fpulsar-admin namespaces set-bookie-affinity-group public\u002Fns-isolation \\\n--primary-group group1 \\\n--secondary-group group2\n\n",[1165,1607,1605],{"__ignoreMap":18},[1152,1609,1610],{},[342,1611,1612],{},"Check the namespace affinity group.",[1158,1614,1617],{"className":1615,"code":1616,"language":1163},[1161],"\nbin\u002Fpulsar-admin namespaces get-bookie-affinity-group public\u002Fns-isolation\n{\n  \"bookkeeperAffinityGroupPrimary\" : \"group1\",\n  \"bookkeeperAffinityGroupSecondary\" : \"group2\"\n}\n\n",[1165,1618,1616],{"__ignoreMap":18},[1152,1620,1621],{},[342,1622,1623],{},"Produce messages to the topic.",[1158,1625,1628],{"className":1626,"code":1627,"language":1163},[1161],"\nbin\u002Fpulsar-client produce -m 'hello' -n 500 public\u002Fns-isolation\u002Ft2\n\n",[1165,1629,1627],{"__ignoreMap":18},[1152,1631,1632],{},[342,1633,1634],{},"Get internal stats of the topic.",[1158,1636,1639],{"className":1637,"code":1638,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics stats-internal public\u002Fns-isolation\u002Ft2 | grep ledgerId | tail -n 6\n    \"ledgerId\" : 0,\n    \"ledgerId\" : 1,\n    \"ledgerId\" : 2,\n    \"ledgerId\" : 3,\n    \"ledgerId\" : 4,\n    \"ledgerId\" : -1,\n\n",[1165,1640,1638],{"__ignoreMap":18},[1152,1642,1643],{},[342,1644,1645,1646,190],{},"Check ledger ensembles for the ledgers ",[970,1647,1648],{},"0, 1, 2, 3, 4",[1158,1650,1653],{"className":1651,"code":1652,"language":1163},[1161],"\n# execute these commands in the node bk1\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk1 \u002Fbin\u002Fbash\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 0\n# check ensembles\nensembles={0=[bk1:3181, bk3:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 1\n# check ensembles\nensembles={0=[bk3:3181, bk1:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 2\n# check ensembles\nensembles={0=[bk1:3181, bk3:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 3\n# check ensembles\nensembles={0=[bk1:3181, bk3:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 4\n# check ensembles\nensembles={0=[bk1:3181, bk3:3181]}\n\n",[1165,1654,1652],{"__ignoreMap":18},[1152,1656,1657],{},[342,1658,1659],{},"Stop bookie1.",[1158,1661,1664],{"className":1662,"code":1663,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose stop bk1\n\n",[1165,1665,1663],{"__ignoreMap":18},[1152,1667,1668],{},[342,1669,1623],{},[1158,1671,1673],{"className":1672,"code":1627,"language":1163},[1161],[1165,1674,1627],{"__ignoreMap":18},[1152,1676,1677],{},[342,1678,1679],{},"Check ledger metadata.",[1158,1681,1684],{"className":1682,"code":1683,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics stats-internal public\u002Fns-isolation\u002Ft2 | grep ledgerId | tail -n 6\n    \"ledgerId\" : 5,\n    \"ledgerId\" : 6,\n    \"ledgerId\" : 7,\n    \"ledgerId\" : 8,\n    \"ledgerId\" : 9,\n    \"ledgerId\" : -1,\n\n",[1165,1685,1683],{"__ignoreMap":18},[48,1687,1688,1689,1692],{},"Check ledger metadata for the newly added ledgers ",[970,1690,1691],{},"5,6,7,8,9",". Because bookie1 is not usable and the configuration bookkeeperClientEnforceMinNumRacksPerWriteQuorum is false, we should find that the secondary bookies are used. Bookie3 is in the primary group so bookie3 is always used.",[1158,1694,1697],{"className":1695,"code":1696,"language":1163},[1161],"\n# execute these commands in the node bk2\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 \u002Fbin\u002Fbash\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 5\n# check ensembles\nensembles={0=[bk4:3181, bk3:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 6\n# check ensembles\nensembles={0=[bk3:3181, bk2:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 7\n# check ensembles\nensembles={0=[bk2:3181, bk3:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 8\n# check ensembles\nensembles={0=[bk3:3181, bk2:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 9\n# check ensembles\nensembles={0=[bk3:3181, bk2:3181]}\n\n",[1165,1698,1696],{"__ignoreMap":18},[48,1700,1701],{},"Restart bk1",[1158,1703,1706],{"className":1704,"code":1705,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose start bk1\n\n",[1165,1707,1705],{"__ignoreMap":18},[32,1709,1711],{"id":1710},"migrate-bookie-affinity-group","Migrate Bookie Affinity Group",[1152,1713,1714],{},[342,1715,1716],{},"Check the bookie affinity group.",[1158,1718,1720],{"className":1719,"code":1616,"language":1163},[1161],[1165,1721,1616],{"__ignoreMap":18},[1152,1723,1724],{},[342,1725,1726],{},"Modify the bookie affinity group of the namespace.",[1158,1728,1731],{"className":1729,"code":1730,"language":1163},[1161],"\nbin\u002Fpulsar-admin namespaces set-bookie-affinity-group public\u002Fns-isolation \\\n--primary-group group2\n\n",[1165,1732,1730],{"__ignoreMap":18},[1152,1734,1735],{},[342,1736,1716],{},[1158,1738,1741],{"className":1739,"code":1740,"language":1163},[1161],"\nbin\u002Fpulsar-admin namespaces get-bookie-affinity-group public\u002Fns-isolation\n{\n  \"bookkeeperAffinityGroupPrimary\" : \"group2\"\n}\n\n",[1165,1742,1740],{"__ignoreMap":18},[1152,1744,1745],{},[342,1746,1485],{},[1158,1748,1750],{"className":1749,"code":1397,"language":1163},[1161],[1165,1751,1397],{"__ignoreMap":18},[1152,1753,1754],{},[342,1755,1756],{},"Produce messages.",[1158,1758,1760],{"className":1759,"code":1627,"language":1163},[1161],[1165,1761,1627],{"__ignoreMap":18},[1152,1763,1764],{},[342,1765,1766],{},"Check the ensemble's bookies for newly created ledgers.",[1158,1768,1771],{"className":1769,"code":1770,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics stats-internal public\u002Fns-isolation\u002Ft2 | grep ledgerId | tail -n 6\n    \"ledgerId\" : 12,\n    \"ledgerId\" : 13,\n    \"ledgerId\" : 14,\n    \"ledgerId\" : 15,\n    \"ledgerId\" : 16,\n    \"ledgerId\" : -1,\n\n",[1165,1772,1770],{"__ignoreMap":18},[1152,1774,1775],{},[342,1776,1688,1777,190],{},[970,1778,1779],{},"12, 13, 14, 15, 16",[1158,1781,1784],{"className":1782,"code":1783,"language":1163},[1161],"\n# execute these commands in the node bk2\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 \u002Fbin\u002Fbash\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 12\n# check ensembles\nensembles={0=[bk4:3181, bk2:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 13\n# check ensembles\nensembles={0=[bk4:3181, bk2:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 14\n# check ensembles\nensembles={0=[bk4:3181, bk2:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 15\n# check ensembles\nensembles={0=[bk4:3181, bk2:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 16\n# check ensembles\nensembles={0=[bk2:3181, bk4:3181]}\n\n",[1165,1785,1783],{"__ignoreMap":18},[32,1787,1789],{"id":1788},"scale-up-and-down-bookies","Scale up and down Bookies",[818,1791,1420],{"id":1792},"scale-up-1",[1152,1794,1795],{},[342,1796,1797],{},"Add the following configuration in the docker-compose file.",[1158,1799,1802],{"className":1800,"code":1801,"language":1163},[1161],"\n  bk5:\n    hostname: bk5\n    container_name: bk5\n    image: apachepulsar\u002Fpulsar:latest\n    command: >\n      bash -c \"export dbStorage_writeCacheMaxSizeMb=\"${dbStorage_writeCacheMaxSizeMb:-16}\" && \\\n               export dbStorage_readAheadCacheMaxSizeMb=\"${dbStorage_readAheadCacheMaxSizeMb:-16}\" && \\\n               bin\u002Fapply-config-from-env.py conf\u002Fbookkeeper.conf && \\\n               bin\u002Fapply-config-from-env.py conf\u002Fpulsar_env.sh && \\\n               bin\u002Fwatch-znode.py -z $$zkServers -p \u002Finitialized-$$clusterName -w && \\\n               exec bin\u002Fpulsar bookie\"\n    environment:\n      clusterName: test\n      zkServers: zk1:2181\n      numAddWorkerThreads: 8\n      useHostNameAsBookieID: \"true\"\n    volumes:\n      - .\u002Fapply-config-from-env.py:\u002Fpulsar\u002Fbin\u002Fapply-config-from-env.py\n    depends_on:\n      - zk1\n      - pulsar-init\n    networks:\n      pulsar:\n\n",[1165,1803,1801],{"__ignoreMap":18},[1152,1805,1806],{},[342,1807,1808],{},"Start bookie5.",[1158,1810,1813],{"className":1811,"code":1812,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose create\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose start bk5\n\n",[1165,1814,1812],{"__ignoreMap":18},[1152,1816,1817],{},[342,1818,1819],{},"Check the readable and writable bookie list. Because bookie1 is stopped, there should be 4 bookies.",[1158,1821,1824],{"className":1822,"code":1823,"language":1163},[1161],"\n# execute this command in bk2\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 bin\u002Fbookkeeper shell listbookies -rw\n\n",[1165,1825,1823],{"__ignoreMap":18},[1158,1827,1830],{"className":1828,"code":1829,"language":1163},[1161],"\nReadWrite Bookies :\nBookieID:bk2:3181, IP:192.168.32.5, Port:3181, Hostname:bk2\nBookieID:bk4:3181, IP:192.168.32.7, Port:3181, Hostname:bk4\nBookieID:bk3:3181, IP:192.168.32.6, Port:3181, Hostname:bk3\nBookieID:bk1:3181, IP:192.168.32.4, Port:3181, Hostname:bk1\nBookieID:bk5:3181, IP:192.168.32.9, Port:3181, Hostname:bk5\n\n",[1165,1831,1829],{"__ignoreMap":18},[1152,1833,1834],{},[342,1835,1836],{},"Add the newly added bookie node to the primary group.",[1158,1838,1841],{"className":1839,"code":1840,"language":1163},[1161],"\nbin\u002Fpulsar-admin bookies set-bookie-rack \\\n--bookie bk5:3181 \\\n--hostname bk5:3181 \\\n--group group2 \\\n--rack \u002Frack2\n\n",[1165,1842,1840],{"__ignoreMap":18},[1152,1844,1845],{},[342,1846,1590],{},[1158,1848,1851],{"className":1849,"code":1850,"language":1163},[1161],"\nbin\u002Fpulsar-admin bookies racks-placement\ngroup1    {bk1:3181=BookieInfoImpl(rack=\u002Frack1, hostname=bk1:3181), bk3:3181=BookieInfoImpl(rack=\u002Frack1, hostname=bk3:3181)}\ngroup2    {bk2:3181=BookieInfoImpl(rack=\u002Frack2, hostname=bk2:3181), bk4:3181=BookieInfoImpl(rack=\u002Frack2, hostname=bk4:3181), bk5:3181=BookieInfoImpl(rack=\u002Frack2, hostname=bk5:3181)}\n\n",[1165,1852,1850],{"__ignoreMap":18},[1152,1854,1855],{},[342,1856,1485],{},[1158,1858,1860],{"className":1859,"code":1397,"language":1163},[1161],[1165,1861,1397],{"__ignoreMap":18},[1152,1863,1864],{},[342,1865,1866],{},"Produce messages to a new topic.",[1158,1868,1870],{"className":1869,"code":1627,"language":1163},[1161],[1165,1871,1627],{"__ignoreMap":18},[1152,1873,1874],{},[342,1875,1876],{},"Check the newly added ledger of the topic.",[1158,1878,1881],{"className":1879,"code":1880,"language":1163},[1161],"\nbin\u002Fpulsar-admin topics stats-internal public\u002Fns-isolation\u002Ft2 | grep ledgerId | tail -n 6\n    \"ledgerId\" : 17,\n    \"ledgerId\" : 20,\n    \"ledgerId\" : 21,\n    \"ledgerId\" : 22,\n    \"ledgerId\" : 23,\n    \"ledgerId\" : -1,\n\n",[1165,1882,1880],{"__ignoreMap":18},[48,1884,1885],{},"Verify ledger ensembles, we could find that the new created ledgers are all wrote to primary group, because there are enough rw bookies.",[1158,1887,1890],{"className":1888,"code":1889,"language":1163},[1161],"\n# execute these commands in the node bk1\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 \u002Fbin\u002Fbash\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 17\n# check ensembles\nensembles={0=[bk5:3181, bk2:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 20\n# check ensembles\nensembles={0=[bk2:3181, bk4:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 21\n# check ensembles\nensembles={0=[bk5:3181, bk4:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 22\n# check ensembles\nensembles={0=[bk5:3181, bk4:3181]}\n\nbin\u002Fbookkeeper shell ledgermetadata -ledgerid 23\n# check ensembles\nensembles={0=[bk2:3181, bk4:3181]}\n\n",[1165,1891,1889],{"__ignoreMap":18},[32,1893,1507],{"id":1894},"scale-down-1",[1152,1896,1897],{},[342,1898,1899],{},"Check the placement of the racks.",[1158,1901,1903],{"className":1902,"code":1850,"language":1163},[1161],[1165,1904,1850],{"__ignoreMap":18},[1152,1906,1907],{},[342,1908,1909],{},"Delete the bookie from the affinity bookie group.",[1158,1911,1914],{"className":1912,"code":1913,"language":1163},[1161],"\nbin\u002Fpulsar-admin bookies delete-bookie-rack -b bk5:3181\n\n",[1165,1915,1913],{"__ignoreMap":18},[1152,1917,1918],{},[342,1919,1920],{},"Check if there are under-replicated ledgers, which should be expected because we deleted a bookie.",[1158,1922,1925],{"className":1923,"code":1924,"language":1163},[1161],"\n# execute these commands in the node bk2\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 bin\u002Fbookkeeper shell listunderreplicated\n\n",[1165,1926,1924],{"__ignoreMap":18},[1152,1928,1929],{},[342,1930,1931],{},"Stop the bookie.",[1158,1933,1936],{"className":1934,"code":1935,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose stop bk5\n\n",[1165,1937,1935],{"__ignoreMap":18},[1152,1939,1940],{},[342,1941,1942],{},"Decommission the bookie.",[1158,1944,1947],{"className":1945,"code":1946,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 bin\u002Fbookkeeper shell decommissionbookie -bookieid bk5:3181\n\n",[1165,1948,1946],{"__ignoreMap":18},[1152,1950,1951],{},[342,1952,1953],{},"Check ledgers in the decommissioned bookie.",[1158,1955,1958],{"className":1956,"code":1957,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 bin\u002Fbookkeeper shell listledgers -bookieid bk5:3181\n\n",[1165,1959,1957],{"__ignoreMap":18},[1152,1961,1962],{},[342,1963,1964],{},"List the bookies.",[1158,1966,1969],{"className":1967,"code":1968,"language":1163},[1161],"\n${DOCKER_COMPOSE_HOME}\u002Fdocker-compose exec bk2 bin\u002Fbookkeeper shell listbookies -rw\nReadWrite Bookies :\nBookieID:bk2:3181, IP:192.168.48.5, Port:3181, Hostname:bk2\nBookieID:bk4:3181, IP:192.168.48.7, Port:3181, Hostname:bk4\nBookieID:bk3:3181, IP:192.168.48.6, Port:3181, Hostname:bk3\nBookieID:bk1:3181, IP:192.168.48.4, Port:3181, Hostname:bk1\n\n",[1165,1970,1968],{"__ignoreMap":18},[40,1972,1974],{"id":1973},"whats-next","What’s Next",[1152,1976,1977,1980,1984,1988,1992,2001,2009],{},[342,1978,1979],{},"Read the previous blogs in this series to learn more about Pulsar isolation:",[342,1981,1982],{},[55,1983,1105],{"href":1104},[342,1985,1986],{},[55,1987,1121],{"href":1120},[342,1989,1990],{},[55,1991,1128],{"href":1127},[342,1993,1994,1995,2000],{},"Learn Pulsar Fundamentals with StreamNative Academy: If you are new to Pulsar, we recommend taking the ",[55,1996,1999],{"href":1997,"rel":1998},"https:\u002F\u002Fwww.academy.streamnative.io\u002F",[264],"self-paced Pulsar courses"," developed by the original creators of Pulsar.",[342,2002,2003,2004,2008],{},"Spin up a Pulsar cluster in minutes: ",[55,2005,2007],{"href":958,"rel":2006},[264],"Sign up for StreamNative Cloud"," today. StreamNative Cloud is the simple, fast, and cost-effective way to run Pulsar in the public cloud.",[342,2010,2011,2012,2017],{},"Save your spot at the Pulsar Summit San Francisco: The first in-person Pulsar Summit is taking place this August! ",[55,2013,2016],{"href":2014,"rel":2015},"https:\u002F\u002Fpulsar-summit.org\u002F",[264],"Sign up today"," to join the Pulsar community and the messaging and event streaming community.",{"title":18,"searchDepth":19,"depth":19,"links":2019},[2020,2021,2022,2026,2031],{"id":42,"depth":19,"text":46},{"id":1135,"depth":19,"text":1136},{"id":1194,"depth":19,"text":1195,"children":2023},[2024,2025],{"id":1339,"depth":279,"text":1340},{"id":1415,"depth":279,"text":1416},{"id":1559,"depth":19,"text":1560,"children":2027},[2028,2029,2030],{"id":1710,"depth":279,"text":1711},{"id":1788,"depth":279,"text":1789},{"id":1894,"depth":279,"text":1507},{"id":1973,"depth":19,"text":1974},"Apache Pulsar","2022-06-01","This blog provides a step-by-step tutorial on how to use a single cluster to achieve broker and bookie isolation.",{},"\u002Fblog\u002Fpulsar-isolation-part-iv-single-cluster-isolation","30 min read",{"title":1088,"description":2034},"blog\u002Fpulsar-isolation-part-iv-single-cluster-isolation",[2041,2032],"Tutorials","cw1k4PzRSwsLJsiLpI1Jam4nCltGLLOMi9dW3NlEJH4",[2044],{"id":2045,"title":1090,"bioSummary":2046,"email":289,"extension":8,"image":2047,"linkedinUrl":289,"meta":2048,"position":2055,"stem":2056,"twitterUrl":2057,"__hash__":2058},"authors\u002Fauthors\u002Fran-gao.md","Ran Gao is a software engineer at StreamNative. Before that, he was responsible for the development of search service at Zhaopin.com. Prior to that, he worked on the development of the logistics system at JD Logistics. Being interested in open source and messaging systems, Ran is an Apache Pulsar committer.","\u002Fimgs\u002Fauthors\u002Fran-gao.webp",{"body":2049},{"type":15,"value":2050,"toc":2053},[2051],[48,2052,2046],{},{"title":18,"searchDepth":19,"depth":19,"links":2054},[],"Software Engineer, StreamNative","authors\u002Fran-gao","https:\u002F\u002Ftwitter.com\u002Fleon_ran_10","3A9nHLkyET8EJYbIiXraydYB66H4E01wA5ojbBtJjFc",[2060,2068,2073],{"path":2061,"title":2062,"date":2063,"image":2064,"link":-1,"collection":2065,"resourceType":2066,"score":2067,"id":2061},"\u002Fblog\u002Fdeep-dive-into-data-placement-policies","Data Placement Policy Best Practices for Apache Pulsar","2023-07-16","\u002Fimgs\u002Fblogs\u002F63c7f9f43d691125f4ff6429_63b3ff32877620a3217db989_deep-dive-of-data-placement-policies-top-.jpeg","blogs","Blog",1,{"path":2069,"title":2070,"date":2071,"image":2072,"link":-1,"collection":2065,"resourceType":2066,"score":2067,"id":2069},"\u002Fblog\u002Fintroducing-pulsar-admin-go-library-for-go-developers","Introducing the Pulsar Admin Library for Go","2023-04-11","\u002Fimgs\u002Fblogs\u002F6435d00f3e8670998834c3bb_PulsarAdminGo.jpg",{"path":2074,"title":2075,"date":2076,"image":2077,"link":-1,"collection":2065,"resourceType":2066,"score":2067,"id":2074},"\u002Fblog\u002Fspring-into-pulsar-part-3-building-an-application-with-the-new-spring-library-for-apache-pulsar","Spring into Pulsar Part 3: Building An Application with the New Spring Library for Apache Pulsar","2023-02-21","\u002Fimgs\u002Fblogs\u002F6406944ce2dfd0dc96ea7ba3_spring-into-pulsar-part-3-building-an-application-with-the-new-spring-library-for-apache-pulsar.png",1776409759559]