GitHub user kpvt001 added a comment to the discussion: 是否支持4.x的rocketmq？
是需要通过proxy去访问4.x的rmq吗？文档里似乎并没有对此有介绍https://rocketmq.apache.org/zh/docs/
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/517#discussioncomment-5901551
This is an automatically sent email for
GitHub user aaron-ai added a comment to the discussion: 是否支持4.x的rocketmq？
Support of 4.x is not contained in the plan of community as proxy was
introduced in RocketMQ 5.x
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/517#discussioncomment-5900555
This is an
GitHub user pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点
谢谢您的答复，之后我又想到了一个方法，我发现在brokerController中存在changeToMaster和changeToSlave这两个函数，但并没有暴露出Java
Api提供使用，因此我在AdminBrokerProcessor中增加了如下的函数：
```java
private RemotingCommand updateBrokerRole(ChannelHandlerContext ctx,
GitHub user RongtongJin added a comment to the discussion: rocketmq 将从节点切换成主节点
> 我搭建了rocketmq的两主两从结构，如果brokerA的主节点挂了，能否通过修改brokerA的从节点的配置来将其切换为主节点？我尝试执行了如下2条命令，在dashboard上看是切换成功了，且生产者和消费者都没有出现问题，但不清楚是否还有缺陷:
>
> ```
> sh mqadmin updateBrokerConfig -k brokerId -v 0 -n nameSrvAddr -b brokerAddr
>
GitHub user RongtongJin added a comment to the discussion:
org.apache.rocketmq.util.cache doesn't look like it's being used
Hi @socutes , IMO, we can clean it.
GitHub link:
https://github.com/apache/rocketmq/discussions/6743#discussioncomment-5895321
This is an automatically sent email
GitHub user RongtongJin added a comment to the discussion: Further automate the
management of GitHub Issues and PRs
+1
GitHub link:
https://github.com/apache/rocketmq/discussions/6710#discussioncomment-5870107
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user chenzlalvin added a comment to the discussion: does the
rocketmq-client-java client support broadcast mode consumption messages in
rocketmq 5.0？
Yes, we will provide atomic API interfaces to facilitate the implementation of
one-to-N consumption scenarios, but there may not be
GitHub user weihubeats edited a comment on the discussion: rocketmq broker
keeps printing the following error: schedule CQ offset invalid. offset=62857,
cqMinOffset=0, cqMaxOffset=0, queueId=2
The command sh bin/mqadmin getSyncStateSet finds the node **NotInSyncReplica**.
Checking the sync
GitHub user weihubeats edited a comment on the discussion: rocketmq broker
keeps printing the following error: schedule CQ offset invalid. offset=62857,
cqMinOffset=0, cqMaxOffset=0, queueId=2
The command sh bin/mqadmin getSyncStateSet finds the node **NotInSyncReplica**.
Checking the sync
GitHub user pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点
我使用的rocketmq是4.9.1版本，暂时不考虑使用dledger方式
GitHub link:
https://github.com/apache/rocketmq/discussions/6721#discussioncomment-5844454
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user weihubeats edited a comment on the discussion: rocketmq broker
keeps printing the following error: schedule CQ offset invalid. offset=62857,
cqMinOffset=0, cqMaxOffset=0, queueId=2
The command sh bin/mqadmin getSyncStateSet finds the node **NotInSyncReplica**.
Checking the sync
GitHub user weihubeats added a comment to the discussion: rocketmq broker keeps
printing the following error: schedule CQ offset invalid. offset=62857,
cqMinOffset=0, cqMaxOffset=0, queueId=2
The command sh bin/mqadmin getSyncStateSet finds the node NotInSyncReplica.
Checking the sync log has
GitHub user echooymxq added a comment to the discussion:
ExamineConsumeStats这个API返回数据的问题
可以用正则表达式取每一对{"brokerName":"broker-a","queueId":7,"topic":"evidence-sync-cloud"}:{"brokerOffset":0,"consumerOffset":0,"lastTimestamp":0}这样的数据，然后单独反序列化具体每一对数据。
GitHub link:
GitHub user echooymxq added a comment to the discussion:
延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
Broker应该是没有进行校验，如果是使用5.x，那么在Proxy层会进行主题消息类型的校验。
GitHub link:
https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5837358
This is an automatically sent email for
GitHub user fuyou001 added a comment to the discussion:
延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
技术上，因历史原因，当前并没有做强制限制。延迟可以发普通消息、普通消息也可以发延迟消息。
但从运维角度，建议不要混用，避免给运维带来额外的成本。
GitHub link:
https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5836285
This is an automatically sent email
GitHub user lukaszwawrzyk added a comment to the discussion: Introduce Bazel
Steward - a tool for keeping dependencies up to date in Bazel
@ShadowySpirits Ok, it seems that the major problem is that bots may not push
commits to the repository. But what about dependabot that you seem to be
GitHub user yijieyu added a comment to the discussion: CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER
okkk
GitHub link:
https://github.com/apache/rocketmq/discussions/6432#discussioncomment-5835918
This is an automatically sent email for
GitHub user quattro-abc added a comment to the discussion: CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER
> @quattro-abc How to solve it
>
> this is conf
>
> brokerClusterName = Cluster brokerName = rocket01 brokerId = -1 brokerRole =
> ASYNC_MASTER
GitHub user wushimang1 added a comment to the discussion:
延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
我试过了，发送到普通主题也是一样能定时消费的，我看文档写的是3.x和4.x不强制校验，可以混用，但是我实测5.x也可以混用，不知道为什么
GitHub link:
https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5834902
This is an automatically sent email
GitHub user joeCarf added a comment to the discussion:
延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
个人理解，欢迎指正～
GitHub link:
https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5834872
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an
GitHub user joeCarf added a comment to the discussion:
延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
我理解延迟消息只有被写到延迟主题中才会发挥作用。由于延迟消息的实现原理是延迟主题下的消息定时重新投递，所以如果发送到普通主题的话，应该与普通消息无异。
GitHub link:
https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5834870
This is an automatically sent
GitHub user Stevenzall edited a discussion: 关于Topic顺序的疑惑
我们可以在创建一个Topic的时候设置一个topic是否有序的属性，但是这个属性并没有实际的作用。
https://github.com/apache/rocketmq/blob/34b20950c5de28e48560cf282fa83ee67eb9b130/common/src/main/java/org/apache/rocketmq/common/TopicConfig.java#L185-L192
GitHub user Stevenzall edited a discussion: 关于Topic顺序的疑惑
我们可以在创建一个Topic的时候设置一个topic是否有序的属性，但是这个属性并没有实际的作用。
https://github.com/apache/rocketmq/blob/34b20950c5de28e48560cf282fa83ee67eb9b130/common/src/main/java/org/apache/rocketmq/common/TopicConfig.java#L185-L192
GitHub user fuyou001 added a comment to the discussion:
生产者先于消费者启动，并在消费者启动之前投递了一些消息，消费者启动后为啥不能消费那些已投递但未消费的消息？
此问题解决办法：重置消息位点，重新开始消费。
后续规避办法：建议先启动订阅方。
GitHub link:
https://github.com/apache/rocketmq/discussions/6702#discussioncomment-5823751
This is an automatically sent email for
GitHub user superhx added a comment to the discussion:
生产者先于消费者启动，并在消费者启动之前投递了一些消息，消费者启动后为啥不能消费那些已投递但未消费的消息？
1. Consumer 默认是 CONSUME_FROM_LAST_OFFSET，因此在没有消费进度的时候会优先从末尾消费（RocketMQ 优化场景：若队列
minOffset 为0，且数据还在内存中，则会从 0 开始消费）。
2. 如果想从头开始消费，可以设置为 CONSUME_FROM_FIRST_OFFSET
GitHub link:
GitHub user ShadowySpirits added a comment to the discussion: Introduce Bazel
Steward - a tool for keeping dependencies up to date in Bazel
> Also, could you elaborate a bit on this ASF limit? Maybe something can be
> done about it?
@lukaszwawrzyk Thanks! Here is a reference: [ASF GitHub
GitHub user zuoHx580 edited a discussion:
生产者先于消费者启动，并在消费者启动之前投递了一些消息，消费者启动后为啥不能消费那些已投递但未消费的消息？
这种情况要怎么处理
GitHub link: https://github.com/apache/rocketmq/discussions/6702
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to:
GitHub user mxsm added a comment to the discussion: 5.1 版本controller 无法自动切换：
org.apache.rocketmq.client.exception.MQBrokerException: CODE: 2012 DESC: The
broker has not master, and this new registered broker can't not be elected as
master
epochFileCheckpoint
GitHub user PAYNE1Z added a comment to the discussion: 5.1 版本controller 无法自动切换：
org.apache.rocketmq.client.exception.MQBrokerException: CODE: 2012 DESC: The
broker has not master, and this new registered broker can't not be elected as
master
（1）下线主备Broker
GitHub user mxsm added a comment to the discussion: 5.1 版本controller 无法自动切换：
org.apache.rocketmq.client.exception.MQBrokerException: CODE: 2012 DESC: The
broker has not master, and this new registered broker can't not be elected as
master
能提供一下Controller相关的日志吗？
GitHub link:
GitHub user mxsm added a comment to the discussion: Will Rocketmq be maintained
after 4.9? Do we need to immediately switch to 5.0？
@luozongle
4.9.x will not introduce new features, only bug fixes and some performance
improvements. If you want to use new features such as:
1. Delayed
GitHub user RongtongJin added a comment to the discussion: Questions about try
catch
> Why does this code use two tries? Is there any optimization in it compared to
> using one try catch finally
>
>
GitHub user RongtongJin added a comment to the discussion: Will Rocketmq be
maintained after 4.9? Do we need to immediately switch to 5.0？
> Will Rocketmq be maintained after 4.9? Do we need to immediately switch to
> 5.0？
Before January 2024, RocketMQ 4.9.x will continue to be maintained,
GitHub user ShadowySpirits added a comment to the discussion: 请问该怎么解决 CODE: 2
DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER:
Thanks @imp2002, Great suggestion!
But I would like to recommend setting the `transientStorePoolSize` >= 2 to make
sure every CommitLog
GitHub user yijieyu added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER:
我试试
GitHub link:
https://github.com/apache/rocketmq/discussions/6656#discussioncomment-5730625
This is an automatically sent email for
GitHub user yijieyu added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER:
okkk
GitHub link:
https://github.com/apache/rocketmq/discussions/6656#discussioncomment-5730622
This is an automatically sent email for
GitHub user RongtongJin added a comment to the discussion: 请问该怎么解决 CODE: 2
DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER:
> broker_default.log 一直报system busy 服务器2核8G 版本5.1.0 用controller方式quick_start启动
>
> 这是配置文件
>
> brokerClusterName = Cluster brokerName = rocket01
GitHub user imp2002 added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER:
Seems cause by `Page Cache busy`, a
GitHub user yijieyu added a comment to the discussion: CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER
@quattro-abc How to solve it
this is conf
brokerClusterName = Cluster
brokerName = rocket01
brokerId = -1
brokerRole = ASYNC_MASTER
GitHub user jangwally added a comment to the discussion: 启动报错Expected the
service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
namesrv、broker 、proxy 三个组件都启动了吗？你这个情况应该是没有启动proxy
GitHub link:
https://github.com/apache/rocketmq/discussions/6238#discussioncomment-5707393
GitHub user drpmma added a comment to the discussion: 希望mqAdmin支持通过proxy
连接进行性能测试
close for duplication #6620
GitHub link:
https://github.com/apache/rocketmq/discussions/6638#discussioncomment-5703222
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user drpmma added a comment to the discussion: The Admin Tool can only
be executed in the pod, and I think it would be more reasonable to integrate
relevant functions into the proxy
Related discussion https://github.com/apache/rocketmq/issues/6603
There's no plan to support admin
GitHub user drpmma added a comment to the discussion: 希望mqAdmin支持通过proxy
连接进行性能测试
There's no plan to support admin interface in proxy for now. Please use
nameserver as access endpoint instead.
GitHub link:
https://github.com/apache/rocketmq/discussions/6638#discussioncomment-5703217
GitHub user drpmma added a comment to the discussion: 希望mqAdmin支持通过proxy
连接进行性能测试
Related discussion #6603
GitHub link:
https://github.com/apache/rocketmq/discussions/6638#discussioncomment-5703210
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please
GitHub user zuoHx580 edited a comment on the discussion: slave节点没有同步master
> 似乎epochCheckpoint中的数据与commitLog中的数据无法对齐，是否有手动删除过相关文件呢？
>
> 建议下线清理epochFileCheckpoint和epochFileCheckpoint.bak后重启
有删过，就是因为没法同步，所以删过一次
刚刚又试了一遍，还是不行，slave的机子也没有生成epochFileCheckpoint
然后我把slave ~/store下的文件全删了，再重启，就可以同步了
GitHub user zuoHx580 edited a comment on the discussion: slave节点没有同步master
> 似乎epochCheckpoint中的数据与commitLog中的数据无法对齐，是否有手动删除过相关文件呢？
>
> 建议下线清理epochFileCheckpoint和epochFileCheckpoint.bak后重启
有删过，就是因为没法同步，所以删过一次
刚刚又试了一遍，还是不行，slave的机子也没有生成epochFileCheckpoint
GitHub link:
GitHub user zuoHx580 added a comment to the discussion: slave节点没有同步master
> 似乎epochCheckpoint中的数据与commitLog中的数据无法对齐，是否有手动删除过相关文件呢？
>
> 建议下线清理epochFileCheckpoint和epochFileCheckpoint.bak后重启
有删过，就是因为没法同步，所以删过一次
GitHub link:
GitHub user RongtongJin added a comment to the discussion: slave节点没有同步master
似乎epochCheckpoint中的数据与commitLog中的数据无法对齐，是否有手动删除过相关文件呢？
建议下线清理epochFileCheckpoint和epochFileCheckpoint.bak后重启
GitHub link:
https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668144
This is an
GitHub user zuoHx580 added a comment to the discussion: slave节点没有同步master
> 主的store.log有信息吗？另外用的版本是？
这是主的store.log，版本为5.1.0
GitHub link:
GitHub user zuoHx580 added a comment to the discussion: 自动主从切换部署不能选出master
> > > Comment options
> > > cleanBrokerData 这个命令是哪个工具的，可以发个完整的吗
>
> mqadmin工具的，最新develop分支命名为cleanBrokerMetadata
好的，非常感谢
GitHub link:
https://github.com/apache/rocketmq/discussions/6354#discussioncomment-5668073
GitHub user RongtongJin added a comment to the discussion: slave节点没有同步master
主的store.log有信息吗？另外用的版本是？
GitHub link:
https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668068
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send
GitHub user zuoHx580 edited a comment on the discussion: slave节点没有同步master
> > 
> >
> > 应该是slave没有和master对齐，如何手动对齐呢
>
> 看一下master和slave的store.log，日志应该有相关提示
GitHub user zuoHx580 added a comment to the discussion: slave节点没有同步master
> > 
> >
> > 应该是slave没有和master对齐，如何手动对齐呢
>
> 看一下master和slave的store.log，日志应该有相关提示
GitHub user RongtongJin added a comment to the discussion: 自动主从切换部署不能选出master
> > Comment options
> > cleanBrokerData 这个命令是哪个工具的，可以发个完整的吗
mqadmin工具的，最新develop分支命名为cleanBrokerMetadata
GitHub link:
https://github.com/apache/rocketmq/discussions/6354#discussioncomment-5668050
This is an
GitHub user RongtongJin added a comment to the discussion: slave节点没有同步master
> 
>
>
>
> 应该是slave没有和master对齐，如何手动对齐呢
看一下master和slave的store.log，日志应该有相关提示
GitHub link:
GitHub user zuoHx580 edited a discussion: slave节点没有同步master
应该是slave没有和master对齐，如何手动对齐呢
GitHub link: https://github.com/apache/rocketmq/discussions/6621
This is an
GitHub user zuoHx580 edited a discussion: slave节点没有同步master
应该是slave没有和master对齐，如何手动对齐呢
GitHub link: https://github.com/apache/rocketmq/discussions/6621
This is an
GitHub user zuoHx580 added a comment to the discussion: 自动主从切换部署不能选出master
> Comment options
cleanBrokerData 这个命令是哪个工具的，可以发个完整的吗
GitHub link:
https://github.com/apache/rocketmq/discussions/6354#discussioncomment-5658530
This is an automatically sent email for dev@rocketmq.apache.org.
GitHub user kejiancai added a comment to the discussion:
5.1.0版本dledger集群时，定时消息不生效
嗯，我也是怀疑可能是版本的问题，支持master-slave集群，目前是发现dledger集群的定时有问题
GitHub link:
https://github.com/apache/rocketmq/discussions/6617#discussioncomment-5658480
This is an automatically sent email for
GitHub user kejiancai added a comment to the discussion:
5.1.0版本dledger集群时，定时消息不生效
应该不是，我测试的时候，只加了10秒上去，而且不管是否出时间轮，在消息的MESSAGE
ID那边是肯定要能查询到的，关键是现在没查询到，topic也没有这条数据，之前没有用dledger集群部署的时候，定时消息也都是正常的，用了dledger才出现了这个问题
GitHub link:
GitHub user RongtongJin added a comment to the discussion:
5.1.0版本dledger集群时，定时消息不生效
有可能与该修复有关，5.1.0的版本中DLedgerCommitLog缺少实现方法。
https://github.com/apache/rocketmq/pull/5879
GitHub link:
https://github.com/apache/rocketmq/discussions/6617#discussioncomment-5657844
This is an
GitHub user zuoHx580 added a comment to the discussion: fail to switch master
and log said Update master address from 192.168.47.129:10911 to null
> @zuoHx580 是否还有其他日志，另外可以用getSyncStateSet命令查看下controller中的元数据情况？
解决问题了，原因时发现有个节点没配controller的地址
GitHub link:
GitHub user RongtongJin added a comment to the discussion: fail to switch
master and log said Update master address from 192.168.47.129:10911 to null
@zuoHx580 是否还有其他日志，另外可以用getSyncStateSet命令查看下controller中的元数据情况？
GitHub link:
GitHub user MrZbb added a comment to the discussion: 请教个广播模式下如何避免重复消费的问题
Thanks. Currently, I am using the PostConstruct method to query the local
offsets file of the machine instance during application startup and delete it
directly. This does ensure that each time the broadcast mode is
GitHub user zhiliatom added a comment to the discussion:
5.1.0版本dledger集群时，定时消息不生效
不好意思看错了，message.setDelayTimeMs(10);是填间隔时间。有一种可能是客户端时间和服务端不一致，实际还未出时间轮
GitHub link:
https://github.com/apache/rocketmq/discussions/6617#discussioncomment-5657666
This is an automatically sent email for
GitHub user kejiancai edited a comment on the discussion:
5.1.0版本dledger集群时，定时消息不生效
使用开源客户端，setDeliverTimeMs这个是填写的时间戳哦
GitHub link:
https://github.com/apache/rocketmq/discussions/6617#discussioncomment-5657466
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user kejiancai added a comment to the discussion:
5.1.0版本dledger集群时，定时消息不生效
setDeliverTimeMs这个是填写的时间戳哦
GitHub link:
https://github.com/apache/rocketmq/discussions/6617#discussioncomment-5657466
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user superhx added a comment to the discussion: 请教个广播模式下如何避免重复消费的问题
You could create Consumer with different instanceName, then the new Consumer
will consume from newest message.
Or you can create a PR, let broadcast consumer support always consumer from the
last
GitHub link:
GitHub user zhiliatom added a comment to the discussion:
5.1.0版本dledger集群时，定时消息不生效
setDeliverTimeMs(1681876800)这个api填毫秒数，不是时间戳
GitHub link:
https://github.com/apache/rocketmq/discussions/6617#discussioncomment-5656474
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user kejiancai edited a discussion: 5.1.0版本dledger集群时，定时消息不生效
关于5.1.0版本，在单机或者普通主从集群情况下，定时可用，当部署为dledger集群时，定时只能对立即发送的数据有效，如果定时时间非立即执行，返回状态成功，并返回msgId，但是实际查询不到该msgId数据。不知道是否有人碰到过此情况，如果是我操作问题，希望帮忙指出，如果是该版本自身问题，希望此问题有助于提供帮助。
举例：如当前时间为2023-04-19 11:37:00，需要发送一条定时时间在2023-04-19
GitHub user zuoHx580 edited a discussion: fail to switch master and log said
Update master address from 192.168.47.129:10911 to null
version: 5.1
jdk:1.8
enviroment:
and three
GitHub user zuoHx580 edited a discussion: fail to switch master and log said
Update master address from 192.168.47.129:10911 to null
version: 5.1
jdk:1.8
enviroment:
and three
GitHub user drpmma added a comment to the discussion: In the local mode of
RocketMQ 5, the pushconsumer for a FIFO queue experiences delays while
consuming.
Please provide more information about your client and your server environment.
GitHub link:
GitHub user echooymxq added a comment to the discussion: The proxy local mode?
Yeah, i misunderstood the local mode routing data, thank you.
GitHub link:
https://github.com/apache/rocketmq/discussions/6552#discussioncomment-5635742
This is an automatically sent email for
GitHub user drpmma added a comment to the discussion: The proxy local mode?
The escape concept is not necessary for local mode.
In local mode, the client is able to know who is MASTER just from the topic
route. And the client will only send or receive from master.
See the code below.
GitHub user drpmma edited a comment on the discussion: The proxy local mode?
The local mode represents that the connection between Proxy and Broker is a
local procedure call. So escaping the message to the remote broker is not
recommended.
As an alternative plan, the SLAVE broker should
GitHub user echooymxq edited a discussion: What's the traceContext in Clients?
As we know, the RocketMQ 4.x use message trace as observability. With RocketMQ
5.x, it use opentelemetry metric. But for some scenarios, we have no a
professional ops team, we just need the traditional and simple
GitHub user echooymxq edited a discussion: Why not implement the traceContext
in Clients?
As we know, the RocketMQ 4.x use message trace as observability. With RocketMQ
5.x, it use opentelemetry metric. But for some scenarios, we have no a
professional ops team, we just need the traditional
GitHub user aaron-ai added a comment to the discussion: What not implement the
traceContext in Clients?
In the future, we plan to make the interceptor hook available for users to
replace the 'message trace' counterpart in RocketMQ 4.x. However, 'message
trace' in 4.x is not available in 5.x
GitHub user jiakme added a comment to the discussion: single instance with
multi DefaultLitePullConsumer(use same topic and different tag) don't poll
message right
我测试了一下， 使用不同 consumer group 的情况, 消息消费还是有问题:
GitHub user RongtongJin added a comment to the discussion: single instance with
multi DefaultLitePullConsumer(use same topic and different tag) don't poll
message right
lite pull consumer和push consumer，需要保证订阅关系的一致
GitHub link:
GitHub user jiakme added a comment to the discussion: single instance with
multi DefaultLitePullConsumer(use same topic and different tag) don't poll
message right
rocketmq-dashboard:
GitHub user jiakme edited a comment on the discussion: single instance with
multi DefaultLitePullConsumer(use same topic and different tag) don't poll
message right
generate DefaultLitePullConsumer instance
```java
private void initRocketMQPushConsumer() throws MQClientException {
List
GitHub user jiakme edited a comment on the discussion: single instance with
multi DefaultLitePullConsumer(use same topic and different tag) don't poll
message right
```java
private void initRocketMQPushConsumer() throws MQClientException {
List pullConsumers = new ArrayList<>();
GitHub user jiakme added a comment to the discussion: single instance with
multi DefaultLitePullConsumer(use same topic and different tag) don't poll
message right
`private void initRocketMQPushConsumer() throws MQClientException {
List pullConsumers = new ArrayList<>();
GitHub user francisoliverlee added a comment to the discussion: add api
reporting producer runninginfo to broker as consumer did
> @francisoliverlee where can I get more details on it to start with ? I will
> appreciate any help/hint.
>
> Regards
any details， email me: 1026203...@qq.com,
GitHub user francisoliverlee added a comment to the discussion: add api
reporting producer runninginfo to broker as consumer did
consumers implements a method consumerRunningInfo() which will be called when
admin tool calls broker, broker calls every online-consumer's
consumerRunningInfo().
GitHub user francisoliverlee added a comment to the discussion: The proxy local
mode?
+1.
proxies should be stateless， as the RED LINE shows.
GitHub link:
GitHub user echooymxq added a comment to the discussion: The proxy local mode?
Yeah, But in the current implementation, it will not escape. In local mode, the
client doesn't actually know who is MASTER, because the topic route is
wrapped. And as your say, in production, we will deploying the
GitHub user drpmma added a comment to the discussion: The proxy local mode?
The local mode represents that the connection between Proxy and Broker is a
local procedure call. So escaping the message to the remote broker is
recommended.
As an alternative plan, the SLAVE broker should also
GitHub user echooymxq edited a discussion: The proxy local mode?
Proxy local mode has the ability of multi-protocol adaptation, with the
advantages of low latency and high throughput. But it has additional problems,
in local deployment mode, it becomes stateful. The client always need know
GitHub user Abhijeetmishr added a comment to the discussion: add api reporting
producer runninginfo to broker as consumer did
@francisoliverlee where can I get more details on it to start with ?
I will appreciate any help/hint.
Regards
GitHub link:
GitHub user aaron-ai edited a discussion: Migrate logging related artifact to
an independent apache repository.
The groupId currently used by the logging module in RocketMQ is not very
neutral, and some developers from the community have suggested that we move it
under the groupId of
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
1 - 100 of 43000 matches
Mail list logo
