开源软件名称：

开源软件地址：

开源软件介绍：

RocketMQ on Pulsar(RoP)

RoP stands for RocketMQ on Pulsar. Rop broker supports RocketMQ-4.6.1 protocol, and is backed byPulsar.

RoP is implemented as aPulsar ProtocolHandlerwith protocol name "rocketmq". ProtocolHandler is build as a nar file, and is loaded when PulsarBroker starts.

Supported

RoP is implemented based on Pulsar features. Currently, the functions supported by RoP are asfollows:

• Send and Receive Messages
• SendAsync Messages
• Queue Selector Producer
• Round Robin Producer
• Producer And Consumer(Push and Pull) With Namespace
• Batch Messages
• Order Messages
• Send And Receive With Tag
• Deliver Level Message
• Retry Topic
• DLQ Topic
• Broadcast Consumer

Get started

In this guide, you will learn how to use the Pulsar broker to serve requests from RocketMQ client.

Download Pulsar

Download Pulsar 2.7.1binary package apache-pulsar-2.7.1-bin.tar.gz. and unzip it.

Note: Currently, RoP is only compatible with Apache Pulsar 2.7.0 and above.

Download and Build RoP Plugin

You can download rop nar file from the RoP sources.

To build from code, complete the following steps:

1. Clone the project from GitHub to your local.

git clone https://github.com/streamnative/rop.gitcd rop

2. Build the project.

mvn clean install -DskipTests

You can find the nar file in the following directory.

./target/pulsar-protocol-handler-rocketmq-${version}.nar

Configuration

Configure Pulsar broker to run RoP protocol handler as Plugin

As mentioned above, RoP module is loaded with Pulsar broker. You need to add configs in Pulsar'sconfig file, such as broker.conf or standalone.conf.

1. Protocol handler configuration

You need to add messagingProtocols(the default value is null), protocolHandlerDirectory (the default value is "./protocols") and loadManagerClassName=org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl, in Pulsar configuration files, such as broker.confor standalone.conf. For RoP, the value for messagingProtocols is rocketmq; the valuefor protocolHandlerDirectory is the directory of RoP nar file.

The following is an example.

messagingProtocols=rocketmqprotocolHandlerDirectory=./protocolsloadManagerClassName=org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl

2. Set RocketMQ service listeners

Set RocketMQ service listeners. Note that the hostname value in listeners is the same as Pulsarbroker's advertisedListeners.

The following is an example.

rocketmqListeners=rocketmq://127.0.0.1:9876advertisedListeners=INTERNAL:pulsar://127.0.0.1:6650,INTERNAL:pulsar+ssl://127.0.0.1:6651,INTERNAL_ROP:pulsar://127.0.0.1:9876,INTERNAL_ROP:pulsar+ssl://127.0.0.1:9896rocketmqListenerPortMap=9876:INTERNAL_ROP

3. Set offset management as below since offset management for RoP depends on Pulsar "Broker Entry Metadata". It’s required for KoP 2.8.0 or higher version.

brokerEntryMetadataInterceptors=org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor

4. Set brokerDeleteInactiveTopicsEnabled to false.

brokerDeleteInactiveTopicsEnabled=false

Note: advertisedListeners and advertisedAddress cannot be configured at the same time.

Run Pulsar broker

With the above configuration, you can start your Pulsar broker. For details, referto Pulsar Get started guides.

cd apache-pulsar-2.7.1bin/pulsar standalone -nss -nfw

Run RocketMQ Client to verify

In the RoP repo, we provide a sub model of examples, which contains a variety of scenarios used bythe rocketmq client. You can run these examples directly in the IDE. Or you can download theRocketMQ src code and run RocketMQ client of examples.

Log level configuration

In Pulsar log4j2.yaml config file,you can set RoP log level.

The following is an example.

    Logger:      - name: RocketMQProtocolHandler        level: debug        additivity: false        AppenderRef:          - ref: Console