Re: [VOTE] Release Apache RocketMQ EventBridge 1.1.0
+1 On Sat, Mar 9, 2024 at 2:22 PM 沈林 <2011shen...@gmail.com> wrote: > Hello RocketMQ Community, > > This is the vote for 1.1.0 release of Apache RocketMQ EventBridge. In this > version, We will be releasing some functionality of EventBridge. Including: > [+] The runtime of eventbridge. > [+] Built in demo use case: send events,filter,transform and write to file. > [+] Supports built-in databases without the need to build MySQL. > [+] Add file sink connector. > [+] Add e2e test case. > [+] Add git workflows check when creating the pull request. > > According to the last suggestion, a new version to be released was > generated through github workflows: > > The artifact: > > https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-eventbridge/1.1.0-rc1/ > > > Git tag for the release: > > https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0 > > Hash for the release tag: 0008e7826f0cbf2e61f14565a5229e97be42c8d7 > > Relate Notes: > > https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0 > > > The artifacts have been signed with Key : > F1CF7B3B63003270B3EB5B0B66BFD9C8461F1A4A, which can be found in the keys > file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS > > > Fill in the following: > [+] check LICENSE, should be Apache V2 > [+] check NOTICE, should have a notice for third-party dependency if > necessary > [+] extract the zip and check if the source version is correct > [+] verify the asc(PGP sign),SHA512 > > > The vote will be open for at least 72 hours or until the necessary number > of votes are reached. > Please vote accordingly: > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache RocketMQ Team > > 沈林 <2011shen...@gmail.com> 于2024年2月18日周日 09:02写道： > > > Hello RocketMQ Community, > > > > This is the vote for 1.1.0 release of Apache RocketMQ EventBridge. In > this > > version, We will be releasing some functionality of EventBridge. > Including: > > [+] The runtime of eventbridge. > > [+] Built in demo use case: send events,filter,transform and write to > file. > > [+] Supports built-in databases without the need to build MySQL. > > [+] Add file sink connector. > > [+] Add e2e test case. > > [+] Add git workflows check when creating the pull request. > > > > The artifact: > > > > > https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-eventbridge/1.1.0-rc1/ > > > > > > Git tag for the release: > > > > > https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0 > > > > Hash for the release tag: 6a852f22fb55a2c8c3e80070100547eb9b1a9b51 > > > > Relate Notes: > > > > > https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0 > > > > > > The artifacts have been signed with Key : > > F1CF7B3B63003270B3EB5B0B66BFD9C8461F1A4A, which can be found in the keys > > file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS > > > > > > Fill in the following: > > [+] check LICENSE, should be Apache V2 > > [+] check NOTICE, should have a notice for third-party dependency if > > necessary > > [+] extract the zip and check if the source version is correct > > [+] verify the asc(PGP sign),SHA512 > > > > > > The vote will be open for at least 72 hours or until the necessary number > > of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > The Apache RocketMQ Team > > >
Re: [D] message store is not writeable, so putMessage is forbidden [rocketmq]
GitHub user MmringZee added a comment to the discussion: message store is not writeable, so putMessage is forbidden yaml是不是不该直接以代码的形式放进来... GitHub link: https://github.com/apache/rocketmq/discussions/7950#discussioncomment-8869928 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] message store is not writeable, so putMessage is forbidden [rocketmq]
GitHub user MmringZee edited a discussion: message store is not writeable, so
putMessage is forbidden
我在使用官方quickstart提供的demo访问部署在k8s上的单节点mq时,程序报错:
`2024-03-22T02:43:27.134+08:00 ERROR 1 --- [nio--exec-2]
c.p.r.controller.ProduceController : Failed to send message
org.apache.rocketmq.client.java.exception.InternalErrorException:
[request-id=406e0549-b4df-4aa7-b0ce-fc13878c83c1, response-code=50001]
org.apache.rocketmq.proxy.common.ProxyException: service not available now. It
may be caused by one of the following reasons: the broker's disk is full [CL:
0.91 CQ: 0.91 INDEX: 0.91], messages are put to the slave, message store has
been shut down, etc.`
到broker.log查看,显示:
`
message store is not writeable, so putMessage is forbidden
`
这是yaml:
```
apiVersion: v1
kind: ConfigMap
metadata:
name: rmq-proxy
namespace: pscp-rocketmq
data:
rmq-proxy.json: |
{
"rocketMQClusterName": "EkmsCluster",
"grpcServerPort": 8081,
"remotingListenPort": 8080
}
---
apiVersion: v1
kind: ConfigMap
metadata:
name: rocketmq-config
namespace: pscp-rocketmq
data:
broker-a.properties: |
brokerClusterName = EkmsCluster
brokerName = broker-a
brokerId = 0
deleteWhen = 04
fileReservedTime = 48
brokerRole = ASYNC_MASTER
flushDiskType = ASYNC_FLUSH
storePathRootDir=/data/rocketmq/store
brokerRole=MASTER
autoCreateSubscriptionGroup=true
aclEnable=false
brokerIP1 = broker-a.pscp-rocketmq.svc.cluster.local
---
apiVersion: v1
kind: Service
metadata:
labels:
app: broker-a
name: broker-a
namespace: pscp-rocketmq
spec:
type: ClusterIP
ports:
- port: 10911
targetPort: 10911
name: broker-port
- port: 8081
targetPort: 8081
name: broker-proxy
- port: 8080
targetPort: 8080
name: proxy-port
selector:
app: broker-a
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: broker-a
namespace: pscp-rocketmq
spec:
serviceName: broker-a
replicas: 1
selector:
matchLabels:
app: broker-a
template:
metadata:
labels:
app: broker-a
spec:
tolerations:
- key: dgw.xxx.com.cn
operator: Equal
value: 'true'
effect: NoSchedule
imagePullSecrets:
- name: pscp-rocketmq-registrydev
containers:
- name: broker-a
image: registrydev.xxx.com.cn/pscp/rocketmq-5.1.4:v1
command: ["sh","-c","/usr/local/rocketmq-5.1.4/bin/mqbroker -c
/usr/local/rocketmq-5.1.4/conf/broker-a.properties --enable-proxy -n
mqnamesrv.pscp-rocketmq.svc.cluster.local:9876"]
imagePullPolicy: IfNotPresent
env:
- name: JAVA_OPT
value: "-server -XX:ParallelGCThreads=1 -Xms1g -Xmx1g -Xmn512m"
resources:
requests:
memory: 128Mi
volumeMounts:
- mountPath: /root/logs
name: pscp-rocketmq-cifs
subPath: rocketmq-brokera-logs
- mountPath: /data/rocketmq
name: pscp-rocketmq-cifs
subPath: rocketmq-brokera-store
- name: broker-config
mountPath: /usr/local/rocketmq-5.1.4/conf/broker-a.properties
subPath: broker-a.properties
- name: rmq-proxy
mountPath: /usr/local/rocketmq-5.1.4/conf/rmq-proxy.json
subPath: rmq-proxy.json
volumes:
- name: broker-config
configMap:
name: rocketmq-config
- name: rmq-proxy
configMap:
name: rmq-proxy
volumeClaimTemplates:
- metadata:
name: pscp-rocketmq-cifs
annotations:
volume.beta.kubernetes.io/storage-class: "pscp-cifs-1"
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 50Gi
```
GitHub link: https://github.com/apache/rocketmq/discussions/7950
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] message store is not writeable, so putMessage is forbidden [rocketmq]
GitHub user MmringZee deleted a comment on the discussion: message store is not writeable, so putMessage is forbidden yaml是不是不该直接以代码的形式放进来... GitHub link: https://github.com/apache/rocketmq/discussions/7950#discussioncomment-8869928 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] pop消费模式下消费速度和消费者数量以及topic queue数量的关系 [rocketmq]
GitHub user cserwen edited a comment on the discussion: pop消费模式下消费速度和消费者数量以及topic queue数量的关系 锁竞争影响性能，理论上得需要很高并发，4个并发显然不够，并且 Broker 处理拉取请求的并发是有限制的，默认最多会有 32 个线程在竞争，我理解也不严重（每个拉取请求获取锁后都是从内存中读数据，速度非常快，并不会长期持有锁） 况且很多时候消费瓶颈不在拉取上，而在消费逻辑上，从生产环境数据来看，一般每个 Broker 上设置单个 queue 足够 GitHub link: https://github.com/apache/rocketmq/discussions/7942#discussioncomment-8872789 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] pop消费模式下消费速度和消费者数量以及topic queue数量的关系 [rocketmq]
GitHub user cserwen added a comment to the discussion: pop消费模式下消费速度和消费者数量以及topic queue数量的关系 锁竞争影响性能，理论上得需要很高并发，4个并发显然不够，并且 Broker 处理拉取请求的并发是有限制的，默认最多会有 32 个线程在竞争，我理解也不严重（每个拉取请求获取锁后都是从内存中读数据，速度非常快，并不会长期持有锁） 况且很多时候消费瓶颈不在拉取上，而在消费逻辑上，从生产环境数据来看，一般采用单个 queue 足够 GitHub link: https://github.com/apache/rocketmq/discussions/7942#discussioncomment-8872789 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 5.1.4] 内外网隔离的情况下，怎么做到内外网都可以通过MQ收发消息 [rocketmq]
GitHub user jimchanghub added a comment to the discussion: [RocketMQ 5.1.4] 内外网隔离的情况下，怎么做到内外网都可以通过MQ收发消息 我也碰到同样的问题了，请问有办法解决吗 GitHub link: https://github.com/apache/rocketmq/discussions/7558#discussioncomment-8873224 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
