apache / eventmesh

EventMesh is a new generation serverless event middleware for building distributed event-driven applications.
https://eventmesh.apache.org/
Apache License 2.0
1.61k stars 638 forks source link

[Question]creating too many RocketMQ connections #4629

Open zscomehuyue opened 10 months ago

zscomehuyue commented 10 months ago

Search before asking

Question

A project will have many consumer groups, which will create a lot of clients (including pubs and subs), as well as many ClientGroupWrappers, producers (can they be shared?), consumers, and broadcasts (why do they need to be created? I don't need to);

pandaapo commented 10 months ago

To be honest, I don't fully grasp the situation described in this issue, but I still want to learn as much as possible. For instance, what does 'broadcasts' refer to?

zscomehuyue commented 10 months ago
  1. 一个项目会很多的消费组,这样会创建很多的client(包含pub,sub),一个group创建一个ClientGroupWrapper,而一个ClientGroupWrapper,创建启动3个连接:proudcer(可以共享吗?),persistentMsgConsumer,broadCastMsgConsumer(为何需要创建那?我又不用);而该group的sub类型是SubscriptionMode.CLUSTERING,并不需要broadCastMsgConsumer,但是默认还是创建了该连接;
xwm1992 commented 10 months ago
  1. 一个项目会很多的消费组,这样会创建很多的client(包含pub,sub),一个group创建一个ClientGroupWrapper,而一个ClientGroupWrapper,创建启动3个连接:proudcer(可以共享吗?),persistentMsgConsumer,broadCastMsgConsumer(为何需要创建那?我又不用);而该group的sub类型是SubscriptionMode.CLUSTERING,并不需要broadCastMsgConsumer,但是默认还是创建了该连接;

1.目前是组代理的模式,一个组,共享一个rocketmq client 2.目前在做消费方建连的时候会初始化producer\persistConsumer\broadCastConsumer,是为了减少消费者的冷启动问题。

github-actions[bot] commented 6 months ago

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.