docker部署nsq

最新推荐文章于 2023-06-08 17:22:29 发布
最新推荐文章于 2023-06-08 17:22:29 发布
阅读量1.6k 收藏
点赞数
分类专栏： nsq 文章标签： nsq
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Nick_666/article/details/80904051
版权 
[root@localhost ~]# docker pull nsqio/nsq
[root@localhost ~]# docker run -d --name lookupd -p 4160:4160 -p 4161:4161 nsqio/nsq /nsqlookupd
2fa8d6d17df28454d57dc52a3c7f207dc6feb1c4c873b473432a10b8ef241d54
[root@localhost ~]# 
[root@localhost ~]# docker run -d --name nsqd -p 4150:4150 -p 4151:4151 nsqio/nsq /nsqd --broadcast-address=192.168.174.130 --lookupd-tcp-address=192.168.174.130:4160
73ee118badae2166a8e3165a1aa02555e4efbf0c5e0d797ba8b0e43eac77180d
[root@localhost ~]# 
[root@localhost ~]# docker run -d --name nsqadmin -p 4171:4171 nsqio/nsq /nsqadmin  --lookupd-http-address=192.168.174.130:4161
898e85a4b65ff171543bb600cd122173e3b6916047d9ab3dbf1d745ddb4d796f

#关闭防火墙
[root@localhost ~]# yum install iptables
[root@localhost ~]# iptables -I INPUT -p tcp --dport 4150:4151 -j ACCEPT
[root@localhost ~]# iptables -I INPUT -p tcp --dport 4160:4161 -j ACCEPT
[root@localhost ~]# iptables -I INPUT -p tcp --dport 4171 -j ACCEPT

永久关闭
[root@localhost ~]# vim /etc/sysconfig/iptables-config
文件中添加
-A INPUT -p tcp -m state --state NEW -m tcp --dport 4150:4151 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 4160:4161 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 4171 -j ACCEPT

这里写图片描述

多个节点部署：
在另外一台机器上

[root@localhost ~]# docker pull nsqio/nsq
[root@localhost ~]# docker run --name nsqd -p 4150:4150 -p 4151:4151 nsqio/nsq /nsqd --broadcast-address=192.168.174.131 --lookupd-tcp-address=192.168.174.130:4160

这里写图片描述

往节点发送主题消息

package main

import (
    "github.com/nsqio/go-nsq"
    "log"
)

func main() {
    config := nsq.NewConfig()

    //nsqProducer, _ := nsq.NewProducer("192.168.174.130:4150", config)
    nsqProducer, _ := nsq.NewProducer("192.168.174.131:4150", config)

    err := nsqProducer.Ping()
    if err != nil {
        log.Fatal("ping error")
        return
    }
    defer nsqProducer.Stop()
    topicName := "publish_test"
    count := 4
    for i := 0; i < count; i++ {
         //err = nsqProducer.DeferredPublish(topicName, time.Second * 10, []byte("hello world"))
        err = nsqProducer.Publish(topicName, []byte("publish test"))
        if err != nil {
            log.Fatal("error")
        }
    }
}

这里写图片描述

package main

import (
    "github.com/nsqio/go-nsq"
    "log"
)

func main() {
    config := nsq.NewConfig()

    nsqProducer, _ := nsq.NewProducer("192.168.174.130:4150", config)
    //nsqProducer, _ := nsq.NewProducer("192.168.174.131:4150", config)

    err := nsqProducer.Ping()
    if err != nil {
        log.Fatal("ping error")
        return
    }
    defer nsqProducer.Stop()
    topicName := "publish_test_2"
    count := 4
    for i := 0; i < count; i++ {
        err = nsqProducer.Publish(topicName, []byte("publish test 2"))
        if err != nil {
            log.Fatal("error")
        }
    }
}

这里写图片描述

不过现在还都没有接收的channel
这里写图片描述

package main

import (
    "fmt"
    "github.com/nsqio/go-nsq"
    "os"
    "os/signal"
    "strconv"
    "sync"
    "time"
)

type ConsumerHandle struct {
    consumer *nsq.Consumer
    msgGood  int
}

var consumers = make([]*nsq.Consumer, 0)
var mux = &sync.Mutex{}

func main() {
    topicName := "publish_test"
    count := 5
    for i := 0; i < count; i++ {
        time.Sleep(time.Second)
        go readMessage(topicName, i)
    }

    cleanup := make(chan os.Signal)
    signal.Notify(cleanup, os.Interrupt)
    fmt.Println("server is running....")
    exit := make(chan bool)
    go func() {

        select {
        case <-cleanup:
            fmt.Println("Receive an interrupt signal, stoping service ...")
            for _, ele := range consumers {
                ele.StopChan <- 1
                ele.Stop()
            }
            exit <- true
        }
    }()
    <-exit
    fmt.Println("stop server....")
}

func (h *ConsumerHandle) HandleMessage(message *nsq.Message) error {
    msg := string(message.Body) + "  " + strconv.Itoa(h.msgGood)
    fmt.Println(msg)
    return nil
}

func readMessage(topicName string, count int) {
    defer func() {
        if err := recover(); err != nil {
            fmt.Println("error: ", err)
        }
    }()

    config := nsq.NewConfig()
    config.MaxInFlight = 10000
    config.MaxBackoffDuration = time.Minute

    consumer, _ := nsq.NewConsumer(topicName, "ch"+strconv.Itoa(count), config)

    consumerHandle := &ConsumerHandle{consumer: consumer, msgGood: count}
    consumer.AddHandler(consumerHandle)

    err := consumer.ConnectToNSQLookupd("192.168.174.130:4161")
    //err := consumer.ConnectToNSQDs([]string{"192.168.174.130:4161"})
    //err := consumer.ConnectToNSQD("192.168.174.130:4150")
    //err := consumer.ConnectToNSQD("192.168.174.130:4151")
    if err != nil {
        fmt.Println("ConnectToNSQLookupd error")
    }
    mux.Lock()
    consumers = append(consumers, consumer)
    mux.Unlock()
    <-consumer.StopChan
    fmt.Println("stop....")
}

运行程序

2018/07/04 09:51:47 INF    1 [publish_test/ch0] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 09:51:47 INF    1 [publish_test/ch0] (192.168.174.131:4150) connecting to nsqd
publish test  0
publish test  0
publish test  0
publish test  0
2018/07/04 09:51:48 INF    2 [publish_test/ch1] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 09:51:48 INF    2 [publish_test/ch1] (192.168.174.131:4150) connecting to nsqd
2018/07/04 09:51:49 INF    3 [publish_test/ch2] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 09:51:49 INF    3 [publish_test/ch2] (192.168.174.131:4150) connecting to nsqd
2018/07/04 09:51:50 INF    4 [publish_test/ch3] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 09:51:50 INF    4 [publish_test/ch3] (192.168.174.131:4150) connecting to nsqd
server is running....
2018/07/04 09:51:51 INF    5 [publish_test/ch4] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 09:51:51 INF    5 [publish_test/ch4] (192.168.174.131:4150) connecting to nsqd
2018/07/04 09:52:53 INF    1 [publish_test/ch0] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 09:52:54 INF    3 [publish_test/ch2] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 09:52:57 INF    2 [publish_test/ch1] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test

主题出现了接收的channel
这里写图片描述

上面4个channel已经就绪了，再发消息，4个channel都能接收到，我们重新发消息

2018/07/04 10:12:53 INF    1 [publish_test/ch0] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:12:53 INF    1 [publish_test/ch0] (192.168.174.131:4150) connecting to nsqd
2018/07/04 10:12:53 WRN    1 [publish_test/ch0] (192.168.174.131:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:53 INF    1 [publish_test/ch0] (192.168.174.130:4150) connecting to nsqd
2018/07/04 10:12:53 WRN    1 [publish_test/ch0] (192.168.174.130:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:54 INF    2 [publish_test/ch1] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:12:54 INF    2 [publish_test/ch1] (192.168.174.131:4150) connecting to nsqd
2018/07/04 10:12:54 WRN    2 [publish_test/ch1] (192.168.174.131:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:54 INF    2 [publish_test/ch1] (192.168.174.130:4150) connecting to nsqd
2018/07/04 10:12:54 WRN    2 [publish_test/ch1] (192.168.174.130:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:55 INF    3 [publish_test/ch2] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:12:55 INF    3 [publish_test/ch2] (192.168.174.131:4150) connecting to nsqd
2018/07/04 10:12:55 WRN    3 [publish_test/ch2] (192.168.174.131:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:55 INF    3 [publish_test/ch2] (192.168.174.130:4150) connecting to nsqd
2018/07/04 10:12:55 WRN    3 [publish_test/ch2] (192.168.174.130:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:56 INF    4 [publish_test/ch3] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:12:56 INF    4 [publish_test/ch3] (192.168.174.131:4150) connecting to nsqd
2018/07/04 10:12:56 WRN    4 [publish_test/ch3] (192.168.174.131:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:56 INF    4 [publish_test/ch3] (192.168.174.130:4150) connecting to nsqd
2018/07/04 10:12:56 WRN    4 [publish_test/ch3] (192.168.174.130:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
server is running....
2018/07/04 10:12:57 INF    5 [publish_test/ch4] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:12:57 INF    5 [publish_test/ch4] (192.168.174.131:4150) connecting to nsqd
2018/07/04 10:12:57 WRN    5 [publish_test/ch4] (192.168.174.131:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
2018/07/04 10:12:57 INF    5 [publish_test/ch4] (192.168.174.130:4150) connecting to nsqd
2018/07/04 10:12:57 WRN    5 [publish_test/ch4] (192.168.174.130:4150) max RDY count 2500 < consumer max in flight 10000, truncation possible
publish test  1
publish test  2
publish test  3
publish test  4
publish test  0
publish test  0
publish test  0
publish test  0
publish test  1
publish test  1
publish test  1
publish test  2
publish test  2
publish test  2
publish test  3
publish test  3
publish test  3
publish test  4
publish test  4
publish test  4
2018/07/04 10:13:56 INF    3 [publish_test/ch2] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:14:05 INF    1 [publish_test/ch0] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:14:05 INF    4 [publish_test/ch3] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:14:06 INF    2 [publish_test/ch1] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
2018/07/04 10:14:08 INF    5 [publish_test/ch4] querying nsqlookupd http://192.168.174.130:4161/lookup?topic=publish_test
Receive an interrupt signal, stoping service ...
stop....
stop....
stop....
stop....
stop....
stop server....
2018/07/04 10:14:09 INF    1 [publish_test/ch0] stopping...
2018/07/04 10:14:09 INF    2 [publish_test/ch1] stopping...
2018/07/04 10:14:09 INF    3 [publish_test/ch2] stopping...
2018/07/04 10:14:09 INF    4 [publish_test/ch3] stopping...
2018/07/04 10:14:09 INF    5 [publish_test/ch4] stopping...

Process finished with exit code 0
左耳朵猫
关注
专栏目录
docker-compose安装nsq集群
qq2806000829的博客
10-26 506
docker-compose安装nsq集群 因公司项目用到了nsq，自己在家捣鼓了几个小时翻阅文档在本地搭了个集群,直接上docker-compose.yml version: '3' services: nsqlookupd: restart: always image: nsqio/nsq command: /nsqlookupd --broadcast-address=192.168.2.3 ports: - "4160:4160" -
docker-compose部署nsq集群
Simon的博客
07-06 1045
两台机器上分别创建docker-compose.yml 然后执行docker-compose up -d version: '2' services: nsqlookupd: image: nsqio/nsq command: /nsqlookupd ports: ...
docker-compose 容器部署 nsq
07-30
docker-compose 容器部署 nsq 配置文件
docker 部署 nsq
weixin_30306905的博客
09-18 532
这篇文章主要介绍如何使用docker部署 nsq 组件 环境准备 本文基于一台 ubuntu 虚拟机试验 docker 安装 docker 安装方式 使用docker version 命令检查 docker 是否安装成功 docker-compose 安装 apt-get install docker-compose nsq docker 部署 nsq 主要有三个组件: nsqlook...
Docker docker-compose 部署 NSQ
王佳宇的个人博客
06-30 4616
Docker docker-compose 部署 NSQ 学习NSQ队列的原因主要是想了解一下内部源码，学习一下框架级的channel使用，目前来说使用最多的消息队列还是kafka以及rabbitmq system:centos docker下载这里就不说了，随随便便网上都能搜到一大堆 因为还需要docker-compose并且是第一次下载所以记录一下 [root@localhos...
GO_NSQ_docker部署
非晓为骁的博客
03-22 263
消息队列 nsq
docker 安装 nsq
chen_peng7的博客
06-08 1464
docker 安装 nsq
docker-compose 怎么部署nsq
最新发布
03-21
下面是使用Docker Compose部署NSQ的步骤： 1. 创建一个名为docker-compose.yml的文件，并在其中定义NSQ的服务。以下是一个示例配置： ```yaml version: '3' services: nsqlookupd: image: nsqio/nsq:v1.2.0 ...
nsq消息队列 Java_nsq消息队列部署几种方案(单机)
weixin_42405371的博客
03-05 291
NSQ是一个实时的分布式消息平台。它的设计目标是为在多台计算机上运行的松散服务提供一个现代化的基础设施骨架。NSQ是由3个进程组成的：nsqd 是一个接收、排队、然后转发消息到客户端的进程。nsqlookupd管理拓扑信息并提供最终一致性的发现服务。nsqadmin用于实时查看集群的统计数据(并且执行各种各样的管理任务)。1 源码部署cd /usr/local/nsq-1.1.0.linux-am...
Docker搭建NSQ实时分布式消息集群
weixin_34216196的博客
06-09 136
NSQ是一个基于Go语言的分布式实时消息平台，它基于MIT开源协议发布，代码托管在GitHub。NSQ可用于大规模系统中的实时消息服务，并且每天能够处理数亿级别的消息，其设计目标是为在分布式环境下运行的去中心化服务提供一个强大的基础架构。 NSQ具有分布式、去中心化的拓扑结构，该结构具有无单点故障、故障容错、高可用性以及能够保证消息的可靠传递的特征。NSQ非常容易配置和部署，且具有最大的灵活性，支...
在mac下使用docker-compose部署nsq(乌班图也适用）
weixin_38707040的博客
10-16 501
文章目录nsq官网docker-compose的问题解决方案第一步，使用docker-compose 部署nsq第二步，打开admin，修改host nsq官网docker-compose的问题 nsq的安装，命令行方式安装nsq的，nsq官网已经有了，使用起来也没啥毛病，但是看了下官网提供的docker-compose方式部署的使用起来却有些问题， 官网提供的docker-compose.yml如下 version: '3' services: nsqlookupd: image: nsqio
NSQ-docker安装部署
u011913691的博客
09-02 1197
官网链接 官网地址 安装运行 下载nsq docker镜像 docker pull nsqio/nsq 运行docker容器lookupd 运行：docker inspect -f '{{ .NetworkSettings.IPAddress }}' lookupd 得到容器ip: 172.17.0.12 运行docker容器nsqd docker run -d --name ns...
docker-compose.yml nsq
云满笔记
01-06 566
这里写目录标题1. docker-compose.yml nsq1.1. 说明1.3. tree1.4. docker-compose.yml1.5. restart_nsq.sh 1. docker-compose.yml nsq 1.1. 说明 nsq 需要启动至少 3 个端: nsqlookupd: nsqlookupd 管理拓扑信息, 客户端根据特定的 topic 查询 nsqlookupd 来发现 nsqd 生产者及 nsqd 广播 topic 和 channel 信息。 nsqd(可多个。一般
NSQ基于windows和docker的部署
逍遥壮士
06-03 378
NSQ是什么？简介 NSQ 是一个实时分布式消息平台，旨在大规模运行，每天处理数十亿条消息。它提倡没有单点故障的分布式和分散式拓扑结构，实现容错和高可用性，同时保证可靠的消息传递。请...
Docker部属Nsq集群
词语大杂烩
10-25 646
为了容灾需要对nsqd多机器部属，有了Docker后，快速扩还是很方便的。 　　部署完后我会用go和c#写一些代码方便大家学习。   　　准备工作： 　　》两台服务器：192.168.0.49; 192.168.0.105. 　　》需要在两台机器上安装好Docker 　　》两台机器上镜像的拉取  docker pull nsqio/nsq 　　我
docker启动nsq-server
完颜振江
09-27 381
docker启动nsq-server
docker深入1-使用docker运行nsq
weixin_33895695的博客
03-26 293
docker深入1-使用docker运行nsq一、在10.0.200.21上测试 首先pull一个nsq的镜像 dockerpullnsqio/nsq 二、启动容器 1）运行docker容器lookupd [root@svr200-21docker]#dockerrun-d--namelookupd-p4160:4160-p4161:4161nsq...
通过docker实现nsq高可用
死磕音视频
10-13 626
准备工作 准备2台机器 192.168.1.21 A机器 192.168.1.22 B机器 概念 nsqlookupd 相当于服务发现，我们不同的机器上的nsqd需要注册到服务发现，并带上nsqd的ip地址，端口默认使用的4150，通过这样实现负载和高可用 #启动 注意nsqd的端口最好保持默认端口 一台机器上启动nsqlookupd，和nsqd version: '3' services: nsqlookupd: container_name: nsqlookupd image:
Mac安装MySQL、Redis、MongoDB、NSQ、Docker
haoranhaoshi的博客
09-17 282
Mac上， 安装MySQL：https://www.jianshu.com/p/199492627ccc 安装Redis：https://blog.csdn.net/realize_dream/article/details/106227622 安装MongoDB：https://www.runoob.com/mongodb/mongodb-osx-install.html
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值