+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.
> [+]
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
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
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
GitHub user cserwen edited a comment on the discussion:
pop消费模式下消费速度和消费者数量以及topic queue数量的关系
锁竞争影响性能，理论上得需要很高并发，4个并发显然不够，并且 Broker 处理拉取请求的并发是有限制的，默认最多会有 32
个线程在竞争，我理解也不严重（每个拉取请求获取锁后都是从内存中读数据，速度非常快，并不会长期持有锁）
况且很多时候消费瓶颈不在拉取上，而在消费逻辑上，从生产环境数据来看，一般每个 Broker 上设置单个 queue 足够
GitHub link:
GitHub user cserwen added a comment to the discussion:
pop消费模式下消费速度和消费者数量以及topic queue数量的关系
锁竞争影响性能，理论上得需要很高并发，4个并发显然不够，并且 Broker 处理拉取请求的并发是有限制的，默认最多会有 32
个线程在竞争，我理解也不严重（每个拉取请求获取锁后都是从内存中读数据，速度非常快，并不会长期持有锁）
况且很多时候消费瓶颈不在拉取上，而在消费逻辑上，从生产环境数据来看，一般采用单个 queue 足够
GitHub link:
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
