-
Notifications
You must be signed in to change notification settings - Fork 178
quickstart
Beta版厨子3.0® edited this page Nov 15, 2016
·
1 revision
1.Setup Zookeeper Cluster
reference : https://zookeeper.apache.org/doc/r3.3.2/zookeeperAdmin.html#sc_zkMulitServerSetup
2.Download KiteQ released package (https://github.com/blackbeans/kiteq/releases)
3.Install KiteQ
-
Extract KiteQ-xxx-xxxx.tar.gz to your deploy path
-
modify conf/cluster.toml
#registry
[registry]
#dev mode
[registry.dev]
hosts=${dev zk hosts}
#hosts="etcd://http://localhost:2379"
#product mode
[registry.online]
hosts=${product zk hosts}
#kiteq clusters
[clusters]
[clusters.${clustername}]
env="online" #env=dev/online
topics=["demo-topic"]
dlqExecHour=2
deliveryFirst=false
logxml="/home/deploy/kiteq/log/log.xml"
db="file:///data/kiteq?cap=10000000&checkSeconds=10"
deliverySeconds=5
maxDeliverWorkers=8000
recoverSeconds=10
recievePermitsPerSecond=20000
- above configuration ,kiteq's cluster uses file storage and message data will be stored at "/data/kiteq"
4.Run the following command to start KiteQServer
${KiteQ_HOME}/kiteq -clusterName=${clustername} -configPath=${KiteQ_HOME}/conf/cluster.toml -pport=13801 -bind=:13800
5.See the KiteQ Log
${KiteQ_HOME}/logs/kiteq_server.log
[2016/11/15 17:39:39 CST] [INFO] KiteQServer|RemotionServer|START|SUCC|:13800
[2016/11/15 17:39:39 CST] [INFO] KiteQServer|PushQServer|SUCC|[trade]
[2016/11/15 17:39:39 CST] [INFO] KiteQServer|startDLQ|SUCC|2016-11-15 17:39:39.731004072 +0800 CST
[2016/11/15 17:39:39 CST] [INFO]
Remoting: read:0/0 write:0/0 dispatcher_go:0 connetions:0
KiteQ: deliver:0 deliver-go:0
KiteStore:
message-length:map[] writeChannel:0
...
Congratulation ~ KiteQServer is Started!