rongtong
6a9e84f113
* chore: bump DLedger to 0.3.3.4 (maintenance line) Update the DLedger dependency from 0.3.2 to 0.3.3.4, the latest release on the 0.3.x maintenance line published on Maven Central. The 0.3.3.4 release is API-compatible with 0.3.2 and only carries dependency hygiene fixes (aligning fastjson2 and excluding fastjson1 from its rocketmq-remoting transitive path). Also update the Bazel WORKSPACE artifact coordinate to keep the two build systems in sync. * chore: fully remove fastjson1 from the build DLedger 0.3.3.4 already excludes com.alibaba:fastjson from its rocketmq-remoting dependency and its bytecode only references fastjson2, but rocketmq still declared fastjson1 itself, so it kept leaking onto every module compile classpath through rocketmq-common. - drop the com.alibaba:fastjson property and dependencyManagement entry from the root pom - drop the unused com.alibaba:fastjson dependency from rocketmq-common (no main source imports com.alibaba.fastjson.*) - drop the fastjson1 pin from WORKSPACE and the fastjson1 dep from the remoting test target in remoting/BUILD.bazel - migrate RemotingSerializableCompatTest to fastjson2: use the fastjson2 JSONField annotation (which is what the protocol classes actually carry) and round trip through RemotingSerializable instead of com.alibaba.fastjson.JSON fastjson1 wire-format coverage is retained by the frozen fastjson1 payload already asserted in testCompatibilityCheckWithBitSet. * fix(bazel): exclude rocketmq-remoting from coursier resolution dledger 0.3.3.4 depends on rocketmq-remoting:5.5.0, which Coursier fetches from Maven Central. That artifact transitively brings grpc-netty-shaded:1.53.0 with a strict [1.53.0] range on grpc-core, conflicting with the WORKSPACE-declared grpc 1.47.0 artifacts. Since rocketmq-remoting is built from source in this repo (//remoting), exclude it from external resolution — matching what PR #10947 already does for the DLedger 0.4.x line. --------- Co-authored-by: 通融 <rongtong.jrt@alibaba-inc.com>
Apache RocketMQ
Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability.
It offers a variety of features:
- Messaging patterns including publish/subscribe, request/reply and streaming
- Financial grade transactional message
- Built-in fault tolerance and high availability configuration options based on DLedger Controller
- Built-in message tracing capability, also supports opentracing
- Versatile big-data and streaming ecosystem integration
- Message retroactivity by time or offset
- Reliable FIFO and strict ordered messaging in the same queue
- Efficient pull and push consumption model
- Million-level message accumulation capacity in a single queue
- Multiple messaging protocols like gRPC, MQTT, JMS and OpenMessaging
- Flexible distributed scale-out deployment architecture
- Lightning-fast batch message exchange system
- Various message filter mechanics such as SQL and Tag
- Docker images for isolated testing and cloud isolated clusters
- Feature-rich administrative dashboard for configuration, metrics and monitoring
- Authentication and authorization
- Free open source connectors, for both sources and sinks
- Lightweight real-time computing
Quick Start
This paragraph guides you through steps of installing RocketMQ in different ways. For local development and testing, only one instance will be created for each component.
Run RocketMQ locally
RocketMQ runs on all major operating systems and requires only a Java JDK version 8 or higher to be installed.
To check, run java -version:
$ java -version
java version "1.8.0_121"
For Windows users, click here to download the 5.5.0 RocketMQ binary release,
unpack it to your local disk, such as D:\rocketmq.
For macOS and Linux users, execute following commands:
# Download release from the Apache mirror
$ wget https://dist.apache.org/repos/dist/release/rocketmq/5.5.0/rocketmq-all-5.5.0-bin-release.zip
# Unpack the release
$ unzip rocketmq-all-5.5.0-bin-release.zip
Prepare a terminal and change to the extracted bin directory:
$ cd rocketmq-all-5.5.0-bin-release/bin
1) Start NameServer
NameServer will be listening at 0.0.0.0:9876, make sure that the port is not used by others on the local machine, and then do as follows.
For macOS and Linux users:
### start Name Server
$ nohup sh mqnamesrv &
### check whether Name Server is successfully started
$ tail -f ~/logs/rocketmqlogs/namesrv.log
The Name Server boot success...
For Windows users, you need to set environment variables first:
- From the desktop, right click the Computer icon.
- Choose Properties from the context menu.
- Click the Advanced system settings link.
- Click Environment Variables.
- Add Environment
ROCKETMQ_HOME="D:\rocketmq".
Then change directory to rocketmq, type and run:
$ mqnamesrv.cmd
The Name Server boot success...
2) Start Broker
For macOS and Linux users:
### start Broker
$ nohup sh mqbroker -n localhost:9876 &
### check whether Broker is successfully started, eg: Broker's IP is 192.168.1.2, Broker's name is broker-a
$ tail -f ~/logs/rocketmqlogs/broker.log
The broker[broker-a, 192.168.1.2:10911] boot success...
For Windows users:
$ mqbroker.cmd -n localhost:9876
The broker[broker-a, 192.168.1.2:10911] boot success...
Run RocketMQ in Docker
You can run RocketMQ on your own machine within Docker containers,
host network will be used to expose listening port in the container.
1) Start NameServer
$ docker run -it --net=host apache/rocketmq ./mqnamesrv
2) Start Broker
$ docker run -it --net=host --mount type=bind,source=/tmp/store,target=/home/rocketmq/store apache/rocketmq ./mqbroker -n localhost:9876
Run RocketMQ in Kubernetes
You can also run a RocketMQ cluster within a Kubernetes cluster using RocketMQ Operator.
Before your operations, make sure that kubectl and related kubeconfig file installed on your machine.
1) Install CRDs
### install CRDs
$ git clone https://github.com/apache/rocketmq-operator
$ cd rocketmq-operator && make deploy
### check whether CRDs are successfully installed
$ kubectl get crd | grep rocketmq.apache.org
brokers.rocketmq.apache.org 2022-05-12T09:23:18Z
consoles.rocketmq.apache.org 2022-05-12T09:23:19Z
nameservices.rocketmq.apache.org 2022-05-12T09:23:18Z
topictransfers.rocketmq.apache.org 2022-05-12T09:23:19Z
### check whether operator is running
$ kubectl get pods | grep rocketmq-operator
rocketmq-operator-6f65c77c49-8hwmj 1/1 Running 0 93s
2) Create Cluster Instance
### create RocketMQ cluster resource
$ cd example && kubectl create -f rocketmq_v1alpha1_rocketmq_cluster.yaml
### check whether cluster resources are running
$ kubectl get sts
NAME READY AGE
broker-0-master 1/1 107m
broker-0-replica-1 1/1 107m
name-service 1/1 107m
Apache RocketMQ Community
- RocketMQ Streams: A lightweight stream computing engine based on Apache RocketMQ.
- RocketMQ Flink: The Apache RocketMQ connector of Apache Flink that supports source and sink connector in data stream and Table.
- RocketMQ APIs: RocketMQ protobuf protocol.
- RocketMQ Clients: gRPC/protobuf-based RocketMQ clients.
- RocketMQ Remoting-based Clients
- RocketMQ Spring: A project which helps developers quickly integrate Apache RocketMQ with Spring Boot.
- RocketMQ Exporter: An Apache RocketMQ exporter for Prometheus.
- RocketMQ Operator: Providing a way to run an Apache RocketMQ cluster on Kubernetes.
- RocketMQ Docker: The Git repo of the Docker Image for Apache RocketMQ.
- RocketMQ Dashboard: Operation and maintenance console of Apache RocketMQ.
- RocketMQ Connect: A tool for scalably and reliably streaming data between Apache RocketMQ and other systems.
- RocketMQ MQTT: A new MQTT protocol architecture model, based on which Apache RocketMQ can better support messages from terminals such as IoT devices and Mobile APP.
- RocketMQ EventBridge: EventBridge makes it easier to build an event-driven application.
- RocketMQ Incubating Community Projects: Incubator community projects of Apache RocketMQ, including logappender, rocketmq-ansible, rocketmq-beats-integration, rocketmq-cloudevents-binding, etc.
- RocketMQ Site: The repository for Apache RocketMQ website.
- RocketMQ E2E: A project for testing Apache RocketMQ, including end-to-end, performance, compatibility tests.
Learn it & Contact us
- Mailing Lists: https://rocketmq.apache.org/about/contact/
- Home: https://rocketmq.apache.org
- Docs: https://rocketmq.apache.org/docs/quick-start/
- Issues: https://github.com/apache/rocketmq/issues
- Rips: https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal
- Ask: https://stackoverflow.com/questions/tagged/rocketmq
Contributing
We always welcome new contributions, whether for trivial cleanups, big new features or other material rewards, more details see here.
License
Apache License, Version 2.0 Copyright (C) Apache Software Foundation
Export Control Notice
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included cryptographic software:
This software uses Apache Commons Crypto (https://commons.apache.org/proper/commons-crypto/) to support authentication, and encryption and decryption of data sent across the network between services.