Files

Sun-ZhenXing ece59b42bf Add environment configuration and documentation for various services

- Created .env.example files for Kafka, Kibana, KodBox, Kong, Langfuse, Logstash, n8n, Nginx, OceanBase, OpenCoze, RocketMQ, TiDB, and TiKV.
- Added README.md and README.zh.md files for OceanBase, RocketMQ, TiDB, and TiKV, detailing usage, configuration, and access instructions.
- Implemented docker-compose.yaml files for OceanBase, RocketMQ, TiDB, and TiKV, defining service configurations, health checks, and resource limits.
- Included broker.conf for RocketMQ to specify broker settings.
- Established a consistent timezone (UTC) across all services.
- Provided optional port overrides in .env.example files for flexibility in deployment.

2025-10-22 11:46:50 +08:00

2.2 KiB

Raw Blame History

RocketMQ

Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability.

Usage

docker compose up -d

Components

This setup includes:

NameServer: Manages broker routing information
Broker: Stores and delivers messages
Dashboard: Web UI for monitoring and management

Configuration

The broker configuration is in broker.conf. Key settings:

brokerClusterName: Cluster name
brokerName: Broker name
autoCreateTopicEnable: Auto-create topics (enabled by default)
flushDiskType: Disk flush strategy (ASYNC_FLUSH for better performance)

Ports

9876: NameServer port
10909: Broker listening port (fastRemotingServer)
10911: Broker port (remoting server)
10912: Broker HA port
8080: Dashboard Web UI

Access

Dashboard

Access the RocketMQ Dashboard at: http://localhost:8080

Command Line Tools

Execute admin commands:

# List clusters
docker compose exec broker mqadmin clusterList -n namesrv:9876

# List topics
docker compose exec broker mqadmin topicList -n namesrv:9876

# Create topic
docker compose exec broker mqadmin updateTopic -n namesrv:9876 -c DefaultCluster -t TestTopic

# Query message
docker compose exec broker mqadmin queryMsgById -n namesrv:9876 -i <messageId>

Example: Send and Receive Messages

# Send messages
docker compose exec broker sh /home/rocketmq/rocketmq/bin/tools.sh org.apache.rocketmq.example.quickstart.Producer

# Consume messages
docker compose exec broker sh /home/rocketmq/rocketmq/bin/tools.sh org.apache.rocketmq.example.quickstart.Consumer

Client Connection

Configure your RocketMQ client to connect to:

NameServer: localhost:9876

Notes

This is a single-master setup suitable for development
For production, use a multi-master or multi-master-multi-slave setup
Adjust JVM heap sizes in JAVA_OPT_EXT based on your needs
Data is persisted in named volumes

2.2 KiB Raw Blame History