dsencheng opened a new pull request, #87:
URL: https://github.com/apache/rocketmq-docker/pull/87
fix maven 3.6.3 not found
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
GitHub user pxd98 edited a discussion: RocketMQ 在broker 重启时，
生产者显示消息发送超时，但该消息仍被mq接收
RocketMQ版本为4.9.1，生产者是同步发送，broker端为同步双写。在重启一个Broker主节点的时候发现在该节点刚重启完的时候出现了超时（sendDefaultImpl
call timeout），生产者的超时时间设置为3s，使用mqadmin
GitHub user pxd98 added a comment to the discussion: RocketMQ 在broker 重启时，
生产者显示消息发送超时，但该消息仍被mq接收
我把同步双写改成异步双写后就没有这个问题了，由于该消息在mq中存在，是不是因为主从同步超时，从而导致生产者有这个报错？谢谢解答。
GitHub link:
https://github.com/apache/rocketmq/discussions/7099#discussioncomment-6591587
This is an automatically sent
GitHub user onejimmyboy edited a comment on the discussion: 2m-noslave
模式，使用brokerIP开启了外网访问，但是每次收到2条相同消息，关闭一个master就只能收到一条。啥原因。。。我想收到1条啊
配置文件？
GitHub link:
https://github.com/apache/rocketmq/discussions/7020#discussioncomment-6591743
This is an automatically sent email for
GitHub user onejimmyboy added a comment to the discussion: 2m-noslave
模式，使用brokerIP开启了外网访问，但是每次收到2条相同消息，关闭一个master就只能收到一条。啥原因。。。我想收到1条啊
可以详细描述一下吗？包括配置文件？
GitHub link:
https://github.com/apache/rocketmq/discussions/7020#discussioncomment-6591743
This is an automatically sent email for
GitHub user pxd98 edited a discussion: RocketMQ 在broker 重启时，
生产者显示消息发送超时，但该消息仍被mq接收
RocketMQ版本为4.9.1，生产者是同步发送，broker端为同步双写。在重启一个Broker主节点的时候发现在该节点刚重启完的时候出现了超时（sendDefaultImpl
call timeout），生产者的超时时间设置为3s，使用mqadmin
GitHub user sujiangliu added a comment to the discussion: Start RocketMQ on M1
failed
I modified the code in the file of CommitLog. java， and it takes effect.
`
pageSize = 10; // LibC.INSTANCE.getpagesize();
`
GitHub link:
GitHub user hsszlll added a comment to the discussion: Start RocketMQ on M1
failed
Yes, I run it on MacOS with M1, I start successfully when switch version from
5.1.3 to 5.1.0, will try this way turn off the borker switch related to cold
reading, thanks!
GitHub link:
GitHub user sujiangliu edited a comment on the discussion: Start RocketMQ on M1
failed
I modified the code in the file of CommitLog. java， and it takes effect. ths!
`
pageSize = 10; // LibC.INSTANCE.getpagesize();
`
GitHub link:
dependabot[bot] opened a new pull request, #4:
URL: https://github.com/apache/rocketmq-remoting/pull/4
Bumps [io.netty:netty-all](https://github.com/netty/netty) from 4.1.26.Final
to 4.1.42.Final.
Commits
dependabot[bot] opened a new pull request, #5:
URL: https://github.com/apache/rocketmq-remoting/pull/5
Bumps [junit:junit](https://github.com/junit-team/junit4) from 4.11 to
4.13.1.
Release notes
Sourced from https://github.com/junit-team/junit4/releases;>junit:junit's
releases.
dependabot[bot] opened a new pull request, #3:
URL: https://github.com/apache/rocketmq-remoting/pull/3
Bumps ch.qos.logback:logback-classic from 1.0.13 to 1.2.0.
[![Dependabot compatibility
dependabot[bot] opened a new pull request, #12:
URL: https://github.com/apache/rocketmq-ons-cpp/pull/12
Bumps [junit:junit](https://github.com/junit-team/junit4) from 4.11 to
4.13.1.
Release notes
Sourced from https://github.com/junit-team/junit4/releases;>junit:junit's
releases.
dependabot[bot] opened a new pull request, #20:
URL: https://github.com/apache/rocketmq-ons/pull/20
Bumps commons-beanutils:commons-beanutils from 1.9.3 to 1.9.4.
[![Dependabot compatibility
dependabot[bot] opened a new pull request, #21:
URL: https://github.com/apache/rocketmq-ons/pull/21
Bumps ch.qos.logback:logback-core from 1.1.11 to 1.2.9.
[![Dependabot compatibility
dependabot[bot] opened a new pull request, #22:
URL: https://github.com/apache/rocketmq-ons/pull/22
Bumps ch.qos.logback:logback-classic from 1.1.11 to 1.2.0.
[![Dependabot compatibility
dependabot[bot] opened a new pull request, #23:
URL: https://github.com/apache/rocketmq-ons/pull/23
Bumps ch.qos.logback:logback-classic from 1.1.11 to 1.2.0.
[![Dependabot compatibility
dependabot[bot] opened a new pull request, #24:
URL: https://github.com/apache/rocketmq-ons/pull/24
Bumps ch.qos.logback:logback-core from 1.1.11 to 1.2.9.
[![Dependabot compatibility
GitHub user onejimmyboy added a comment to the discussion:
5.0开启Proxy，采用Local模式时，需要把当前集群中所有的broker都开启proxy吗？
如果是DLedger
Controler模式，只在部分broker启用proxy，如果主从经历切换后，有可能会出现slave节点启动proxy，master节点没有proxy，这种情况下生产者还可以继续往master节点发消息吗？
GitHub link:
GitHub user shirenchuang edited a discussion: 消息轨迹希望支持更细粒度的场景
目前开启消息轨迹，一般都是生产者实例和消费者实例在构造函数的时候指定了，所以只要是通过他们发送和消费的消息都会发送轨迹消息；
但是这样会有一个问题，QPS大的情况下，消息轨迹的写入压力也会很大，因为相当于是将业务的消息 Double了一下；
但是大部分场景下，很多消息都不太关注消息轨迹，只有部分消息需要关注；
我觉得可以支持一下更细粒度的配置
在Producer和Consumer都开启了消息轨迹的前提下
新增一个配置，用来 Match
CyJaySong commented on issue #85:
URL: https://github.com/apache/rocketmq-docker/issues/85#issuecomment-1673457651
@LeeGode
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
CyJaySong closed issue #85: Unable to start Broker using Docker Compose
URL: https://github.com/apache/rocketmq-docker/issues/85
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
GitHub user tyfprof added a comment to the discussion: RocektMQ 5.x Proxy 单独
cluster 部署的情况下需要额外用 nginx 做负载均衡吗
你好！
感谢你的答复。
追加一个问题，如果单独部署 proxy cluster，它会自动负载均衡或者具备 HA 能力吗？
GitHub link:
https://github.com/apache/rocketmq/discussions/7141#discussioncomment-6697176
This is an
GitHub user RongtongJin added a comment to the discussion: Controller 嵌入
NameServer 部署方式，只有两个节点，停掉broker主节点，从节点不能变成主？
日志显示从节点无法连接到主节点，检查一下连通性
GitHub link:
https://github.com/apache/rocketmq/discussions/7136#discussioncomment-6698333
This is an automatically sent email for
GitHub user HFFZZZ added a comment to the discussion: 启动报错Expected the service
PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
我也是这个错误 头大了 控制台都是正常的 使用java客户端就连不上
GitHub link:
https://github.com/apache/rocketmq/discussions/6238#discussioncomment-6708428
This is an
GitHub user HFFZZZ added a comment to the discussion: 启动报错Expected the service
PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
没用 我也遇到此问题了 设置 30 200 1000都没用 还是出现这个错误
GitHub link:
https://github.com/apache/rocketmq/discussions/6238#discussioncomment-6708408
This
GitHub user onejimmyboy added a comment to the discussion: Rocketmq Dashboard
查看消息详情异常。
rocketmq-dashboard1.0.0版本依赖的rocketmq-tools的版本是4.9.0的，没有引入最新的5.1.3。rocketmq-dashboard年都没怎么更新了
GitHub link:
https://github.com/apache/rocketmq/discussions/7108#discussioncomment-6636055
This is an
GitHub user ShadowySpirits added a comment to the discussion:
macOs启动broker报下面的错，启动mqnamesrv不报错。
This problem was introduced in RIP-62 Cold read control.
GitHub user ShadowySpirits added a comment to the discussion: Rocketmq
5.x版本的消息发送的同步问题。
同步发送消息的情况下，消息存储在 broker 上即返回给生产者响应，不会等待消费者消费
GitHub link:
https://github.com/apache/rocketmq/discussions/7107#discussioncomment-6644318
This is an automatically sent email for
GitHub user RongtongJin added a comment to the discussion:
macOs启动broker报下面的错，启动mqnamesrv不报错。
Fix in #7014
GitHub link:
https://github.com/apache/rocketmq/discussions/7119#discussioncomment-6650194
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please
CyJaySong commented on issue #85:
URL: https://github.com/apache/rocketmq-docker/issues/85#issuecomment-1667511489
没呢
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
fujian-zfj opened a new issue, #921:
URL: https://github.com/apache/rocketmq-externals/issues/921
The issue tracker is **ONLY** used for bug report and feature request.
**FEATURE REQUEST**
We will introduce kv(rocksdb) storage to solve the possible Full GC caused
by large
GitHub user tyfprof edited a discussion: RocektMQ 5.x Proxy 单独 cluster
部署的情况下需要额外用 nginx 做负载均衡吗
RocketMQ5.x 单独 cluster 部署的情况下需要额外用 nginx 做负载均衡吗? 谢谢！
GitHub link: https://github.com/apache/rocketmq/discussions/7141
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user tyfprof edited a discussion: RocektMQ 5.x Proxy 单独 cluster
部署的情况下需要额外用 nginx 做负载均衡吗
RocketMQ5.x 需要额外用 nginx 做负载均衡吗? 谢谢！
GitHub link: https://github.com/apache/rocketmq/discussions/7141
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please
lollipopjin commented on PR #922:
URL:
https://github.com/apache/rocketmq-externals/pull/922#issuecomment-1671150484
Please add NOTICE and LICENSE file, and please add copyright to all the
added files.
--
This is an automated message from the Apache Git Service.
To respond to the
fujian-zfj opened a new pull request, #922:
URL: https://github.com/apache/rocketmq-externals/pull/922
Which Issue(s) This PR Fixes
Fixes #921
Brief Description
This proposal mainly optimizes and solves the existing perfermance problems
in the million-topic scenario from two
GitHub user RongtongJin added a comment to the discussion: Controller 嵌入
NameServer 部署方式，只有两个节点，停掉broker主节点，从节点不能变成主？
@onejimmyboy
看配置没有问题（如果希望不丢消息，建议allAckInSyncStateSet设置为true），可以用getSyncStateSet命令看下，主备是否同步，怀疑切换时备并不是完全同步主，导致没有正常切换。
GitHub link:
GitHub user onejimmyboy edited a comment on the discussion: Controller 嵌入
NameServer 部署方式，只有两个节点，停掉broker主节点，从节点不能变成主？
集群正常时执行命令行
集群正常的时候，应该就没有同步，是不是两节点的这种情形不支持啊
把allAckInSyncStateSet设置为了true结果一样
GitHub user francisoliverlee added a comment to the discussion: RocektMQ 5.x
Proxy 单独 cluster 部署的情况下需要额外用 nginx 做负载均衡吗
不行喔， 5.X的客户端从哪个proxy拉取的消息，需要ack给对应的proxy
GitHub link:
https://github.com/apache/rocketmq/discussions/7141#discussioncomment-6686904
This is an automatically sent email
GitHub user RongtongJin added a comment to the discussion: Controller 嵌入
NameServer 部署方式，只有两个节点，停掉broker主节点，从节点不能变成主？
看下store.log，查下为啥没有正常同步。两节点是支持的
GitHub link:
https://github.com/apache/rocketmq/discussions/7136#discussioncomment-6686864
This is an automatically sent email for
GitHub user onejimmyboy added a comment to the discussion: Controller 嵌入
NameServer 部署方式，只有两个节点，停掉broker主节点，从节点不能变成主？
集群正常时执行命令行
集群正常的时候，应该就没有同步，是不是两节点的这种情形不支持啊
GitHub link:
GitHub user onejimmyboy added a comment to the discussion: Controller 嵌入
NameServer 部署方式，只有两个节点，停掉broker主节点，从节点不能变成主？
从节点中日志信息
主节点日志信息
GitHub user HScarb added a comment to the discussion:
关于indexFile和consumeQueue的数据完整性问题
IndexFile和ConsumeQueue刷盘时都会将`StoreCheckpoint`刷盘，它用来记录当前这两个文件的刷盘进度。
重启时从上次保存的刷盘进度开始，通过CommitLog重新构建。
只要保证CommitLog完整，就可以构建出一模一样的IndexFile和ConsumeQueue
GitHub link:
GitHub user HScarb edited a comment on the discussion: [Bug] the queue's
messages, span too long, so do flow control
消费处理队列 ProcessQueue 中的数据堆积过多，超过阈值（默认为2000）。
消息拉取速度大于消费速度导致。
GitHub link:
https://github.com/apache/rocketmq/discussions/7133#discussioncomment-6690902
This is an
GitHub user HScarb added a comment to the discussion: [Bug] the queue's
messages, span too long, so do flow control
消费队列中的数据堆积过多，超过阈值（默认为2000）。
消息拉取速度大于消费速度导致。
GitHub link:
https://github.com/apache/rocketmq/discussions/7133#discussioncomment-6690902
This is an automatically sent email
GitHub user ijbuhv added a comment to the discussion:
关于indexFile和consumeQueue的数据完整性问题
GitHub user pxd98 edited a discussion: RocketMQ fastListenPort设置问题
RocketMQ
4.9.1的版本中是不是在broker.conf中设置了fastListenPort并没有用？就是10909这个vip端口，我看好像初始化时直接设为listenPort-2了，在代码里没找到将设置读入的地方。
GitHub link: https://github.com/apache/rocketmq/discussions/7158
This is an automatically sent email for
GitHub user AI1186780944 edited a discussion: Rocketmq 5.x版本的消息发送的同步问题。
服务器版本：rocketmq：5.1.3，
客户端版本：rocketmq-client-java：5.0.5，
服务运行模式：Local模式，
现象描述：
1、在使用同步发送消息的情况下，消费者不处理完消息，生产者没办法在send()方法中获取到MessageId的结果值。
2、基于第1条现象，在关闭消费者的情况下，消息又能正常的发送，并且无视消费者的存在与否。
问题：
GitHub user AI1186780944 edited a discussion: Rocketmq Dashboard 查看消息详情异常。
服务版本： rocketmq：5.1.3。
Dashboard版本：1.0.0。
服务运行模式：Local模式，开启proxy。
场景描述：
Rocketmq
Dashboard的namesrvAddr指向是rocketmq-namesrv地址（无法指向proxy的remoting或者grpc端口，会发生错误）。
问题：
当客户端生产者在使用proxy代理的情况下，发送的消息。想通过Rocketmq
GitHub user ShadowySpirits added a comment to the discussion: Duplicates Topics
Confirmation
At present, the MQAdmin cli tools only offer the updateTopic command. However,
we could improve this by dividing it into two separate commands: createTopic
and updateTopic. The former allow users to
GitHub user haiyanghan closed a discussion: 关于broker的brokerClusterName
这个属性我的理解是用来区分brokerName,
相同的brokerName在不同的brokerClusterName下，可以同时存在broekrId=0的broker
不知道我的理解是否有偏差
GitHub link:
GitHub user elfwalk reopened a discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
**环境：**
1. 2台虚机：hostA 194.0.11.118、hostB 194.0.11.119
2. docker镜像：apache/rocketmq:5.1.1
3. hostA部署: nameserver+controller 3容器 + 2broker
```
#ControllerGroupRaftGroup
#ControllerLeaderId
GitHub user elfwalk closed a discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
**环境：**
1. 2台虚机：hostA 194.0.11.118、hostB 194.0.11.119
2. docker镜像：apache/rocketmq:5.1.1
3. hostA部署: nameserver+controller 3容器 + 2broker
```
#ControllerGroupRaftGroup
#ControllerLeaderId n1
GitHub user elfwalk deleted a comment on the discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
Thanks!
GitHub link:
https://github.com/apache/rocketmq/discussions/6914#discussioncomment-6208240
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user elfwalk added a comment to the discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
Thanks!
GitHub link:
https://github.com/apache/rocketmq/discussions/6914#discussioncomment-6208240
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user elfwalk closed a discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
**环境：**
1. 2台虚机：hostA 194.0.11.118、hostB 194.0.11.119
2. docker镜像：apache/rocketmq:5.1.1
3. hostA部署: nameserver+controller 3容器 + 2broker
```
#ControllerGroupRaftGroup
#ControllerLeaderId n1
GitHub user elfwalk added a comment to the discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
感谢，确实是这个问题，配置brokerIP2后正常。
参数名 | 默认值 | 说明
-- | -- | --
brokerIP1 | 网卡的 InetAddress | 当前 broker 监听的 IP
brokerIP2 | 跟 brokerIP1 一样 | 存在主从 broker 时，如果在 broker 主节点上配置了 brokerIP2
属性，broker
GitHub user RongtongJin closed the discussion with a comment:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
> 升级了服务端的话，客户端是否需要对应呢？
GitHub link:
https://github.com/apache/rocketmq/discussions/6921#discussioncomment-6236312
This is an automatically sent email for dev@rocketmq.apache.org.
GitHub user kecongcong closed a discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
rocketmq4.9.6是否有对应的springboot-starter版本？如果没有的话是否有rocketmq5.1.1版本对应的springboot-starter版本
因为这几个版本存在问题
GitHub user RongtongJin added a comment to the discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
是可以兼容的
GitHub link:
https://github.com/apache/rocketmq/discussions/6921#discussioncomment-6236310
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user kecongcong edited a comment on the discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
升级了服务端的话，客户端是否需要对应呢？
是可以兼容的
GitHub link:
https://github.com/apache/rocketmq/discussions/6921#discussioncomment-6228502
This is an automatically sent email for
GitHub user kecongcong edited a comment on the discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
升级了服务端的话，客户端是否需要对应呢？
GitHub link:
https://github.com/apache/rocketmq/discussions/6921#discussioncomment-6228502
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user Dr-wgy edited a discussion: rocketmq 5.1.1 mvn clean compile
rocketmq-all-5.1.2-source-release mvn -Prelease-all -DskipTests
-Dspotbugs.skip=true clean install -U
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective
GitHub user Dr-wgy added a comment to the discussion: rocketmq 5.1.1 mvn clean
compile
mvn -v
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
GitHub link:
https://github.com/apache/rocketmq/discussions/6924#discussioncomment-6236985
This is an automatically sent email
GitHub user Dr-wgy edited a discussion: rocketmq 5.1.1 mvn clean compile
rocketmq-all-5.1.2-source-release mvn -Prelease-all -DskipTests
-Dspotbugs.skip=true clean install -U
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective
GitHub user Dr-wgy edited a discussion: rocketmq 5.1.1 mvn clean compile
Could not resolve dependencies for project
org.apache.rocketmq:rocketmq-common:jar:5.1.0: Failed to collect dependencies
at io.grpc:grpc-netty-shaded:jar:1.50.0 -> io.grpc:grpc-core:jar:[1.50.0]: No
versions available
GitHub user Dr-wgy deleted a comment on the discussion: rocketmq 5.1.1 mvn
clean compile
mvn -v
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
GitHub link:
https://github.com/apache/rocketmq/discussions/6924#discussioncomment-6236985
This is an automatically sent email
GitHub user Dr-wgy reopened a discussion: rocketmq 5.1.1 mvn clean compile
Could not resolve dependencies for project
org.apache.rocketmq:rocketmq-common:jar:5.1.0: Failed to collect dependencies
at io.grpc:grpc-netty-shaded:jar:1.50.0 -> io.grpc:grpc-core:jar:[1.50.0]: No
versions
GitHub user Dr-wgy closed a discussion: rocketmq 5.1.1 mvn clean compile
Could not resolve dependencies for project
org.apache.rocketmq:rocketmq-common:jar:5.1.0: Failed to collect dependencies
at io.grpc:grpc-netty-shaded:jar:1.50.0 -> io.grpc:grpc-core:jar:[1.50.0]: No
versions available
GitHub user Dr-wgy closed a discussion: rocketmq 5.1.1 mvn clean compile
rocketmq-all-5.1.2-source-release mvn -Prelease-all -DskipTests
-Dspotbugs.skip=true clean install -U
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective
GitHub user fade-away added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
这个问题有解决吗？我也遇到相同的问题了
通过这个命令从节点拿到的消息数和主节点的不一致
GitHub link:
https://github.com/apache/rocketmq/discussions/6218#discussioncomment-6193295
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user elfwalk edited a discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
**环境：**
1. 2台虚机：hostA 194.0.11.118、hostB 194.0.11.119
2. docker镜像：apache/rocketmq:5.1.1
3. hostA部署: nameserver+controller 3容器 + 2broker
```
#ControllerGroupRaftGroup
#ControllerLeaderId n1
GitHub user elfwalk edited a discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
**环境：**
1. 2台虚机：hostA 194.0.11.118、hostB 194.0.11.119
2. docker镜像：apache/rocketmq:5.1.1
3. hostA部署: nameserver+controller 3容器 + 2broker
```
#ControllerGroupRaftGroup
#ControllerLeaderId n1
GitHub user elfwalk edited a discussion:
docker部署5.1.1版本的controller模式，跨主机的broker主从不同步，也无法自动切换
**环境：**
1. 2台虚机：hostA 194.0.11.118、hostB 194.0.11.119
2. docker镜像：apache/rocketmq:5.1.1
3. hostA部署: nameserver+controller 3容器 + 2broker
```
#ControllerGroupRaftGroup
#ControllerLeaderId n1
GitHub user elfwalk added a comment to the discussion: m1 下 docker 使用rockerMq
可以尝试自己打包镜像或者虚拟机安装
打包镜像参考：https://github.com/apache/rocketmq-docker/tree/master/image-build
GitHub link:
https://github.com/apache/rocketmq/discussions/6911#discussioncomment-6194866
This is an automatically
GitHub user RongtongJin edited a discussion: Do not upgrade to Apache RocketMQ
5.1.2 if you use automatic master-slave switching mode
Due to the merging of other pull requests, the initialization order of the
replicaManager was adjusted, which caused the automatic master-slave switching
mode
caigy commented on issue #77:
URL: https://github.com/apache/rocketmq-docker/issues/77#issuecomment-1606082675
The RocketMQ docker images are under optimization, where the base image will
be changed to multi-arch one. After that, we may support official ARM64 image.
--
This is an
drivebyer commented on issue #77:
URL: https://github.com/apache/rocketmq-docker/issues/77#issuecomment-1606093239
> The RocketMQ docker images are under optimization, where the base image
will be changed to multi-arch one. After that, we may support official ARM64
image.
Nice! Any
GitHub user pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点
谢谢您的答复，之后我又想到了一个方法，我发现在brokerController中存在changeToMaster和changeToSlave这两个函数，但并没有暴露出Java
Api提供使用，因此我在AdminBrokerProcessor中增加了如下的函数：
```java
private RemotingCommand updateBrokerRole(ChannelHandlerContext ctx,
GitHub user pxd98 edited a comment on the discussion: rocketmq 将从节点切换成主节点
已废弃
GitHub link:
https://github.com/apache/rocketmq/discussions/6721#discussioncomment-5899974
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to:
GitHub user pxd98 deleted a comment on the discussion: rocketmq 将从节点切换成主节点
已废弃
GitHub link:
https://github.com/apache/rocketmq/discussions/6721#discussioncomment-5899974
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to:
GitHub user kecongcong edited a discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
rocketmq4.9.6是否有对应的springboot-starter版本？如果没有的话是否有rocketmq5.1.1版本对应的springboot-starter版本
因为这几个版本存在问题
GitHub user humkum edited a discussion: 【LMQ & Multi-tags】Can we use LMQ to
support multi-tags?
As we know, one RocketMQ message doesn't support to set multi tags.
We found that using LMQ to generate consume indexes for one message can satisfy
this requirement, like follows:
drivebyer opened a new issue, #77:
URL: https://github.com/apache/rocketmq-docker/issues/77
There is third-party arm image, such as
https://github.com/apache/rocketmq-docker/issues/55. But still looking forward
to official suport.
--
This is an automated message from the Apache Git
GitHub user kecongcong edited a discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
rocketmq4.9.6是否有对应的springboot-starter版本？如果没有的话是否有rocketmq5.1.1版本对应的springboot-starter版本
因为这几个版本存在问题
GitHub user kecongcong edited a discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
rocketmq4.9.6是否有对应的springboot-starter版本？如果没有的话是否有rocketmq5.1.1版本对应的springboot-starter版本
因为这几个版本存在问题
GitHub user humkum edited a discussion: 【LMQ & Multi-tags】Can we use LMQ to
support multi-tags?
As we know, one RocketMQ message doesn't support to set multi tags.
We found that using LMQ to generate consume indexes for one message can satisfy
this requirement, like follows:
GitHub user humkum edited a discussion: 【LMQ & Multi-tags】Can we use LMQ to
support multi-tags?
As we know, one RocketMQ message doesn't support to set multi tags.
We found that using LMQ to generate consume indexes for one message can satisfy
this requirement, like follows:
GitHub user RongtongJin added a comment to the discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
> rocketmq4.9.6是否有对应的springboot-starter版本？如果没有的话是否有rocketmq5.1.1版本对应的springboot-starter版本
>
> 因为这几个版本存在问题
>
>
GitHub user kecongcong added a comment to the discussion:
【漏洞】rocketmq4.9.6是否有对应的springboot-starter版本
升级了服务端的话，客户端是否需要对应呢？
GitHub link:
https://github.com/apache/rocketmq/discussions/6921#discussioncomment-6228502
This is an automatically sent email for dev@rocketmq.apache.org.
To
caigy opened a new issue, #79:
URL: https://github.com/apache/rocketmq-docker/issues/79
As what has been done in #74, an entry-point script will be added in CentOS
image of RocketMQ.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
RongtongJin merged PR #80:
URL: https://github.com/apache/rocketmq-docker/pull/80
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
RongtongJin closed issue #79: Add an entry point for RocketMQ docker image
(CentOS version)
URL: https://github.com/apache/rocketmq-docker/issues/79
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
GitHub user mxsm edited a comment on the discussion: 主从架构下消息是如何保证不重复消费的
消息的消费只会从Master进行消费， 但是当Master
宕机，在5.0版本下Controller模式的高可用模式会选举Slave作为master继续进行。而5.0之前的版本会从Slave继续进行消费，
并不会出现你上述说的一个请求了Master一个请求了Slave的情况。
GitHub user mxsm added a comment to the discussion: 主从架构下消息是如何保证不重复消费的
消息的消费只会从Master进行消费， 但是当Master
宕机，在5.0版本下Controller模式的高可用模式会选举Slave作为master继续进行。而5.0之前的版本会从Slave继续进行消费，
并不会出现你上述说的一个请求了Master一个请求了Slave的情况。
GitHub link:
caigy opened a new pull request, #80:
URL: https://github.com/apache/rocketmq-docker/pull/80
fix #79
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
GitHub user panwuji edited a discussion: 阻塞本地事务（线程睡眠模拟），事务消息回查未触发，线程重新活跃后提交事务报错
服务端：5.1.1
客户端：rocketmq-client-java（5.0.5）
参考官网demo：https://rocketmq.apache.org/zh/docs/featureBehavior/04transactionmessage
修改为
`private static boolean doLocalTransaction() {`
`try {`
`
GitHub user panwuji edited a discussion: 阻塞本地事务（线程睡眠模拟），事务消息回查未触发，线程重新活跃后提交事务报错
服务端：5.1.1
客户端：rocketmq-client-java（5.0.5）
参考官网demo：https://rocketmq.apache.org/zh/docs/featureBehavior/04transactionmessage
修改
`private static boolean doLocalTransaction() {
try {
GitHub user shach1990 closed a discussion: 大量事务消息出现反复回查的情况
**请教各位是否遇到过类似的问题，初步怀疑是否时因为 transientStorePoolEnable 为
true导致，但本地无法复现，但线上环境100%出现，有没有解决方案呢？**
### 背景
GitHub user shach1990 closed the discussion with a comment: 大量事务消息出现反复回查的情况
调整配置为`transientStorePoolEnable=false`，事务消息100%出现回查的情况就没有了。怀疑跟writeBuffer写入page
cache的时机有关。
GitHub link:
https://github.com/apache/rocketmq/discussions/6954#discussioncomment-6322153
This is an automatically
401 - 500 of 896 matches
Mail list logo
