Re: [I] [Bug] The lettuce log appears in rocketmq_client.log, although rocketmq does not use this package, but why lettuce logs will be output to rocketmq_client.log? lettuce package when redis topolo
FrankCy commented on issue #8111: URL: https://github.com/apache/rocketmq/issues/8111#issuecomment-2102078851 > org.apache.rocketmq.client.log.ClientLogger > > set -Drocketmq.client.logUseSlf4j=true > > and try again Thank you. I'll try it later. -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] [Enhancement] 请发布一个Node.js客户端的新版本，解决 #676 和 #649 [rocketmq-clients]
VxRain opened a new issue, #745: URL: https://github.com/apache/rocketmq-clients/issues/745 ### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Programming Language of the Client Node.js ### Summary 该提交 (https://github.com/apache/rocketmq-clients/commit/0f38c07a704225e0e32a3895b17d38f01e2b01ee) 解决了心跳包参数错误的问题，关联 #676 和 #649 但是这个bug修复后没发版，目前npm上的版本，消费者跑一段时间后还是会抛异常 > InternalErrorException: [request-id=undefined, response-code=50001] INTERNAL_SERVER_ERROR 应该发布一个新版本来解决这个问题 ### Motivation 修复Node.js客户端bug ### Describe the Solution You'd Like 发布一个新版本 ### Describe Alternatives You've Considered 暂无 ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Enhancement] 请发布一个Node.js客户端的新版本，解决 #676 和 #649 [rocketmq-clients]
VxRain commented on issue #745: URL: https://github.com/apache/rocketmq-clients/issues/745#issuecomment-2102091364 @aaron-ai @lizhanhui -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Bug] The lettuce log appears in rocketmq_client.log, although rocketmq does not use this package, but why lettuce logs will be output to rocketmq_client.log? lettuce package when redis topolo
FrankCy commented on issue #8111: URL: https://github.com/apache/rocketmq/issues/8111#issuecomment-2102288031 > org.apache.rocketmq.client.log.ClientLogger > > set -Drocketmq.client.logUseSlf4j=true > > and try again It's not correct, it won't even output the following INFO record after setting it up INFO RocketmqClient - [persistAll] Group: -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [Bug] The lettuce log appears in rocketmq_client.log, although rocketmq does not use this package, but why lettuce logs will be output to rocketmq_client.log? lettuce package when redis topolo
FrankCy commented on issue #8111: URL: https://github.com/apache/rocketmq/issues/8111#issuecomment-2102309176 rocketmq startup parameters: -Drocketmq.client.logRoot=/data/logs/ -Drocketmq.client.logLevel=DEBUG A snippet of the rockemq_client.log output: 2024-05-09 17:30:44,832 DEBUG io.lettuce.core.cluster.PooledClusterConnectionProvider$DefaultClusterNodeConnectionFactory - Resolved SocketAddress 172.17.48.40:6379 using for Cluster node at 172.17.48.40:6379 2024-05-09 17:30:44,832 DEBUG io.lettuce.core.cluster.PooledClusterConnectionProvider$DefaultClusterNodeConnectionFactory - Resolved SocketAddress 172.17.48.40:6379 using for Cluster node at 172.17.48.40:6379 2024-05-09 17:30:44,832 DEBUG io.lettuce.core.cluster.PooledClusterConnectionProvider$DefaultClusterNodeConnectionFactory - Resolved SocketAddress 172.17.48.40:6379 using for Cluster node at 172.17.48.40:6379 2024-05-09 17:30:44,897 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] channelActive() 2024-05-09 17:30:44,897 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] channelActive() 2024-05-09 17:30:44,897 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] channelActive() 2024-05-09 17:30:44,898 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] channelActive() 2024-05-09 17:30:44,898 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] channelActive() 2024-05-09 17:30:44,898 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] channelActive() 2024-05-09 17:30:44,899 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@34fe5c90) 2024-05-09 17:30:44,899 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@34fe5c90) 2024-05-09 17:30:44,899 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@34fe5c90) 2024-05-09 17:30:44,899 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@34fe5c90) 2024-05-09 17:30:44,899 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@34fe5c90) 2024-05-09 17:30:44,899 DEBUG io.lettuce.core.protocol.ConnectionWatchdog - [channel=0x74b549ee, /10.8.0.70:59425 -> 172.17.48.40/172.17.48.40:6379, last known addr=172.17.48.40/172.17.48.40:6379] userEventTriggered(ctx, io.lettuce.core.ConnectionEvents$Activated@34fe5c90) 2024-05-09 17:30:47,644 INFO RocketmqClient - [persistAll] Group: frank-rocketmq-demo ClientId: 10.8.0.70@172.17.48.88:9876@26015 updateConsumeOffsetToBroker MessageQueue [topic=%RETRY%frank-rocketmq-demo-group, brokerName=broker-a, queueId=0] 1655 2024-05-09 17:30:47,646 INFO RocketmqClient - [persistAll] Group: frank-rocketmq-demo ClientId: 10.8.0.70@172.17.48.88:9876@26015 updateConsumeOffsetToBroker MessageQueue [topic=ARCH_CACHE_MIDDLEWARE_FRANK, brokerName=broker-a, queueId=0] 3960 2024-05-09 17:30:47,647 INFO RocketmqClient - [persistAll] Group: frank-rocketmq-demo ClientId: 10.8.0.70@172.17.48.88:9876@26015 updateConsumeOffsetToBroker MessageQueue [topic=ARCH_CACHE_MIDDLEWARE_FRANK, brokerName=broker-a, queueId=1] 3963 2024-05-09 17:30:47,647 INFO RocketmqClient - [persistAll] Group: frank-rocketmq-demo ClientId: 10.8.0.70@172.17.48.88:9876@26015 updateConsumeOffsetToBroker MessageQueue [topic=ARCH_CACHE_MIDDLEWARE_FRANK, brokerName=broker-a, queueId=2] 3957 2024-05-09 17:30:47,647 INFO RocketmqClient - [persistAll] Group: frank-rocketmq-demo C
Re: [I] [Enhancement] Support tiered storage run in primary/backup mode [rocketmq]
bxfjb commented on issue #8066: URL: https://github.com/apache/rocketmq/issues/8066#issuecomment-2102529918 > 当前分级存储对主备模式和 DLedger 的支持不够完善，非常欢迎你把他作为新的特性来贡献。从设计方案上来说，并不只是 schedule 任务判断一下即可，metadata store 中元数据的同步，以及 broker container 模式下的截断等问题都是需要考虑和讨论的，从目前的 pr 来看考虑不够完善。 hello，最近在考虑 IndexFile 的主从同步问题，发现如果使用对象存储作为冷存，根据现有逻辑，如果发生切主，由于从节点无法获得未上传的 IndexFile 中消息所指向的冷存中的消费位点，Sealed 与 Unsealed 部分的数据似乎会永久丢失掉，这个问题有什么解决思路吗 目前可以想到的折中方案包括：将 DispatchRequest 攒批同步到从节点，从节点自行构建本地 IndexFile，切为主节点后再做上传；但这个方案问题在于同步过程容易出现 gap，可以预见到切主过程中这段时间的消息将不能通过 IndexFile 查询到 -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] springboot3.1.7 version can`t consum message [rocketmq]
humkum commented on issue #8112: URL: https://github.com/apache/rocketmq/issues/8112#issuecomment-2102550934 You can start a new issue in project https://github.com/apache/rocketmq-spring/issues -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [csharp] Optimization message id generator performance. [rocketmq-clients]
github-actions[bot] commented on PR #724: URL: https://github.com/apache/rocketmq-clients/pull/724#issuecomment-2103637386 This PR is stale because it has been open for 30 days with no activity. It will be closed in 3 days if no further activity occurs. If you wish not to mark it as stale, please leave a comment in this PR. -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [ISSUE #5923] Fix tiered store README.md error [rocketmq]
yuz10 opened a new pull request, #8115: URL: https://github.com/apache/rocketmq/pull/8115 ### Which Issue(s) This PR Fixes Fixes #5923 ### Brief Description ### How Did You Test This Change? -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GH] (rocketmq): Workflow run "E2E test for pull request" failed!
The GitHub Actions job "E2E test for pull request" on rocketmq.git has failed. Run started by GitHub user yuz10 (triggered by yuz10). Head commit for run: 89c1509014b15c2ce91161356cf09a18c945a926 / dingshuangxi888 [ISSUE #8046] Fix authentication context build for no extFields (#8102) Report URL: https://github.com/apache/rocketmq/actions/runs/9025900125 With regards, GitHub Actions via GitBox
[GH] (rocketmq): Workflow run "Coverage" failed!
The GitHub Actions job "Coverage" on rocketmq.git has failed. Run started by GitHub user yuz10 (triggered by yuz10). Head commit for run: 7583c68b5da7d599d15b3e1ba155cd4729b2cf27 / yuz10 <845238...@qq.com> [ISSUE #5923] Fix tiered store README.md error Report URL: https://github.com/apache/rocketmq/actions/runs/9025871527 With regards, GitHub Actions via GitBox
Re: [PR] [ISSUE #8070] Optimize the submitConsumeRequest and remove unnecessary exception catching [rocketmq]
cserwen commented on PR #8071: URL: https://github.com/apache/rocketmq/pull/8071#issuecomment-2103750693 Merge develop branch to fix the ut. @biningo -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" is working again!
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has succeeded. Run started by GitHub user yuz10 (triggered by yuz10). Head commit for run: 7583c68b5da7d599d15b3e1ba155cd4729b2cf27 / yuz10 <845238...@qq.com> [ISSUE #5923] Fix tiered store README.md error Report URL: https://github.com/apache/rocketmq/actions/runs/9025871532 With regards, GitHub Actions via GitBox
Re: [PR] [ISSUE #50] Feature add rocketmq exporter to nameserver [rocketmq-operator]
anguoming commented on code in PR #51: URL: https://github.com/apache/rocketmq-operator/pull/51#discussion_r1596190384 ## example/rocketmq_v1alpha1_rocketmq_exporter_cluster.yaml: ## @@ -0,0 +1,157 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +apiVersion: v1 +kind: ConfigMap +metadata: + name: broker-config +data: + # BROKER_MEM sets the broker JVM, if set to "" then Xms = Xmx = max(min(1/2 ram, 1024MB), min(1/4 ram, 8GB)) + BROKER_MEM: " -Xms2g -Xmx2g -Xmn1g " + broker-common.conf: | +# brokerClusterName, brokerName, brokerId are automatically generated by the operator and do not set it manually!!! +deleteWhen=04 +fileReservedTime=48 +flushDiskType=ASYNC_FLUSH +# set brokerRole to ASYNC_MASTER or SYNC_MASTER. DO NOT set to SLAVE because the replica instance will automatically be set!!! +brokerRole=ASYNC_MASTER + +--- +apiVersion: rocketmq.apache.org/v1alpha1 +kind: Broker +metadata: + # name of broker cluster + name: broker +spec: + # size is the number of the broker cluster, each broker cluster contains a master broker and [replicaPerGroup] replica brokers. + size: 1 + # nameServers is the [ip:port] list of name service + nameServers: "" + # replicaPerGroup is the number of each broker cluster + replicaPerGroup: 0 + # brokerImage is the customized docker image repo of the RocketMQ broker + brokerImage: apacherocketmq/rocketmq-broker:4.5.0-alpine-operator-0.3.0 + # imagePullPolicy is the image pull policy + imagePullPolicy: Always + # resources describes the compute resource requirements and limits + resources: +requests: + memory: "2048Mi" + cpu: "250m" +limits: + memory: "12288Mi" + cpu: "500m" + # allowRestart defines whether allow pod restart + allowRestart: true + # storageMode can be EmptyDir, HostPath, StorageClass + storageMode: EmptyDir + # hostPath is the local path to store data + hostPath: /tmp/data/rocketmq/broker + # scalePodName is [Broker name]-[broker group number]-master-0 + scalePodName: broker-0-master-0 + # env defines custom env, e.g. BROKER_MEM + env: +- name: BROKER_MEM + valueFrom: +configMapKeyRef: + name: broker-config + key: BROKER_MEM + # volumes defines the broker.conf + volumes: +- name: broker-config + configMap: +name: broker-config +items: + - key: broker-common.conf +path: broker-common.conf + # volumeClaimTemplates defines the storageClass + volumeClaimTemplates: +- metadata: +name: broker-storage + spec: +accessModes: + - ReadWriteOnce +resources: + requests: +storage: 8Gi +selector: + matchLabels: +app: broker-storage-pv +--- +apiVersion: rocketmq.apache.org/v1alpha1 +kind: NameService +metadata: + name: name-service +spec: + # size is the the name service instance number of the name service cluster + size: 1 + # nameServiceImage is the customized docker image repo of the RocketMQ name service + nameServiceImage: apacherocketmq/rocketmq-nameserver:4.5.0-alpine-operator-0.3.0 + # imagePullPolicy is the image pull policy + imagePullPolicy: Always + # hostNetwork can be true or false + hostNetwork: true + # Set DNS policy for the pod. + # Defaults to "ClusterFirst". + # Valid values are 'ClusterFirstWithHostNet', 'ClusterFirst', 'Default' or 'None'. + # DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. + # To have DNS options set along with hostNetwork, you have to specify DNS policy + # explicitly to 'ClusterFirstWithHostNet'. + dnsPolicy: ClusterFirstWithHostNet + # resources describes the compute resource requirements and limits + resources: +requests: + memory: "512Mi" + cpu: "250m" +limits: + memory: "1024Mi" + cpu: "500m" + # storageMode can be EmptyDir, HostPath, StorageClass + storageMode: EmptyDir + # hostPath is the local path to store data + hostPath: /data/rocketmq/nameserver + exporter: +enabled: true +annotations: + prometheus.io/path: /metrics + prometheus.io/port: "5557" + prometheus.io/scrape: "true" +env: +
Re: [PR] [ISSUE #5838] retry to send when broker returns SYSTEM_BUSY [rocketmq]
cserwen merged PR #5845: URL: https://github.com/apache/rocketmq/pull/5845 -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Client will not retry to send message when broker busy [rocketmq]
cserwen closed issue #5838: Client will not retry to send message when broker busy URL: https://github.com/apache/rocketmq/issues/5838 -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
(rocketmq) branch develop updated: [ISSUE #5838] retry to send when broker returns SYSTEM_BUSY (#5845)
This is an automated email from the ASF dual-hosted git repository.
cserwen pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git
The following commit(s) were added to refs/heads/develop by this push:
new e5b357c3df [ISSUE #5838] retry to send when broker returns SYSTEM_BUSY
(#5845)
e5b357c3df is described below
commit e5b357c3dfd9066c6bd363e44533371d195e26e6
Author: cserwen
AuthorDate: Fri May 10 11:10:42 2024 +0800
[ISSUE #5838] retry to send when broker returns SYSTEM_BUSY (#5845)
---
.../main/java/org/apache/rocketmq/client/producer/DefaultMQProducer.java | 1 +
1 file changed, 1 insertion(+)
diff --git
a/client/src/main/java/org/apache/rocketmq/client/producer/DefaultMQProducer.java
b/client/src/main/java/org/apache/rocketmq/client/producer/DefaultMQProducer.java
index 0abf925a82..b350ba074d 100644
---
a/client/src/main/java/org/apache/rocketmq/client/producer/DefaultMQProducer.java
+++
b/client/src/main/java/org/apache/rocketmq/client/producer/DefaultMQProducer.java
@@ -72,6 +72,7 @@ public class DefaultMQProducer extends ClientConfig
implements MQProducer {
ResponseCode.TOPIC_NOT_EXIST,
ResponseCode.SERVICE_NOT_AVAILABLE,
ResponseCode.SYSTEM_ERROR,
+ResponseCode.SYSTEM_BUSY,
ResponseCode.NO_PERMISSION,
ResponseCode.NO_BUYER_ID,
ResponseCode.NOT_IN_CURRENT_UNIT
Re: [PR] [ISSUE #8053] Return SYSTEM_BUSY if PutMessageStatus is OS_PAGE_CACHE_BUSY [rocketmq]
cserwen commented on PR #8054: URL: https://github.com/apache/rocketmq/pull/8054#issuecomment-2103780162 @biningo merge develop to fix the ut -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GH] (rocketmq): Workflow run "PUSH-CI" is working again!
The GitHub Actions job "PUSH-CI" on rocketmq.git has succeeded. Run started by GitHub user cserwen (triggered by cserwen). Head commit for run: e5b357c3dfd9066c6bd363e44533371d195e26e6 / cserwen [ISSUE #5838] retry to send when broker returns SYSTEM_BUSY (#5845) Report URL: https://github.com/apache/rocketmq/actions/runs/9026698690 With regards, GitHub Actions via GitBox
[GH] (rocketmq): Workflow run "Coverage" is working again!
The GitHub Actions job "Coverage" on rocketmq.git has succeeded. Run started by GitHub user cserwen (triggered by cserwen). Head commit for run: e5b357c3dfd9066c6bd363e44533371d195e26e6 / cserwen [ISSUE #5838] retry to send when broker returns SYSTEM_BUSY (#5845) Report URL: https://github.com/apache/rocketmq/actions/runs/9026698687 With regards, GitHub Actions via GitBox
Re: [PR] [ISSUE #5923] Fix tiered store README.md error [rocketmq]
codecov-commenter commented on PR #8115: URL: https://github.com/apache/rocketmq/pull/8115#issuecomment-2103807676 ## [Codecov](https://app.codecov.io/gh/apache/rocketmq/pull/8115?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report All modified and coverable lines are covered by tests :white_check_mark: > Project coverage is 42.91%. Comparing base [(`89c1509`)](https://app.codecov.io/gh/apache/rocketmq/commit/89c1509014b15c2ce91161356cf09a18c945a926?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) to head [(`7583c68`)](https://app.codecov.io/gh/apache/rocketmq/pull/8115?dropdown=coverage&src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache). > Report is 1 commits behind head on develop. Additional details and impacted files ```diff @@ Coverage Diff @@ ## develop#8115 +/- ## = - Coverage 42.93% 42.91% -0.02% + Complexity 1038710382 -5 = Files 1270 1270 Lines 8869388693 Branches 1140111401 = - Hits 3807938066 -13 - Misses 4592545929 +4 - Partials4689 4698 +9 ``` [:umbrella: View full report in Codecov by Sentry](https://app.codecov.io/gh/apache/rocketmq/pull/8115?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache). :loudspeaker: Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache). -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" failed!
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has failed. Run started by GitHub user cserwen (triggered by cserwen). Head commit for run: e5b357c3dfd9066c6bd363e44533371d195e26e6 / cserwen [ISSUE #5838] retry to send when broker returns SYSTEM_BUSY (#5845) Report URL: https://github.com/apache/rocketmq/actions/runs/9026698686 With regards, GitHub Actions via GitBox
Re: [PR] [ISSUE #5923] Fix tiered store README.md error [rocketmq]
RongtongJin merged PR #8115: URL: https://github.com/apache/rocketmq/pull/8115 -- 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: commits-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
(rocketmq) branch develop updated: [ISSUE #5923] Fix tiered store README.md error (#8115)
This is an automated email from the ASF dual-hosted git repository. jinrongtong pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/rocketmq.git The following commit(s) were added to refs/heads/develop by this push: new 159a603219 [ISSUE #5923] Fix tiered store README.md error (#8115) 159a603219 is described below commit 159a603219e363e5f991a0c85213f6dc13f0a9be Author: yuz10 <845238...@qq.com> AuthorDate: Fri May 10 14:16:07 2024 +0800 [ISSUE #5923] Fix tiered store README.md error (#8115) --- tieredstore/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tieredstore/README.md b/tieredstore/README.md index d420494461..baeb56acc3 100644 --- a/tieredstore/README.md +++ b/tieredstore/README.md @@ -12,7 +12,7 @@ This article is a cookbook for RocketMQ tiered storage. Use the following steps to easily use tiered storage -1. Change `messageStorePlugIn` to `org.apache.rocketmq.tieredstore.MessageStoreExtend` in your `broker.conf`. +1. Change `messageStorePlugIn` to `org.apache.rocketmq.tieredstore.TieredMessageStore` in your `broker.conf`. 2. Configure your backend service provider. change `tieredBackendServiceProvider` to your storage medium implement. We give a default implement: POSIX provider, and you need to change `tieredStoreFilePath` to the mount point of storage medium for tiered storage. 3. Start the broker and enjoy! @@ -22,7 +22,7 @@ The following are some core configurations, for more details, see [TieredMessage | Configuration | Default value | Unit| Function | | --- |---| --- | --- | -| messageStorePlugIn | | | Set to org.apache.rocketmq.tieredstore.MessageStoreExtend to use tiered storage | +| messageStorePlugIn | | | Set to org.apache.rocketmq.tieredstore.TieredMessageStore to use tiered storage | | tieredMetadataServiceProvider | org.apache.rocketmq.tieredstore.metadata.DefaultMetadataStore | | Select your metadata provider | | tieredBackendServiceProvider| org.apache.rocketmq.tieredstore.provider.PosixFileSegment | | Select your backend service provider | | tieredStoreFilePath | | | Select the directory using for tiered storage, only for POSIX provider. |
[I] [Enhancement] ClientConfiguration Add namespace [rocketmq-clients]
zhaohai666 opened a new issue, #746: URL: https://github.com/apache/rocketmq-clients/issues/746 ### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Programming Language of the Client Node.js ### Summary The Java language already supports this namespace configuration addition, and I hope node js will also support it. ### Motivation The Java language already supports this namespace configuration addition, and I hope node js will also support it. ### Describe the Solution You'd Like ClientConfiguration Add namespace ### Describe Alternatives You've Considered ClientConfiguration Add namespace ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GH] (rocketmq): Workflow run "PUSH-CI" failed!
The GitHub Actions job "PUSH-CI" on rocketmq.git has failed. Run started by GitHub user RongtongJin (triggered by RongtongJin). Head commit for run: 159a603219e363e5f991a0c85213f6dc13f0a9be / yuz10 <845238...@qq.com> [ISSUE #5923] Fix tiered store README.md error (#8115) Report URL: https://github.com/apache/rocketmq/actions/runs/9028143323 With regards, GitHub Actions via GitBox
