The Evolution History of RoP(RocketMQ-on-Pulsar) - Pulsar Summit Asia 2021

•Descargar como PPTX, PDF•

0 recomendaciones•97 vistas

Recently, the Tencent Cloud MQ team open sourced the 0.1.0 version of RoP(RocketMQ on Pulsar). However, many problems occurred during production practices, such as message ID overflow, incomplete message consumption, unbalanced load on consumption model, and invalid consumption requests. We made a series of optimizations for the above problems in RoP 0.2.0, and improved the overall performance and stability of the current RoP version. In this session, we will introduce the RoP MessageID refactoring, design and implementation of RoP delayed message and routing protocol, RoP ACL design and implementation, RoP performance optimization and the application of RoP in Tencent Cloud. Key takeaways： 1. Common design and implementation ideas for delayed messages in message queues 2. Implementation ideas and practical applications of Apache Pulsar Broker Entry metadata 3. Different ideas for the realization of message routing between Apache RocketMQ and Apache Pulsar 4. The similarities, differences and combination of authentication implementation schemas between Apache Pulsar and Apache RocketMQ.

Internet

Who am i
• PingCAP -> StreamNative -> Tencent
• Apache Pulsar committer
• Apache BookKeeper contributor
• RoP maintainer
• Apache Pulsar Go client 作者
• Apache Pulsar Go Functions 作者
• StreamNative/pulsarctl 作者

RoP 1.0 offset 处理
RocketMQ 64 Bit Offset
Pulsar
8 bit
Partition ID 32 bit Ledger ID 24 bit Entry ID

• 精度丢失
• 对 RocketMQ offset 认识不足
• queue offset
• commitlog offset
存在的问题:

https://github.com/apache/pulsar/wiki/PIP-70%3A-Introduce-lightweight-broker-entry-metadata
TOTAL_SIZE CMD_SIZE CMD MAGIC_NUMBER CHECKSUM METADATA_SIZE METADATA PAYLOAD
原始消息协议：
MAGIC_NUMBER CHECKSUM METADATA_SIZE METADATA PAYLOAD
HEADERS_AND_PAYLOAD
HEADERS_AND_PAYLOAD
Broker Entry Metadata 消息协议：
BROKER_ENTRY_METADATA
BROKER_ENTRY_METADATA_SIZE
BROKER_ENTRY_METADATA_MAGIC_NUMBER
PIP-70: Broker Entry Metadata
brokerEntryMetadataInterceptors=org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor

对 RocketMQ offset 认识不足
RoP 2.0 offset 处理

RocketMQ 64 Bit Offset
commitLog Offset
10 bit
partition nums
1
bit
保
留
位
1
bit
标
记
Retry
52 bit message offsets
RoP 2.0 offset 处理

RocketMQ 路由协议：
- Broker 服务的IP地址
- Broker 上对应 Topic 分区信息（数量+权限）
Rop Proxy
Broker-Tag + Broker-Topic-Seq

需要去处理的问题
- Topic 的映射关系存储到哪里
- 路由关系如何分配
- 当路由关系发生变化之后如何分配
Rop Proxy

Rop Proxy
存储在 zookeeper：
- 不需要引入新的组件
- 复用 Pulsar 自身的路由模型，实现简单
- 初始分配后虚拟节点和物理节点处于同一个节点上，性能好

Rop Proxy
Master-Slave 模型：
- 减少单节点故障对系统的影响
- 各个节点的元数据信息可以保持一致 – offset sotre CompactTopic

RoP 延迟消息
当前pulsar延迟消息存在的问题：
- 无法支持海量延迟消息
- 只能通过高阶consumer接口来读取数据

我们想要的延迟消息实现：
- 支持海量任意时间延迟消息 => 只加载最近的延迟消息到内存索引
- 支持通过底层cursor接口读取 => 在生产端实现消息延迟
RoP 延迟消息

优点：
- 抗积压
- 实现简单
- 扩展性强
缺点：
- 依赖外部系统（依赖稳定的kv存储）
- 兼容性差（不兼容pulsarproducer接口）
RoP 延迟消息

优点：
-抗积压
-不需要依赖外部系统
缺点：
-数据多次复制
-主题、分区数量多
RoP 延迟消息

Más contenido relacionado

La actualidad más candente

Php Webservers

samon127

Colonel转码集群

pluschen

lua & ngx_lua 的介绍与应用

hugo

高性能Web服务器Nginx及相关新技术的应用实践

rewinx

深入浅出Netty l.t

oleone

Openstack neutron 原理详解

Yong Luo

Kafka cluster best practices

Golang 高性能实战

Tcpcopy 阿里技术沙龙

Rpc原理与实现

Weibo lamp improvements

introduce Okhttp

基于Fuel的超融合一体机

微博Lamp性能优化之路(2014)

聊聊我接触的集群管理

How to upgrade_ror3_to_ror4

Golang advance

Linux bonding

MPTCP学习

Ryu Learning Guide

La actualidad más candente (20)

Php Webservers

Colonel转码集群

lua & ngx_lua 的介绍与应用

高性能Web服务器Nginx及相关新技术的应用实践

深入浅出Netty l.t

Openstack neutron 原理详解

Kafka cluster best practices

Golang 高性能实战

Tcpcopy 阿里技术沙龙

Rpc原理与实现

Weibo lamp improvements

introduce Okhttp

基于Fuel的超融合一体机

微博Lamp性能优化之路(2014)

聊聊我接触的集群管理

How to upgrade_ror3_to_ror4

Golang advance

Linux bonding

MPTCP学习

Ryu Learning Guide

Similar a The Evolution History of RoP(RocketMQ-on-Pulsar) - Pulsar Summit Asia 2021

淘宝前台系统性能分析与优化

丁宇

淘宝网前台应用性能优化实践

丁宇

Accelerating or Complicating PHP execution by LLVM Compiler Infrastructure

National Cheng Kung University

未来网络技术发展探梦 - 开篇

Yao-Wei Ou

Http协议介绍

Sanji Zhang

高性能远程调用解决方案

Ady Liu

Linux binary Exploitation - Basic knowledge

Angel Boy

用 golang 自製 db proxy (PostgreSQL) 以及 resource management api 在 GCP 上面利用 OLTP 資料庫的 snapshot 來擴展負擔沈重的分析型查詢，並按需求實作不同 resource controller plugin 來最佳化資料庫與控制成本。使用的 library 與實作範例: https://github.com/rueian/godemand-example https://github.com/rueian/godemand https://github.com/rueian/pgproxy

Scaling Offline Database Usage On GCP @ Dcard

Jui An Huang (黃瑞安)

Binary exploitation - AIS3

Angel Boy

第18讲 Hdlc和Ppp

F.l. Yu

Lamp优化实践

zhliji2

deep inside Sina App Engine cloud service

Sae

MongoDB at Qihoo 360

Node combo

網路技術心得分享

Pptv lb日志实时分析平台

Python 于 webgame 的应用

Elastic stack day-2

Building a server to manage high concurrent connections is non-trival task. For those developers that use ActionScript 3 to build games on the client side it means having a totally different skillset. Being able to use ActionScript 3 on the server to build MMO’s or port client code to the server allows developers to leverage their skills on the server. By walking through a live game example with more then 15,000 concurrent connections running on a medium Amazon EC2 server the presentation will: 1. Introduce Linux server configuration for high concurrent connected usage. 2. Introduce Socket class based on libev library for high concurrent connection. 3. Introduce leveraging Tamarin project for ActionScript 3 on the server.

构建ActionScript游戏服务器，支持超过15000并发连接

Renaun Erickson

Similar a The Evolution History of RoP(RocketMQ-on-Pulsar) - Pulsar Summit Asia 2021 (20)

淘宝前台系统性能分析与优化

淘宝网前台应用性能优化实践

Accelerating or Complicating PHP execution by LLVM Compiler Infrastructure

未来网络技术发展探梦 - 开篇

Http协议介绍

高性能远程调用解决方案

Linux binary Exploitation - Basic knowledge

Scaling Offline Database Usage On GCP @ Dcard

Binary exploitation - AIS3

第18讲 Hdlc和Ppp

Lamp优化实践

deep inside Sina App Engine cloud service

Sae

MongoDB at Qihoo 360

Node combo

網路技術心得分享

Pptv lb日志实时分析平台

Python 于 webgame 的应用

Elastic stack day-2

构建ActionScript游戏服务器，支持超过15000并发连接

Más de StreamNative

So, you are a responsible software engineer building microservices for Apache Kafka, and life is good. Eventually, you hear the community talking about the outstanding experience they are having with Apache Pulsar features. They talk about infinite event stream retention, a rebalance-free architecture, native support for event processing, and multi-tenancy. Exciting, right? Most people would want to migrate their code to Pulsar. Especially when you know that Pulsar also supports Kafka clients natively via the protocol handler known as KoP — which enables the Kafka client APIs on Pulsar. But, as said before, you are responsible; and you don't believe in fairy tales, just like you don't believe that migrations like this happen effortlessly. This session will discuss the architecture behind protocol handlers, what it means having one enabled on Pulsar, and how the KoP works. It will detail the effort required to migrate a microservice written for Kafka to Pulsar, and whether the code need to change for this.

Is Using KoP (Kafka-on-Pulsar) a Good Idea? - Pulsar Summit SF 2022

StreamNative

This talk describes Klaviyo’s internal messaging system, an asynchronous application framework built around Pulsar that provides a set of high-quality tools for building business-critical asynchronous data flows in unreliable environments. This framework includes: a pulsar ORM and schema migrator for topic configuration; a retry/replay system; a versioned schema registry; a consumer framework oriented around preventing message loss and in hostile environments while maximizing observability; an experimental “online schema change” for topics; and more. Development of this system was informed by lessons learned during heavy use of datastores like RabbitMQ and Kafka, and frameworks like Celery, Spark, and Flink. In addition to the capabilities of this system, this talk will also cover (sometimes painful) lessons learned about the process of converting a heterogenous async-computing environment onto Pulsar and a unified model.

Building an Asynchronous Application Framework with Python and Pulsar - Pulsa...

StreamNative

In this talk, learn how Toast leverages our Envoy control-plane to manage blue-green deploys of Pulsar consumers, and how this has helped drive adoption across the engineering organization. Dive into the history of Pulsar at Toast, starting from its introduction in 2019 to provide event-driven architecture across a rapidly scaling restaurant software platform. We will detail some of the hurdles that we encountered gaining buy-in across a diverse set of teams, and dive deep into how we enforce best practices and integrate with our service control plane.

Blue-green deploys with Pulsar & Envoy in an event-driven microservice ecosys...

StreamNative

Event streaming architectures launched a reexamination of applications and systems architectures across the board. We live in a world where answers are needed now in a constant real-time flow. Yet beyond the event streaming system itself, what are the corequisites to ensure our large scale distributed database systems can keep pace with this always-on, always-current real time flow of data? What are the requirements and expectations for this next tech cycle?

Distributed Database Design Decisions to Support High Performance Event Strea...

StreamNative

Pulsar Functions is a succinct framework provided by Apache Pulsar to conduct real-time data processing. Its use cases include ETL pipeline, event-driven applications, and simple data analytics. While Pulsar Functions already provides an extremely simple programming interface, we want to further lower the barrier for users to access real-time data. Since SQL is one of the universal languages in the technology world and well accepted by the vast majority of data engineers, we decided to add a SQL expressing layer on top of Pulsar Functions runtime. In this talk, we will discuss the architecture and implementation of this new service. We will see how SQL syntax, Pulsar Functions, and Function Mesh can work together to deliver a unique user development experience for real-time data jobs in the cloud environment. We will also walk through use cases like filtering, routing, and projecting messages as well as integrating with the Pulsar IO Connectors framework.

Simplify Pulsar Functions Development with SQL - Pulsar Summit SF 2022

StreamNative

Starting with version 2.10, the Apache ZooKeeper dependency has been eliminated and replaced with a pluggable framework that enables you to reduce the infrastructure footprint of Apache Pulsar by leveraging alternative metadata and coordination systems based on your deployment environment. In this talk, walk through the steps required to utilize the existing etcd service running inside Kubernetes to act as Pulsar's metadata store, thereby eliminating the need to run ZooKeeper entirely, leaving you with a Zookeeper-less Pulsar.

Towards a ZooKeeper-less Pulsar, etcd, etcd, etcd. - Pulsar Summit SF 2022

StreamNative

Apache Pulsar is a highly available, distributed messaging system that provides guarantees of no message loss and strong message ordering with predictable read and write latency. In this talk, learn how this can be validated for Apache Pulsar Kubernetes deployments. Various failures are injected using Chaos Mesh to simulate network and other infrastructure failure conditions. There are many questions that are asked about failure scenarios, but it could be hard to find answers to these important questions. When a failure happens, how long does it take to recover? Does it cause unavailability? How does it impact throughput and latency? Are the guarantees of no message loss and strong message ordering kept, even when components fail? If a complete availability zone fails, is the system configured correctly to handle AZ failures? This talk will help you find answers to these questions and apply the tooling and practices to your own testing and validation.

Validating Apache Pulsar’s Behavior under Failure Conditions - Pulsar Summit ...

StreamNative

Despite what the Ghostbusters said, we’re going to go ahead and cross (or, join) the streams. This session covers getting started with streaming data pipelines, maximizing Pulsar’s messaging system alongside one of the most flexible streaming frameworks available, Apache Flink. Specifically, we’ll demonstrate the use of Flink SQL, which provides various abstractions and allows your pipeline to be language-agnostic. So, if you want to leverage the power of a high-speed, highly customizable stream processing engine without the usual overhead and learning curves of the technologies involved (and their interconnected relationships), then this talk is for you. Watch the step-by-step demo to build a unified batch and streaming pipeline from scratch with Pulsar, via the Flink SQL client. This means you don’t need to be familiar with Flink, (or even a specific programming language). The examples provided are built for highly complex systems, but the talk itself will be accessible to any experience level.

Cross the Streams! Creating Streaming Data Pipelines with Apache Flink + Apac...

StreamNative

Apache Pulsar depends upon message acknowledgments to provide at-least-once or exactly-once processing guarantees. With these guarantees, any transmission between the broker and its producers and consumers requires an acknowledgment. But what happens if an acknowledgment is not received? Resending the message introduces the potential of duplicate processing and increases the likelihood of out or order processing. Therefore, it is critical to understand the Pulsar message redelivery semantics in order to prevent either of these conditions. In this talk, we will walk you through the redelivery semantics of Apache Pulsar, and highlight some of the control mechanisms available to application developers to control this behavior. Finally, we will present best practices for configuring message redelivery to suit various use cases.

Message Redelivery: An Unexpected Journey - Pulsar Summit SF 2022

StreamNative

Lakehouses are quickly growing in popularity as a new approach to Data Platform Architecture bringing some of the long-established benefits from OLTP world to OLAP, including transactions, record-level updates/deletes, and changes streaming. In this talk, we will discuss Apache Hudi and how it unlocks possibilities of building your own fully open-source Lakehouse featuring a rich set of integrations with existing technologies, including Apache Pulsar. In this session, we will present: - What Lakehouses are, and why they are needed. - What Apache Hudi is and how it works. - Provide a use-case and demo that applies Apache Hudi’s DeltaStreamer tool to ingest data from Apache Pulsar.

Unlocking the Power of Lakehouse Architectures with Apache Pulsar and Apache ...

StreamNative

Pulsar is a horizontally scalable messaging system, so the traffic in a logical cluster must be balanced across all the available Pulsar brokers as evenly as possible, in order to ensure full utilization of the broker layer. You can use multiple settings and tools to control the traffic distribution which requires a bit of context to understand how the traffic is managed in Pulsar. In this talk, we will walk you through the load balancing capabilities of Apache Pulsar, and highlight some of the control mechanisms available to control the distribution of load across the Pulsar brokers. Finally, we will discuss the various loading shedding strategies that are available. At the end of the talk, you will have a better understanding of how Pulsar's broker level auto-balancing works, and how to properly configure it to meet your workload demands.

Understanding Broker Load Balancing - Pulsar Summit SF 2022

StreamNative

Building an Asynchronous Application Framework with Python and Pulsar - Pulsa...

StreamNative

In today’s world, we are seeing a big shift toward the Cloud. With this shift comes a big shift in the expectations we have for a messaging system, especially when the messaging system is presented as managed service in a large-scale, multi-tenant environment. For any large-scale enterprise, it’s very important to evaluate messaging system and be confident before expanding complex distributed data systems like Apache Pulsar from on-premise to elastically scalable, fully managed services on cloud services. We must consider aspects such as: migration from and integration with large-scale on-premise clusters, security, cost efficiency, and the cloud friendliness of the architecture, modeling cost and capacity, tenant isolation, deployment robustness, availability, monitoring, etc. Not every messaging system is built to be cloud-native and run as a managed service with cost efficiency. We have been running large-scale Apache Pulsar at Yahoo for the last 8 years on various platforms and hardware configurations while meeting application SLAs and serving more than 1M topics in a cluster. In this talk, we will talk about Pulsar’s journey in Yahoo! from an on-premise platform to a hybrid cloud and on-premise system. We will talk about Pulsar’s architecture and features that make Pulsar a good cloud-native messaging-system choice for any enterprise.

Pulsar's Journey in Yahoo!: On-prem, Cloud and Hybrid - Pulsar Summit SF 2022

StreamNative

Pulsar Summit San Francisco is the event dedicated to Apache Pulsar. This one-day, action-packed event will include 5 keynotes, 12 breakout sessions, and 1 amazing happy hour. Speakers are from top companies, including Google, AWS, Databricks, Onehouse, StarTree, Intel, ScyllaDB, and more! It’s the perfect opportunity to network with Pulsar thought leaders in person. Join developers, architects, data engineers, DevOps professionals, and anyone who wants to learn about messaging and event streaming for this one-day, in-person event. Pulsar Summit San Francisco brings the Apache Pulsar Community together to share best practices and discuss the future of streaming technologies.

Event-Driven Applications Done Right - Pulsar Summit SF 2022

StreamNative

Our services team creates, builds, and maintains the as a service offering for base platform services within our organization. Several thousand applications use these custom services daily generating more than 700 million requests per minute. One of these services was our publish / subscriber offering, BQ with custom SDK and custom metrics based on Apache Pulsar. BQ is the core communication service within our organization, having more 200M RPM. All the core processes of the organization depend on this service for operation: the CDC of any of our RDBMS or NoSQL offering, all the eventing efforts of the organization, async communication between apps, notification systems, etc. The backend of the solution was Apache Pulsar running on EC2 on AWS and on top of that we built several components as wrappers of the actual backend, creating our own SDKs and abstractions and in many ways extending the features provided by Pulsar. We had a multi-cluster setup 100% on AWS, with custom Pulsar Docker images running on large ASG setups, along with our own wrapping and admin APIs and DBs. All of this in turn transformed the solution into a volatile solution.

Pulsar @ Scale. 200M RPM and 1K instances - Pulsar Summit SF 2022

StreamNative

There is an increasing need to unleash analytical capabilities directly to the end-users to democratize decision-making. User-Facing Analytics is a new frontier that will shape the products of tomorrow and push the limits of existing technology. It demands a solution that will scale to millions of users to provide fast, real-time insights. In this session, Xiang will talk about his journey to build Apache Pinot to tackle the analytics problem space with the architectural changes and technology inventions made over the past decade. He will also talk about how other big data companies such as LinkedIn, Uber, and Stripe power their user-facing analytical applications.

Data Democracy: Journey to User-Facing Analytics - Pulsar Summit SF 2022

StreamNative

Beam + Pulsar: Powerful Stream Processing at Scale - Pulsar Summit SF 2022

StreamNative

Welcome and Opening Remarks - Pulsar Summit SF 2022

StreamNative

Milvus is an open-source vector database that leverages a novel data fabric to build and manage vector similarity search applications. As the world's most popular vector database, it has already been adopted in production by thousands of companies around the world, including Lucidworks, Shutterstock, and Cloudinary. With the launch of Milvus 2.0, the community aims to introduce a cloud-native, highly scalable and extendable vector similarity solution, and the key design concept is log as data. Milvus relies on Pulsar as the log pub/sub system. Pulsar helps Milvus to reduce system complexity by loosely decoupling each micro service, making the system stateless by disaggregating log storage and computation, which also makes the system further extendable. We will introduce the overview design, the implementation details of Milvus and its roadmap in this topic. Takeaways: 1) Get a general idea about what is a vector database and its real-world use cases. 2) Understand the major design principles of Milvus 2.0. 3) Learn how to build a complex system with the help of a modern log system like Pulsar.

Log System As Backbone – How We Built the World’s Most Advanced Vector Databa...

StreamNative

MQTT (Message Queuing Telemetry Transport,) is a message protocol based on the pub/sub model with the advantages of compact message structure, low resource consumption, and high efficiency, which is suitable for IoT applications with low bandwidth and unstable network environments. This session will introduce MQTT on Pulsar, which allows developers users of MQTT transport protocol to use Apache Pulsar. I will share the architecture, principles and future planning of MoP, to help you understand Apache Pulsar's capabilities and practices in the IoT industry.

MoP(MQTT on Pulsar) - a Powerful Tool for Apache Pulsar in IoT - Pulsar Summi...

StreamNative

Más de StreamNative (20)