[GitHub] [rocketmq-clients] kpvt001 added a comment to the discussion: 是否支持4.x的rocketmq？
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq-clients] aaron-ai added a comment to the discussion: 是否支持4.x的rocketmq？
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 automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点
GitHub user pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点
谢谢您的答复，之后我又想到了一个方法，我发现在brokerController中存在changeToMaster和changeToSlave这两个函数，但并没有暴露出Java
Api提供使用，因此我在AdminBrokerProcessor中增加了如下的函数：
```java
private RemotingCommand updateBrokerRole(ChannelHandlerContext ctx,
RemotingCommand request) throws RemotingCommandException {
final RemotingCommand response =
RemotingCommand.createResponseCommand(null);
final UpdateBrokerRoleRequestHeader requestHeader =
(UpdateBrokerRoleRequestHeader)
request.decodeCommandCustomHeader(UpdateBrokerRoleRequestHeader.class);
try {
switch (requestHeader.getBrokerRole()){
case "ASYNC_MASTER": {//change to async master, brokerId is 0
log.info("Change brokerRole to {}, ignore
brokerId",requestHeader.getBrokerRole());
this.brokerController.changeToMaster(BrokerRole.ASYNC_MASTER);
break;
}
case "SYNC_MASTER": {//change to sync master, brokerId is 0
log.info("Change brokerRole to {}, ignore
brokerId",requestHeader.getBrokerRole());
this.brokerController.changeToMaster(BrokerRole.SYNC_MASTER);
break;
}
case "SLAVE":{//change to slave, needs brokerId
log.info("Change brokerRole to {}, brokerId:
{}",requestHeader.getBrokerRole(),requestHeader.getBrokerId());
this.brokerController.changeToSlave(requestHeader.getBrokerId());
break;
}
default:{
log.warn("Unknown brokerRole {},
skipped",requestHeader.getBrokerRole());
response.setCode(ResponseCode.NO_SUCH_BROKERROLE);
return response;
}
}
response.setCode(ResponseCode.SUCCESS);
return response;
} catch (Exception e) {
log.error("Failed to update broker role", e);
}
return null;
}
```
并在MQClientAPIImpl中增加了如下函数：
```java
public void updateBrokerRole(final String addr, final String brokerRole, final
int brokerId, final long timeoutMillis)
throws RemotingConnectException, RemotingSendRequestException,
RemotingTimeoutException, InterruptedException,
MQBrokerException {
UpdateBrokerRoleRequestHeader requestHeader=new
UpdateBrokerRoleRequestHeader();
requestHeader.setBrokerRole(brokerRole);
requestHeader.setBrokerId(brokerId);
RemotingCommand request =
RemotingCommand.createRequestCommand(RequestCode.UPDATE_BROKER_ROLE,requestHeader);
RemotingCommand response =
this.remotingClient.invokeSync(addr,request,timeoutMillis);
assert response != null;
switch (response.getCode()) {
case ResponseCode.SUCCESS: {
return;
}
default:
break;
}
throw new MQBrokerException(response.getCode(), response.getRemark(),
addr);
}
```
使得我可以通过这样的方式来改变一个broker的节点属性
```java
public static void main(String[] args) throws MQClientException,
RemotingConnectException, RemotingSendRequestException,
RemotingTimeoutException, MQBrokerException, UnsupportedEncodingException,
InterruptedException {
DefaultMQAdminExt defaultMQAdminExt=new DefaultMQAdminExt();
defaultMQAdminExt.setNamesrvAddr("127.0.0.1:9876");
defaultMQAdminExt.start();
defaultMQAdminExt.updateBrokerRole("2.0.0.1:15432","ASYNC_MASTER",0);
defaultMQAdminExt.shutdown();
}
```
我也一并在DefaultMQAdminExt、DefaultMQAdminExtImpl、RequestCode等文件中增加了相关代码，并且在测试环境中使用这些进行测试，暂时未发现存在问题。
那在broker的主节点宕机且无法恢复的情况下，可否使用这种方式进行手动的主从切换？谢谢。
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: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: rocketmq 将从节点切换成主节点
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 > sh mqadmin updateBrokerConfig -k brokerRole -v ASYNC_MASTER -n nameSrvAddr > -b brokerAddr > ``` > > 在生产环境中能否直接这样使用，或者有什么建议？谢谢。 这样的切换方式在数据一致性上会有很大的风险。不建议这样使用。 GitHub link: https://github.com/apache/rocketmq/discussions/6721#discussioncomment-5895326 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: org.apache.rocketmq.util.cache doesn't look like it's being used
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 for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: Further automate the management of GitHub Issues and PRs
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 unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] chenzlalvin added a comment to the discussion: does the rocketmq-client-java client support broadcast mode consumption messages in rocketmq 5.0？
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 broadcast mode parameters in version 4.x. cc to @aaron-ai GitHub link: https://github.com/apache/rocketmq/discussions/6725#discussioncomment-5855009 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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
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 log has the following log printed normally ``` Update slave topic config from master Update slave consumer offset from master Update slave delay offset from master Update slave Message Request Mode ``` View dashboard explicitly for this broker online https://user-images.githubusercontent.com/42484192/236983945-a18730f6-7554-417f-8f4e-4eaf41d4357c.png;> Checking the store log reveals the following error: ``` ERROR AutoSwitchHAClient - master pushed offset not equal the max phy offset in slave, SLAVE: 4224100337368 MASTER: 4224662794263 ERROR AutoSwitchHAClient - Process read result failed ``` I guess it may be the master-slave synchronization commitlog inconsistency problem, I deleted all the storage files of the slave, and then restarted the broker, and I still found this error GitHub link: https://github.com/apache/rocketmq/discussions/6719#discussioncomment-5844314 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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
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 log has the following log printed normally ``` Update slave topic config from master Update slave consumer offset from master Update slave delay offset from master Update slave Message Request Mode ``` View dashboard explicitly for this broker online https://user-images.githubusercontent.com/42484192/236983945-a18730f6-7554-417f-8f4e-4eaf41d4357c.png;> Checking the store log reveals the following error: ``` ERROR AutoSwitchHAClient - master pushed offset not equal the max phy offset in slave, SLAVE: 4224100337368 MASTER: 4224662794263 ERROR AutoSwitchHAClient - Process read result failed ``` GitHub link: https://github.com/apache/rocketmq/discussions/6719#discussioncomment-5844314 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点
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, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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
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 log has the following log printed normally ``` Update slave topic config from master Update slave consumer offset from master Update slave delay offset from master Update slave Message Request Mode ``` View dashboard explicitly for this broker online https://user-images.githubusercontent.com/42484192/236983945-a18730f6-7554-417f-8f4e-4eaf41d4357c.png;> GitHub link: https://github.com/apache/rocketmq/discussions/6719#discussioncomment-5844314 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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
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 the following log printed normally ``` Update slave topic config from master Update slave consumer offset from master Update slave delay offset from master Update slave Message Request Mode ``` View dashboard explicitly for this broker online https://user-images.githubusercontent.com/42484192/236983945-a18730f6-7554-417f-8f4e-4eaf41d4357c.png;> GitHub link: https://github.com/apache/rocketmq/discussions/6719#discussioncomment-5844314 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: ExamineConsumeStats这个API返回数据的问题
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:
https://github.com/apache/rocketmq/discussions/6718#discussioncomment-5837780
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] fuyou001 added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
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 for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] lukaszwawrzyk added a comment to the discussion: Introduce Bazel Steward - a tool for keeping dependencies up to date in Bazel
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 using? What would be an acceptable workflow? How about running on a fork that opens PRs to the actual repo? Also there is an option to run bazel-steward manually from the CLI, so it would just create branches locally on behalf of the caller and these branches could be pushed. Please also let me know if you'd be interested in this approach. GitHub link: https://github.com/apache/rocketmq/discussions/6711#discussioncomment-5836273 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yijieyu added a comment to the discussion: CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] quattro-abc added a comment to the discussion: CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER
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 #flushDiskType=ASYNC_FLUSH deleteWhen = 04 fileReservedTime = 48 > enableControllerMode = true controllerAddr = > 10.203.1.115:9878;10.203.0.175:9878;10.203.1.50:9878 namesrvAddr = > 10.203.1.115:9876;10.203.0.175:9876;10.203.1.50:9876 > allAckInSyncStateSet=true listenPort=30911 > storePathRootDir=/data/rmqstore/rocket02/ > storePathCommitLog=/data/rmqstore/rocket02/commitlog > sendMessageThreadPoolNums=4 useReentrantLockWhenPutMessage=true > isEnableSlaveActingMaster=true > > autoCreateTopicEnable=false autoCreateSubscriptionGroup=false 发生这个问题的原因大致两个方面 1:磁盘空间不足; 2:磁盘IO超负荷; 我的这个问题主要是磁盘IO瓶颈导致的.在业务高峰期,你可以观察下服务器的读写情况. GitHub link: https://github.com/apache/rocketmq/discussions/6432#discussioncomment-5835866 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] wushimang1 added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
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 for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] joeCarf added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
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 email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] joeCarf added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊
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 email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Stevenzall edited a discussion: 关于Topic顺序的疑惑
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 https://github.com/apache/rocketmq/blob/34b20950c5de28e48560cf282fa83ee67eb9b130/client/src/main/java/org/apache/rocketmq/client/impl/producer/TopicPublishInfo.java#L33-L36 下面的这些也回答的模棱两可的 * [where is the isOrderTopic used?](https://github.com/apache/rocketmq/issues/4462) * [What is the real usefulness of TopicConfig#isOrder?](https://github.com/apache/rocketmq/issues/4614) 我翻看了从开源以来这个属性就一直存在，但是一直好像没有实际作用。 GitHub link: https://github.com/apache/rocketmq/discussions/6716 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Stevenzall edited a discussion: 关于Topic顺序的疑惑
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 https://github.com/apache/rocketmq/blob/34b20950c5de28e48560cf282fa83ee67eb9b130/client/src/main/java/org/apache/rocketmq/client/impl/producer/TopicPublishInfo.java#L33-L36 下面的这些也回答的模棱两可的 * [where is the isOrderTopic used?](https://github.com/apache/rocketmq/issues/4462) * [What is the real usefulness of TopicConfig#isOrder?](https://github.com/apache/rocketmq/issues/4614) 我翻看了从开源以来这个属性就一直存在，但是一直好像没有实际作用，想问一下，这块具体设计之初的目的，是未开源之前的历史包袱？为什么一直没有删除掉呢？ GitHub link: https://github.com/apache/rocketmq/discussions/6716 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] fuyou001 added a comment to the discussion: 生产者先于消费者启动，并在消费者启动之前投递了一些消息，消费者启动后为啥不能消费那些已投递但未消费的消息？
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] superhx added a comment to the discussion: 生产者先于消费者启动，并在消费者启动之前投递了一些消息，消费者启动后为啥不能消费那些已投递但未消费的消息？
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: https://github.com/apache/rocketmq/discussions/6702#discussioncomment-5823592 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] ShadowySpirits added a comment to the discussion: Introduce Bazel Steward - a tool for keeping dependencies up to date in Bazel
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 action policy](https://infra.apache.org/github-actions-policy.html) GitHub link: https://github.com/apache/rocketmq/discussions/6711#discussioncomment-5823278 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a discussion: 生产者先于消费者启动，并在消费者启动之前投递了一些消息，消费者启动后为啥不能消费那些已投递但未消费的消息？
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: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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 r
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 link: https://github.com/apache/rocketmq/discussions/6685#discussioncomment-5807152 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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 ne
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 （2）利用cleanBrokerData命令清除Controller中该组Broker元数据 （3）删除主备Broker下的文件～/store/epochFileCheckpoint和epochFileCheckpoint.bak （4）Broker重新上线（尽量保证旧的主备关系，先主后备上线） 参考 #6354 这个操作恢复了 可能是因为我更改过 epochFileCheckpoint 目录 GitHub link: https://github.com/apache/rocketmq/discussions/6685#discussioncomment-5800705 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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 r
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: https://github.com/apache/rocketmq/discussions/6685#discussioncomment-5792396 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm added a comment to the discussion: Will Rocketmq be maintained after 4.9? Do we need to immediately switch to 5.0？
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 messages at any time 2. Proxy mode 3. New high availability Controller mode And other new features, you need to upgrade to Rocketmq 5.0 or above. Of course, the basic functions of version 5.0 and 4.x are compatible. If you have new requirements or use peripheral ecosystem projects of Rocketmq, it is recommended to upgrade to 5.0. Some functions of the 5.0 upgrade process may not be compatible with version 4.x. Please refer to the official website documentation for specific upgrade steps. GitHub link: https://github.com/apache/rocketmq/discussions/6664#discussioncomment-5787277 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: Questions about try catch
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 > > src="https://user-images.githubusercontent.com/35722577/235298560-49000a6b-d9a9-49ca-a28d-a3d2c836a412.png;> Of course, welcome to optimize this part of the code GitHub link: https://github.com/apache/rocketmq/discussions/6667#discussioncomment-5761113 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: Will Rocketmq be maintained after 4.9? Do we need to immediately switch to 5.0？
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, but only for bug fixes and will not add new features. Please refer to https://rocketmq.apache.org/download. If you need some new features of RocketMQ 5.0, such as proxy, arbitrarily precise timing messages, automatic master-slave switching architecture, it is recommended that you upgrade to version 5.0. GitHub link: https://github.com/apache/rocketmq/discussions/6664#discussioncomment-5761108 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] ShadowySpirits added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER:
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 could borrow a write buffer. And maybe you want to know the trade-off for enabling transientStorePool: each buffer will occupy 1G memory by default, and increase the latency of flushing disk (setting flushDiskType=SYNC_FLUSH could be better). GitHub link: https://github.com/apache/rocketmq/discussions/6656#discussioncomment-5733598 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yijieyu added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER:
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yijieyu added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER:
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER:
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 brokerId = -1 brokerRole = > ASYNC_MASTER #flushDiskType=ASYNC_FLUSH deleteWhen = 04 fileReservedTime = 48 > enableControllerMode = true controllerAddr = > 10.203.1.115:9878;10.203.0.175:9878;10.203.1.50:9878 namesrvAddr = > 10.203.1.115:9876;10.203.0.175:9876;10.203.1.50:9876 > allAckInSyncStateSet=true listenPort=30911 > storePathRootDir=/data/rmqstore/rocket02/ > storePathCommitLog=/data/rmqstore/rocket02/commitlog > sendMessageThreadPoolNums=4 useReentrantLockWhenPutMessage=true > isEnableSlaveActingMaster=true > > autoCreateTopicEnable=false autoCreateSubscriptionGroup=false 2c8g在较大流量下可能确实会造成system busy。调大osPageCacheBusyTimeOutMills可能可以从表面上缓解该现象，但如果系统存在性能瓶颈，还是需要升级规格或扩容。此外，我发现配置文件中isEnableSlaveActingMaster参数和enableControllerMode同时为true，两种模式无法同时启动，建议关闭isEnableSlaveActingMaster参数。 GitHub link: https://github.com/apache/rocketmq/discussions/6656#discussioncomment-5730571 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] imp2002 added a comment to the discussion: 请问该怎么解决 CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER:
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 possible solution is to enable the `transientStorePoolEnable` and set the `transientStorePoolSize` realize read-write separation, relieve pressure on page cache. ```conf transientStorePoolEnable=true transientStorePoolSize=1 ``` GitHub link: https://github.com/apache/rocketmq/discussions/6656#discussioncomment-5730397 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yijieyu added a comment to the discussion: CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER
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 #flushDiskType=ASYNC_FLUSH deleteWhen = 04 fileReservedTime = 48 enableControllerMode = true controllerAddr = 10.203.1.115:9878;10.203.0.175:9878;10.203.1.50:9878 namesrvAddr = 10.203.1.115:9876;10.203.0.175:9876;10.203.1.50:9876 allAckInSyncStateSet=true listenPort=30911 storePathRootDir=/data/rmqstore/rocket02/ storePathCommitLog=/data/rmqstore/rocket02/commitlog sendMessageThreadPoolNums=4 useReentrantLockWhenPutMessage=true isEnableSlaveActingMaster=true autoCreateTopicEnable=false autoCreateSubscriptionGroup=false GitHub link: https://github.com/apache/rocketmq/discussions/6432#discussioncomment-5728377 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] jangwally added a comment to the discussion: 启动报错Expected the service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
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 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: 希望mqAdmin支持通过proxy 连接进行性能测试
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, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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
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 interface in proxy for now. Please use nameserver as access endpoint instead. GitHub link: https://github.com/apache/rocketmq/discussions/6620#discussioncomment-5703220 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: 希望mqAdmin支持通过proxy 连接进行性能测试
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 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: 希望mqAdmin支持通过proxy 连接进行性能测试
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 send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a comment on the discussion: slave节点没有同步master
GitHub user zuoHx580 edited a comment on the discussion: slave节点没有同步master > 似乎epochCheckpoint中的数据与commitLog中的数据无法对齐，是否有手动删除过相关文件呢？ > > 建议下线清理epochFileCheckpoint和epochFileCheckpoint.bak后重启 有删过，就是因为没法同步，所以删过一次 刚刚又试了一遍，还是不行，slave的机子也没有生成epochFileCheckpoint 然后我把slave ~/store下的文件全删了，再重启，就可以同步了 GitHub link: https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668249 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a comment on the discussion: slave节点没有同步master
GitHub user zuoHx580 edited a comment on the discussion: slave节点没有同步master > 似乎epochCheckpoint中的数据与commitLog中的数据无法对齐，是否有手动删除过相关文件呢？ > > 建议下线清理epochFileCheckpoint和epochFileCheckpoint.bak后重启 有删过，就是因为没法同步，所以删过一次 刚刚又试了一遍，还是不行，slave的机子也没有生成epochFileCheckpoint GitHub link: https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668249 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 added a comment to the discussion: slave节点没有同步master
GitHub user zuoHx580 added a comment to the discussion: slave节点没有同步master > 似乎epochCheckpoint中的数据与commitLog中的数据无法对齐，是否有手动删除过相关文件呢？ > > 建议下线清理epochFileCheckpoint和epochFileCheckpoint.bak后重启 有删过，就是因为没法同步，所以删过一次 GitHub link: https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668249 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: slave节点没有同步master
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 automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 added a comment to the discussion: slave节点没有同步master
GitHub user zuoHx580 added a comment to the discussion: slave节点没有同步master > 主的store.log有信息吗？另外用的版本是？ 这是主的store.log，版本为5.1.0  GitHub link: https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668090 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 added a comment to the discussion: 自动主从切换部署不能选出master
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 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: slave节点没有同步master
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 an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a comment on the discussion: slave节点没有同步master
GitHub user zuoHx580 edited a comment on the discussion: slave节点没有同步master > >  > > > > 应该是slave没有和master对齐，如何手动对齐呢 > > 看一下master和slave的store.log，日志应该有相关提示  同步异常 GitHub link: https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668053 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 added a comment to the discussion: slave节点没有同步master
GitHub user zuoHx580 added a comment to the discussion: slave节点没有同步master > >  > > > > 应该是slave没有和master对齐，如何手动对齐呢 > > 看一下master和slave的store.log，日志应该有相关提示  GitHub link: https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668053 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: 自动主从切换部署不能选出master
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 automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: slave节点没有同步master
GitHub user RongtongJin added a comment to the discussion: slave节点没有同步master >  > > > > 应该是slave没有和master对齐，如何手动对齐呢 看一下master和slave的store.log，日志应该有相关提示 GitHub link: https://github.com/apache/rocketmq/discussions/6621#discussioncomment-5668033 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a discussion: slave节点没有同步master
GitHub user zuoHx580 edited a discussion: slave节点没有同步master  应该是slave没有和master对齐，如何手动对齐呢 GitHub link: https://github.com/apache/rocketmq/discussions/6621 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a discussion: slave节点没有同步master
GitHub user zuoHx580 edited a discussion: slave节点没有同步master  应该是slave没有和master对齐，如何手动对齐呢 GitHub link: https://github.com/apache/rocketmq/discussions/6621 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 added a comment to the discussion: 自动主从切换部署不能选出master
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. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] kejiancai added a comment to the discussion: 5.1.0版本dledger集群时，定时消息不生效
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] kejiancai added a comment to the discussion: 5.1.0版本dledger集群时，定时消息不生效
GitHub user kejiancai added a comment to the discussion: 5.1.0版本dledger集群时，定时消息不生效 应该不是，我测试的时候，只加了10秒上去，而且不管是否出时间轮，在消息的MESSAGE ID那边是肯定要能查询到的，关键是现在没查询到，topic也没有这条数据，之前没有用dledger集群部署的时候，定时消息也都是正常的，用了dledger才出现了这个问题 GitHub link: https://github.com/apache/rocketmq/discussions/6617#discussioncomment-5658468 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: 5.1.0版本dledger集群时，定时消息不生效
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 automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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
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: https://github.com/apache/rocketmq/discussions/6616#discussioncomment-5657778 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 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
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: https://github.com/apache/rocketmq/discussions/6616#discussioncomment-5657765 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] MrZbb added a comment to the discussion: 请教个广播模式下如何避免重复消费的问题
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 used, the problem of old data being re-consumed after a machine is unavailable for a period of time and restarted is resolved. However, I feel that this approach is a bit of a workaround GitHub link: https://github.com/apache/rocketmq/discussions/6619#discussioncomment-5657688 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zhiliatom added a comment to the discussion: 5.1.0版本dledger集群时，定时消息不生效
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] kejiancai edited a comment on the discussion: 5.1.0版本dledger集群时，定时消息不生效
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 unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] kejiancai added a comment to the discussion: 5.1.0版本dledger集群时，定时消息不生效
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, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] superhx added a comment to the discussion: 请教个广播模式下如何避免重复消费的问题
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: https://github.com/apache/rocketmq/discussions/6619#discussioncomment-5657258 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zhiliatom added a comment to the discussion: 5.1.0版本dledger集群时，定时消息不生效
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 unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] kejiancai edited a discussion: 5.1.0版本dledger集群时，定时消息不生效
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 12:00:00的消息(该时间转换为1681876800)，setDeliverTimeMs(1681876800)设置之后，SendResult能够返回SendStatus.SEND_OK，且SendStatus.getMsgId()也是有值的，但是在集群内，在对应的tpic内无法查找到，通过message id也搜索不到（无论当前时间是否已经到了定时时间）。 GitHub link: https://github.com/apache/rocketmq/discussions/6617 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a discussion: fail to switch master and log said Update master address from 192.168.47.129:10911 to null
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 nameserve nested DLedger Controller on **192.168.47.128**, **192.168.47.129**,**192.168.47.130** i shutdown the b-master（192.168.47.129）manually and then I found slave（192.168.47.131） can't become master here is log:  GitHub link: https://github.com/apache/rocketmq/discussions/6616 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zuoHx580 edited a discussion: fail to switch master and log said Update master address from 192.168.47.129:10911 to null
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 nameserve nested DLedger Controller on 192.168.47.128, 192.168.47.129,192.168.47.130 i shutdown the b-master（192.168.47.129）manually and then I found slave（192.168.47.131） can't become master here is log:  GitHub link: https://github.com/apache/rocketmq/discussions/6616 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: In the local mode of RocketMQ 5, the pushconsumer for a FIFO queue experiences delays while consuming.
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: https://github.com/apache/rocketmq/discussions/6607#discussioncomment-5645716 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: The proxy local mode?
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 dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: The proxy local mode?
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. https://github.com/apache/rocketmq/blob/3fe81bfbac11ee9a3bf9c21155d2c9c69570bb72/proxy/src/main/java/org/apache/rocketmq/proxy/grpc/v2/route/RouteActivity.java#L183-L215 GitHub link: https://github.com/apache/rocketmq/discussions/6552#discussioncomment-5634449 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma edited a comment on the discussion: The proxy local mode?
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 also have a proxy. The client will only send messages to MASTER node. If the MASTER node is down, the client will send messages to the new MASTER after the election. GitHub link: https://github.com/apache/rocketmq/discussions/6552#discussioncomment-5567311 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq-clients] echooymxq edited a discussion: What's the traceContext in Clients?
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 trace on rocketmq-dashboard. In Aliyun ons TCP client, they implement a message trace interceptor to wrap the traceContext as part of the Message systemProperties. I would like to know this part will wroking on the future? Or don't plan to support message trace with 5.x gRPC sdk. /cc @aaron-ai GitHub link: https://github.com/apache/rocketmq-clients/discussions/474 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq-clients] echooymxq edited a discussion: Why not implement the traceContext in Clients?
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 and simple trace on rocketmq-dashboard. In Aliyun ons TCP client, they implement a message trace interceptor to wrap the traceContext as part of the Message systemProperties. I would like to know this part will wroking on the future? Or don't plan to support message trace with 5.x gRPC sdk. /cc @aaron-ai GitHub link: https://github.com/apache/rocketmq-clients/discussions/474 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq-clients] aaron-ai added a comment to the discussion: What not implement the traceContext in Clients?
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 as it is not part of our current roadmap. As a solution, we use OpenTelemetry as our observability tool for tracing and metrics, which is a universal and versatile solution suitable for distributed messaging systems. You may refer to the related documentation for further information. * [Trace for Messaging System](https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/messaging/) * [RocketMQ 5.0 Tracing Instrumentation](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/rocketmq/rocketmq-client/rocketmq-client-5.0) * [Kafka Instrumentation](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/kafka) * [RabbitMQ Instrumentation](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/rabbitmq-2.7) GitHub link: https://github.com/apache/rocketmq-clients/discussions/474#discussioncomment-5611756 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] jiakme added a comment to the discussion: single instance with multi DefaultLitePullConsumer(use same topic and different tag) don't poll message right
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 link: https://github.com/apache/rocketmq/discussions/6578#discussioncomment-5588427 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: single instance with multi DefaultLitePullConsumer(use same topic and different tag) don't poll message right
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: https://github.com/apache/rocketmq/discussions/6578#discussioncomment-5587290 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] jiakme added a comment to the discussion: single instance with multi DefaultLitePullConsumer(use same topic and different tag) don't poll message right
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 link: https://github.com/apache/rocketmq/discussions/6578#discussioncomment-5587201 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] jiakme edited a comment on the discussion: single instance with multi DefaultLitePullConsumer(use same topic and different tag) don't poll message right
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 pullConsumers = new ArrayList<>();
DefaultLitePullConsumer defaultLitePullConsumer =
getDefaultLitePullConsumer("high");
pullConsumers.add(defaultLitePullConsumer);
DefaultLitePullConsumer defaultLitePullConsumer_1 =
getDefaultLitePullConsumer("low");
pullConsumers.add(defaultLitePullConsumer_1);
PULL_CONSUMERS = Collections.unmodifiableList(pullConsumers);
}
private DefaultLitePullConsumer getDefaultLitePullConsumer(String tag) throws
MQClientException {
RocketMQProperties.Consumer consumerConfig = new
RocketMQProperties.Consumer();
consumerConfig.setGroup(MqConfig.CATEGORY_SMART_CAMPUS_APP_CENTER +
"_priority");
consumerConfig.setTopic(TOPIC);
consumerConfig.setPullBatchSize(50);
DefaultLitePullConsumer defaultLitePullConsumer;
consumerConfig.setSelectorExpression(tag);
defaultLitePullConsumer = buildPullConsumer(consumerConfig);
return defaultLitePullConsumer;
}
private DefaultLitePullConsumer buildPullConsumer(RocketMQProperties.Consumer
consumerConfig) throws MQClientException {
/**
* {@link
org.apache.rocketmq.spring.autoconfigure.RocketMQAutoConfiguration#defaultLitePullConsumer(RocketMQProperties)}
*/
String nameServer = rocketMQProperties.getNameServer();
String groupName = consumerConfig.getGroup();
String topicName = consumerConfig.getTopic();
Assert.hasText(nameServer, "[rocketmq.name-server] must not be null");
Assert.hasText(groupName, "[rocketmq.pull-consumer.group] must not be
null");
Assert.hasText(topicName, "[rocketmq.pull-consumer.topic] must not be
null");
String accessChannel = rocketMQProperties.getAccessChannel();
MessageModel messageModel =
MessageModel.valueOf(consumerConfig.getMessageModel());
SelectorType selectorType =
SelectorType.valueOf(consumerConfig.getSelectorType());
String selectorExpression = consumerConfig.getSelectorExpression();
String ak = consumerConfig.getAccessKey();
String sk = consumerConfig.getSecretKey();
int pullBatchSize = consumerConfig.getPullBatchSize();
boolean useTLS = consumerConfig.isTlsEnable();
DefaultLitePullConsumer litePullConsumer =
RocketMQUtil.createDefaultLitePullConsumer(nameServer, accessChannel,
groupName, topicName, messageModel, selectorType,
selectorExpression, ak, sk, pullBatchSize, useTLS);
litePullConsumer.setEnableMsgTrace(consumerConfig.isEnableMsgTrace());
litePullConsumer.setCustomizedTraceTopic(consumerConfig.getCustomizedTraceTopic());
litePullConsumer.setNamespace(consumerConfig.getNamespace());
litePullConsumer.setAllocateMessageQueueStrategy(new
AllocateMessageQueueAveragely());
litePullConsumer.setAutoCommit(true);
return litePullConsumer;
}
```
invoke poll method
```java
try {
if (CollUtil.isEmpty(PULL_CONSUMERS)) {
this.setRunning(true);
return;
}
for (DefaultLitePullConsumer pullConsumer : PULL_CONSUMERS) {
pullConsumer.start();
}
} catch (MQClientException e) {
throw new IllegalStateException("start pull fail", e);
}
```
GitHub link:
https://github.com/apache/rocketmq/discussions/6578#discussioncomment-5587162
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] jiakme edited a comment on the discussion: single instance with multi DefaultLitePullConsumer(use same topic and different tag) don't poll message right
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<>();
DefaultLitePullConsumer defaultLitePullConsumer =
getDefaultLitePullConsumer("high");
pullConsumers.add(defaultLitePullConsumer);
DefaultLitePullConsumer defaultLitePullConsumer_1 =
getDefaultLitePullConsumer("low");
pullConsumers.add(defaultLitePullConsumer_1);
PULL_CONSUMERS = Collections.unmodifiableList(pullConsumers);
}
private DefaultLitePullConsumer getDefaultLitePullConsumer(String tag) throws
MQClientException {
RocketMQProperties.Consumer consumerConfig = new
RocketMQProperties.Consumer();
consumerConfig.setGroup(MqConfig.CATEGORY_SMART_CAMPUS_APP_CENTER +
"_priority");
consumerConfig.setTopic(TOPIC);
consumerConfig.setPullBatchSize(50);
DefaultLitePullConsumer defaultLitePullConsumer;
consumerConfig.setSelectorExpression(tag);
defaultLitePullConsumer = buildPullConsumer(consumerConfig);
return defaultLitePullConsumer;
}
private DefaultLitePullConsumer buildPullConsumer(RocketMQProperties.Consumer
consumerConfig) throws MQClientException {
/**
* {@link
org.apache.rocketmq.spring.autoconfigure.RocketMQAutoConfiguration#defaultLitePullConsumer(RocketMQProperties)}
*/
String nameServer = rocketMQProperties.getNameServer();
String groupName = consumerConfig.getGroup();
String topicName = consumerConfig.getTopic();
Assert.hasText(nameServer, "[rocketmq.name-server] must not be null");
Assert.hasText(groupName, "[rocketmq.pull-consumer.group] must not be
null");
Assert.hasText(topicName, "[rocketmq.pull-consumer.topic] must not be
null");
String accessChannel = rocketMQProperties.getAccessChannel();
MessageModel messageModel =
MessageModel.valueOf(consumerConfig.getMessageModel());
SelectorType selectorType =
SelectorType.valueOf(consumerConfig.getSelectorType());
String selectorExpression = consumerConfig.getSelectorExpression();
String ak = consumerConfig.getAccessKey();
String sk = consumerConfig.getSecretKey();
int pullBatchSize = consumerConfig.getPullBatchSize();
boolean useTLS = consumerConfig.isTlsEnable();
DefaultLitePullConsumer litePullConsumer =
RocketMQUtil.createDefaultLitePullConsumer(nameServer, accessChannel,
groupName, topicName, messageModel, selectorType,
selectorExpression, ak, sk, pullBatchSize, useTLS);
litePullConsumer.setEnableMsgTrace(consumerConfig.isEnableMsgTrace());
litePullConsumer.setCustomizedTraceTopic(consumerConfig.getCustomizedTraceTopic());
litePullConsumer.setNamespace(consumerConfig.getNamespace());
litePullConsumer.setAllocateMessageQueueStrategy(new
AllocateMessageQueueAveragely());
litePullConsumer.setAutoCommit(true);
return litePullConsumer;
}
```
GitHub link:
https://github.com/apache/rocketmq/discussions/6578#discussioncomment-5587162
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] jiakme added a comment to the discussion: single instance with multi DefaultLitePullConsumer(use same topic and different tag) don't poll message right
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<>();
DefaultLitePullConsumer defaultLitePullConsumer =
getDefaultLitePullConsumer("high");
pullConsumers.add(defaultLitePullConsumer);
DefaultLitePullConsumer defaultLitePullConsumer_1 =
getDefaultLitePullConsumer("low");
pullConsumers.add(defaultLitePullConsumer_1);
PULL_CONSUMERS = Collections.unmodifiableList(pullConsumers);
}
private DefaultLitePullConsumer getDefaultLitePullConsumer(String tag) throws
MQClientException {
RocketMQProperties.Consumer consumerConfig = new
RocketMQProperties.Consumer();
consumerConfig.setGroup(MqConfig.CATEGORY_SMART_CAMPUS_APP_CENTER +
"_priority");
consumerConfig.setTopic(TOPIC);
consumerConfig.setPullBatchSize(50);
DefaultLitePullConsumer defaultLitePullConsumer;
consumerConfig.setSelectorExpression(tag);
defaultLitePullConsumer = buildPullConsumer(consumerConfig);
return defaultLitePullConsumer;
}
private DefaultLitePullConsumer buildPullConsumer(RocketMQProperties.Consumer
consumerConfig) throws MQClientException {
/**
* {@link
org.apache.rocketmq.spring.autoconfigure.RocketMQAutoConfiguration#defaultLitePullConsumer(RocketMQProperties)}
*/
String nameServer = rocketMQProperties.getNameServer();
String groupName = consumerConfig.getGroup();
String topicName = consumerConfig.getTopic();
Assert.hasText(nameServer, "[rocketmq.name-server] must not be null");
Assert.hasText(groupName, "[rocketmq.pull-consumer.group] must not be
null");
Assert.hasText(topicName, "[rocketmq.pull-consumer.topic] must not be
null");
String accessChannel = rocketMQProperties.getAccessChannel();
MessageModel messageModel =
MessageModel.valueOf(consumerConfig.getMessageModel());
SelectorType selectorType =
SelectorType.valueOf(consumerConfig.getSelectorType());
String selectorExpression = consumerConfig.getSelectorExpression();
String ak = consumerConfig.getAccessKey();
String sk = consumerConfig.getSecretKey();
int pullBatchSize = consumerConfig.getPullBatchSize();
boolean useTLS = consumerConfig.isTlsEnable();
DefaultLitePullConsumer litePullConsumer =
RocketMQUtil.createDefaultLitePullConsumer(nameServer, accessChannel,
groupName, topicName, messageModel, selectorType,
selectorExpression, ak, sk, pullBatchSize, useTLS);
litePullConsumer.setEnableMsgTrace(consumerConfig.isEnableMsgTrace());
litePullConsumer.setCustomizedTraceTopic(consumerConfig.getCustomizedTraceTopic());
litePullConsumer.setNamespace(consumerConfig.getNamespace());
litePullConsumer.setAllocateMessageQueueStrategy(new
AllocateMessageQueueAveragely());
litePullConsumer.setAutoCommit(true);
return litePullConsumer;
}`
GitHub link:
https://github.com/apache/rocketmq/discussions/6578#discussioncomment-5587162
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] francisoliverlee added a comment to the discussion: add api reporting producer runninginfo to broker as consumer did
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, 微信同qq号 GitHub link: https://github.com/apache/rocketmq/discussions/6539#discussioncomment-5568108 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] francisoliverlee added a comment to the discussion: add api reporting producer runninginfo to broker as consumer did
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(). producer can do the same.  GitHub link: https://github.com/apache/rocketmq/discussions/6539#discussioncomment-5568049 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] francisoliverlee added a comment to the discussion: The proxy local mode?
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: https://github.com/apache/rocketmq/discussions/6552#discussioncomment-5568028 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: The proxy local mode?
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 proxy on all the broker nodes(Because we don't know which broker is Master on autoswicth HA or Dledger mode). I will submit a PR to optimize the message escape on local mode. GitHub link: https://github.com/apache/rocketmq/discussions/6552#discussioncomment-5567467 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: The proxy local mode?
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 have a proxy. The client will only send messages to MASTER node. If the MASTER node is down, the client will send messages to the new MASTER after the election. GitHub link: https://github.com/apache/rocketmq/discussions/6552#discussioncomment-5567311 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq edited a discussion: The proxy local mode?
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 which broker of Proxy is master, if the current connected proxy of broker is SLAVE, it will send message error. We should escape the message to remote broker in `LocalMessageService` when the current broker is SLAVE. /cc @drpmma GitHub link: https://github.com/apache/rocketmq/discussions/6552 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Abhijeetmishr added a comment to the discussion: add api reporting producer runninginfo to broker as consumer did
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: https://github.com/apache/rocketmq/discussions/6539#discussioncomment-5544858 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] aaron-ai edited a discussion: Migrate logging related artifact to an independent apache repository.
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 `org.apache.rocketmq`. There are two potential solutions available: The first solution is to establish a new repository called rocketmq-logging, while the second solution is to place it in [rocketmq-external](https://github.com/apache/rocketmq-externals). The logging module has the following characteristics: the shaded logback is not universal and is specifically shaded for RocketMQ. this is a project customized for the RocketMQ main repository. However, Maven multi-module projects are not very friendly towards the independent shaded modules, so it is not very suitable to have it in the RocketMQ main repository. Additionally, since ASF repositories cannot be deleted and can only be archived, we need to carefully consider this to avoid unnecessary archiving operations in the future. for example: [rocketmq-client-rust](https://github.com/apache/rocketmq-client-rust) GitHub link: https://github.com/apache/rocketmq/discussions/6526 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved
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 It is recommended to add the following indicators: 1. 【Node/Topic】Number of messages produced/consumed 2. 【Node/Topic】Production/consumption message size / 3. 【Node/Topic】Time spent on each interface request 4. 【Node/Topic】Statistics on error codes of each interface 5. 【Node】The number of calls to each interface 6. 【Node】TCP(GRPC/Remoting) connection count statistics 7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity of each thread pool) monitoring 8. 【Node】Process status: indicates that the current process is started or stopped The following table describes the labels of the metrics that are related to the Message Queue for Apache RocketMQ Proxy. cluster: RocketMQ cluster name. node_type: the type of service node, whitch includes the following:proxy,broker,nameserver. node_id:the ID of the service node. topic: the topic of RocketMQ. thread_type: The use of thread pools. eg: sendMessage、pullMessage protocol_type: Type of protocol. eg: grpc, remoting proxy_mode: cluster mode. eg: local, cluster Indicators of node dimension: Type | Name | Unit | Description | Label -- | -- | -- | -- | -- counter | rocketmq_messages_in_total | count | The number of messages that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_messages_out_total | count | The number of messages that are consumed. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_throughput_in_total | byte | The write throughput that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_throughput_out_total | byte | The read throughput that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode histogram | rocketmq_message_size | byte | The distribution of message sizes. This metric is counted only when messages are sent. The following shows the distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | cluster,node_type,node_id,topic, protocol_type,proxy_mode histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow | cluster,node_typ,node_id, request_code, response_code,proxy_mode counter | rocketmq_producer_connections | count | Number of connections for the producer | cluster,node_typ,node_id,proxy_mode counter | rocketmq_consumer_connections | count | The number of consumer connections | cluster,node_typ,node_id,proxy_mode guage | rocketmq_processor_watermark | count | High watermark information for the thread| cluster,node_typ,node_id,thread_type,proxy_mode gauge | rocketmq_proxy_up | value | Process running status | cluster,node_typ,node_id,proxy_mode GitHub link: https://github.com/apache/rocketmq/discussions/6405 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved
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 It is recommended to add the following indicators: 1. 【Node/Topic】Number of messages produced/consumed 2. 【Node/Topic】Production/consumption message size / 3. 【Node/Topic】Time spent on each interface request 4. 【Node/Topic】Statistics on error codes of each interface 5. 【Node】The number of calls to each interface 6. 【Node】TCP(GRPC/Remoting) connection count statistics 7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity of each thread pool) monitoring 8. 【Node】Process status: indicates that the current process is started or stopped The following table describes the labels of the metrics that are related to the Message Queue for Apache RocketMQ Proxy. cluster: RocketMQ cluster name. node_type: the type of service node, whitch includes the following:proxy,broker,nameserver. node_id:the ID of the service node. topic: the topic of RocketMQ. thread_type: The use of thread pools. eg: sendMessage、pullMessage protocol_type: Type of protocol. eg: grpc, remoting proxy_mode: cluster mode. eg: local, cluster Indicators of node dimension: Type | Name | Unit | Description | Label -- | -- | -- | -- | -- counter | rocketmq_messages_in_total | count | The number of messages that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_messages_out_total | count | The number of messages that are consumed. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_throughput_in_total | byte | The write throughput that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_throughput_out_total | byte | The read throughput that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode histogram | rocketmq_message_size | byte | The distribution of message sizes. This metric is counted only when messages are sent. The following shows the distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | cluster,node_type,node_id,topic, protocol_type,proxy_mode histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow | cluster,node_typ,node_id, request_code,request_code, response_code,proxy_mode counter | rocketmq_producer_connections | count | Number of connections for the producer | cluster,node_typ,node_id,proxy_mode counter | rocketmq_consumer_connections | count | The number of consumer connections | cluster,node_typ,node_id,proxy_mode guage | rocketmq_processor_watermark | count | High watermark information for the thread| cluster,node_typ,node_id,thread_type,proxy_mode gauge | rocketmq_proxy_up | value | Process running status | cluster,node_typ,node_id,proxy_mode GitHub link: https://github.com/apache/rocketmq/discussions/6405 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved
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 It is recommended to add the following indicators: 1. 【Node/Topic】Number of messages produced/consumed 2. 【Node/Topic】Production/consumption message size / 3. 【Node/Topic】Time spent on each interface request 4. 【Node/Topic】Statistics on error codes of each interface 5. 【Node】The number of calls to each interface 6. 【Node】TCP(GRPC/Remoting) connection count statistics 7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity of each thread pool) monitoring 8. 【Node】Process status: indicates that the current process is started or stopped The following table describes the labels of the metrics that are related to the Message Queue for Apache RocketMQ Proxy. cluster: RocketMQ cluster name. node_type: the type of service node, whitch includes the following:proxy,broker,nameserver. node_id:the ID of the service node. topic: the topic of RocketMQ. thread_type: The use of thread pools. eg: sendMessage、pullMessage protocol_type: Type of protocol. eg: grpc, remoting proxy_mode: cluster mode. eg: local, cluster Indicators of node dimension: Type | Name | Unit | Description | Label -- | -- | -- | -- | -- counter | rocketmq_messages_in_total | count | The number of messages that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_messages_out_total | count | The number of messages that are consumed. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_throughput_in_total | byte | The write throughput that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode counter | rocketmq_throughput_out_total | byte | The read throughput that are produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode histogram | rocketmq_message_size | byte | The distribution of message sizes. This metric is counted only when messages are sent. The following shows the distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | cluster,node_type,node_id,topic, protocol_type,proxy_mode histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow | cluster,node_typ,node_id, request_code,request_code, response_code,proxy_mode counter | rocketmq_producer_connections | count | Number of connections for the producer | cluster,node_typ,node_id,proxy_mode counter | rocketmq_consumer_connections | count | The number of consumer connections | cluster,node_typ,node_id,proxy_mode guage | rocketmq_processor_watermark | count | High watermark information for the thread| cluster,node_typ,node_id,thread_type,proxy_mode gauge | rocketmq_proxy_up | value | Process running status | cluster,node_typ,node_id,proxy_mode GitHub link: https://github.com/apache/rocketmq/discussions/6405 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved
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 It is recommended to add the following indicators: 1. 【Node/Topic】Number of messages produced/consumed 2. 【Node/Topic】Production/consumption message size / 3. 【Node/Topic】Time spent on each interface request 4. 【Node/Topic】Statistics on error codes of each interface 5. 【Node】The number of calls to each interface 6. 【Node】TCP(GRPC/Remoting) connection count statistics 7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity of each thread pool) monitoring 8. 【Node】Process status: indicates that the current process is started or stopped The following table describes the labels of the metrics that are related to the Message Queue for Apache RocketMQ Proxy. cluster: RocketMQ cluster name. node_type: the type of service node, whitch includes the following:proxy,broker,nameserver. node_id:the ID of the service node. topic: the topic of RocketMQ. thread_type: The use of thread pools. eg: sendMessage、pullMessage protocol_type: Type of protocol. eg: grpc, remoting Indicators of node dimension: Type | Name | Unit | Description | Label -- | -- | -- | -- | -- counter | rocketmq_messages_in_total | count | The number of messages that are produced. | cluster,node_type,node_id,topic, protocol_type counter | rocketmq_messages_out_total | count | The number of messages that are consumed. | cluster,node_type,node_id,topic, protocol_type counter | rocketmq_throughput_in_total | byte | The write throughput that are produced. | cluster,node_type,node_id,topic, protocol_type counter | rocketmq_throughput_out_total | byte | The read throughput that are produced. | cluster,node_type,node_id,topic, protocol_type histogram | rocketmq_message_size | byte | The distribution of message sizes. This metric is counted only when messages are sent. The following shows the distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | cluster,node_type,node_id,topic, protocol_type histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow | cluster,node_typ,node_id, request_code,request_code, response_code counter | rocketmq_producer_connections | count | Number of connections for the producer | cluster,node_typ,node_id counter | rocketmq_consumer_connections | count | The number of consumer connections | cluster,node_typ,node_id guage | rocketmq_processor_watermark | count | High watermark information for the thread| cluster,node_typ,node_id,thread_type gauge | rocketmq_proxy_up | value | Process running status | cluster,node_typ,node_id GitHub link: https://github.com/apache/rocketmq/discussions/6405 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved
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 It is recommended to add the following indicators: 1. 【Node/Topic】Number of messages produced/consumed 2. 【Node/Topic】Production/consumption message size / 3. 【Node/Topic】Time spent on each interface request 4. 【Node/Topic】Statistics on error codes of each interface 5. 【Node】The number of calls to each interface 6. 【Node】TCP(GRPC/Remoting) connection count statistics 7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity of each thread pool) monitoring 8. 【Node】Process status: indicates that the current process is started or stopped The following table describes the labels of the metrics that are related to the Message Queue for Apache RocketMQ Proxy. cluster: RocketMQ cluster name. node_type: the type of service node, whitch includes the following:proxy,broker,nameserver. node_id:the ID of the service node. topic: the topic of RocketMQ. thread_type: The use of thread pools. eg: sendMessage、pullMessage Indicators of node dimension: Type | Name | Unit | Description | Label -- | -- | -- | -- | -- counter | rocketmq_messages_in_total | count | The number of messages that are produced. | cluster,node_type,node_id,topic counter | rocketmq_messages_out_total | count | The number of messages that are consumed. | cluster,node_type,node_id,topic counter | rocketmq_throughput_in_total | byte | The write throughput that are produced. | cluster,node_type,node_id,topic counter | rocketmq_throughput_out_total | byte | The read throughput that are produced. | cluster,node_type,node_id,topic histogram | rocketmq_message_size | byte | The distribution of message sizes. This metric is counted only when messages are sent. The following shows the distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | cluster,node_type,node_id,topic histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow | cluster,node_typ,node_id, request_code,request_code, response_code counter | rocketmq_producer_connections | count | Number of connections for the producer | cluster,node_typ,node_id counter | rocketmq_consumer_connections | count | The number of consumer connections | cluster,node_typ,node_id guage | rocketmq_processor_watermark | count | High watermark information for the thread| cluster,node_typ,node_id,thread_type gauge | rocketmq_proxy_up | value | Process running status | cluster,node_typ,node_id GitHub link: https://github.com/apache/rocketmq/discussions/6405 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved
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 It is recommended to add the following indicators: 1. 【Node/Topic】Number of messages produced/consumed 2. 【Node/Topic】Production/consumption message size / 3. 【Node/Topic】Time spent on each interface request 4. 【Node/Topic】Statistics on error codes of each interface 5. 【Node】The number of calls to each interface 6. 【Node】TCP(GRPC/Remoting) connection count statistics 7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity of each thread pool) monitoring 8. 【Node】Process status: indicates that the current process is started or stopped The following table describes the labels of the metrics that are related to the Message Queue for Apache RocketMQ Proxy. cluster: RocketMQ cluster name. node_type: the type of service node, whitch includes the following:proxy,broker,nameserver. node_id:the ID of the service node. topic: the topic of RocketMQ. thread_type: The use of thread pools. eg: sendMessage、pullMessage Indicators of node dimension: Type | Name | Unit | Description | Label -- | -- | -- | -- | -- counter | rocketmq_messages_in_total | count | The number of messages that are produced. | cluster,node_type,node_id,topic counter | rocketmq_messages_out_total | count | The number of messages that are consumed. | cluster,node_type,node_id,topic counter | rocketmq_throughput_in_total | byte | The write throughput that are produced. | cluster,node_type,node_id,topic counter | rocketmq_throughput_out_total | byte | The read throughput that are produced. | cluster,node_type,node_id,topic histogram | rocketmq_message_size | byte | The distribution of message sizes. This metric is counted only when messages are sent. The following shows the distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | cluster,node_type,node_id,topic histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges: ranges: le_1_ms le_5_ms le_10_ms le_100_ms le_1_ms le_6_ms le_overflow | cluster,node_typ,node_id, request_code,request_code, response_code counter | rocketmq_producer_connections | count | Number of connections for the producer | cluster,node_typ,node_id counter | rocketmq_consumer_connections | count | The number of consumer connections | cluster,node_typ,node_id guage | rocketmq_processor_watermark | count | High watermark information for the thread| cluster,node_typ,node_id,thread_type gauge | rocketmq_proxy_up | value | Process running status | cluster,node_typ,node_id GitHub link: https://github.com/apache/rocketmq/discussions/6405 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved
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 It is recommended to add the following indicators: 1. 【Node/Topic】Number of messages produced/consumed 2. 【Node/Topic】Production/consumption message size / 3. 【Node/Topic】Time spent on each interface request 4. 【Node/Topic】Statistics on error codes of each interface 5. 【Node】The number of calls to each interface 6. 【Node】TCP(GRPC/Remoting) connection count statistics 7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity of each thread pool) monitoring 8. 【Node】Process status: indicates that the current process is started or stopped The following table describes the labels of the metrics that are related to the Message Queue for Apache RocketMQ Proxy. cluster: RocketMQ cluster name. node_type: the type of service node, whitch includes the following:proxy,broker,nameserver. node_id:the ID of the service node. topic: the topic of RocketMQ. thread_type: The use of thread pools. eg: sendMessage、pullMessage Indicators of node dimension: Type | Name | Unit | Description | Label -- | -- | -- | -- | -- counter | rocketmq_messages_in_total | count | The number of messages that are produced. | cluster,node_type,node_id,topic counter | rocketmq_messages_out_total | count | The number of messages that are consumed. | cluster,node_type,node_id,topic counter | rocketmq_throughput_in_total | byte | The write throughput that are produced. | cluster,node_type,node_id,topic counter | rocketmq_throughput_out_total | byte | The read throughput that are produced. | cluster,node_type,node_id,topic histogram | rocketmq_message_size | byte | The distribution of message sizes. This metric is counted only when messages are sent. The following shows the distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | cluster,node_type,node_id,topic histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow| cluster,node_typ,node_id, request_code,request_code, response_code counter | rocketmq_producer_connections | count | Number of connections for the producer | cluster,node_typ,node_id counter | rocketmq_consumer_connections | count | The number of consumer connections | cluster,node_typ,node_id guage | rocketmq_processor_watermark | count | High watermark information for the thread| cluster,node_typ,node_id,thread_type gauge | rocketmq_proxy_up | value | Process running status | cluster,node_typ,node_id GitHub link: https://github.com/apache/rocketmq/discussions/6405 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
