| commit | ece4fff3f656b3d529b6ca4563524af2cd22706e | [log] [tgz] |
|---|---|---|
| author | Zhanhui Li <lizhanhui@gmail.com> | Wed Aug 24 11:15:01 2022 +0800 |
| committer | GitHub <noreply@github.com> | Wed Aug 24 11:15:01 2022 +0800 |
| tree | a6e9ad865a5c5c64e16ae3139d052b9edf55f15b | |
| parent | 3840c3d33e98160ddaa1b8014780a680873419f7 [diff] |
Bazel (#4877) * Make test portable to Windows * Fix label issues * Fix trailing separator issue * Fix java-io-tmpdir inconsistency
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:
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.
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 4.9.3 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://archive.apache.org/dist/rocketmq/4.9.3/rocketmq-all-4.9.3-bin-release.zip # Unpack the release $ unzip rocketmq-all-4.9.3-bin-release.zip
Prepare a terminal and change to the extracted bin directory:
$ cd rocketmq-4.9.3/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 set environment variables first:
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 bin/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.169.1.2:10911] boot success...
For Windows users:
$ mqbroker.cmd -n localhost:9876 The broker[broker-a, 192.169.1.2:10911] boot success...
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 source=/tmp/store,target=/home/rocketmq/store apache/rocketmq ./mqbroker -n localhost:9876
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 is 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 is 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
We always welcome new contributions, whether for trivial cleanups, big new features or other material rewards, more details see here.
Apache License, Version 2.0 Copyright (C) Apache Software Foundation
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.