[GitHub] [rocketmq] drpmma edited a comment on issue #3378: Is it risky to run with jdk 11 ?

drpmma edited a comment on issue #3378: URL: https://github.com/apache/rocketmq/issues/3378#issuecomment-931861028 rocketmq server is completely compatible with jdk11, and we have already run it with jdk11 in production. -- This is an automated message from the Apache Git Service. To

[GitHub] [rocketmq] drpmma edited a comment on issue #3378: Is it risky to run with jdk 11 ?

drpmma edited a comment on issue #3378: URL: https://github.com/apache/rocketmq/issues/3378#issuecomment-931861028 rocketmq is completely compatible with jdk11, and we have already run it with jdk11 in production. -- This is an automated message from the Apache Git Service. To respond

[GitHub] [rocketmq] drpmma commented on issue #3378: Is it risky to run with jdk 11 ?

drpmma commented on issue #3378: URL: https://github.com/apache/rocketmq/issues/3378#issuecomment-931861028 rocketmq is completely compatible with jdk11, and we are already running it with jdk11 in production. -- This is an automated message from the Apache Git Service. To respond to

Re: [DISCUSS] RIP-25 Ease of Use Improvements on RocketMQ Client API

Agree, exiting API set require substantial improvement, to further refine RocketMQ model. On Fri, Oct 1, 2021 at 9:37 AM yukon wrote: > Great catch, we will draft a new version of client APIs in few days~ > > On Wed, Sep 29, 2021 at 4:19 PM dongeforever > wrote: > > > The idea is OK. > > And

Re: RIP 24: Introduce multi-protocol support

Hello, community, Any further opinions about this RIP? If not, we would like to propose a draft of the new protocol spec. Regards, yukon On Tue, Sep 28, 2021 at 8:14 AM vongosling wrote: > Subscribe to the dev mailing list before sending emails. Otherwise, emails > cannot be sent to the

Re: [DISCUSS] RIP-25 Ease of Use Improvements on RocketMQ Client API

Great catch, we will draft a new version of client APIs in few days~ On Wed, Sep 29, 2021 at 4:19 PM dongeforever wrote: > The idea is OK. > And the same time, it is better to show more details. Maybe drafting the > new API interface is a good way to dive deep. > > caigy 于2021年9月28日周二

[GitHub] [rocketmq-streams] duhenglucky opened a new issue #80: Pull Consumer integration

duhenglucky opened a new issue #80: URL: https://github.com/apache/rocketmq-streams/issues/80 Compared with Push consumer, pull consumer more flexible in offset management, so It is recommended to use Pullconsumer instead of PushConsumer -- This is an automated message from the Apache

[GitHub] [rocketmq-exporter] maixiaohai closed issue #72: Error when building the project

maixiaohai closed issue #72: URL: https://github.com/apache/rocketmq-exporter/issues/72 -- 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:

[GitHub] [rocketmq-exporter] maixiaohai commented on pull request #73: fix the error when building the project

maixiaohai commented on pull request #73: URL: https://github.com/apache/rocketmq-exporter/pull/73#issuecomment-931332310 merged~ -- 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

[GitHub] [rocketmq-exporter] maixiaohai merged pull request #73: fix the error when building the project

maixiaohai merged pull request #73: URL: https://github.com/apache/rocketmq-exporter/pull/73 -- 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:

[GitHub] [rocketmq] maixiaohai commented on issue #3390: I want to participate in the development of 5.0

maixiaohai commented on issue #3390: URL: https://github.com/apache/rocketmq/issues/3390#issuecomment-931318903 Welcome~ @Cc -- 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

[GitHub] [rocketmq-client-go] maixiaohai commented on issue #725: Why specify Broker when creating a topic?

maixiaohai commented on issue #725: URL: https://github.com/apache/rocketmq-client-go/issues/725#issuecomment-931310230 1. In production Cluster, topic do not support auto-create because of multi-tenant 2. When a cluster has so many brokers, how to decide which brokers to select --

[GitHub] [rocketmq-client-go] njutsiang opened a new issue #725: Why specify Broker when creating a topic?

njutsiang opened a new issue #725: URL: https://github.com/apache/rocketmq-client-go/issues/725 https://github.com/apache/rocketmq-client-go/blob/406561060cb7d27c84df7f146a5ef003122c9cda/examples/admin/topic/main.go#L43 I'm very sorry, but I don't understand why this is so?

[GitHub] [rocketmq-dashboard] StyleTang edited a comment on issue #24: Consider whether to add query message by topic and tags

StyleTang edited a comment on issue #24: URL: https://github.com/apache/rocketmq-dashboard/issues/24#issuecomment-931255948 Thanks for your request but we may not add this feature. Message tags is designed for message filter [Message

[GitHub] [rocketmq-dashboard] StyleTang commented on issue #24: Consider whether to add query message by topic and tags

StyleTang commented on issue #24: URL: https://github.com/apache/rocketmq-dashboard/issues/24#issuecomment-931255948 Thanks for your request but we may not add this feature. Message tags is designed for message filter [Message

[GitHub] [rocketmq] panzhi33 commented on issue #3391: Probably,LatencyFaultToleranceImpl#pickOneAtLeast result isn't first one When latency items size great to 3.

panzhi33 commented on issue #3391: URL: https://github.com/apache/rocketmq/issues/3391#issuecomment-931198769 > 在重试量足够大而且数量变动频繁的情况下该算法没有办法保证执行的顺序 他是以broker来统计的，除非发生扩容缩容等一些情况，所以整个faultItemTable的数量是固定的，但是每个FaultItem里面的变量在每一次发完消息后就会更新，因此无法做到顺序。不建议打开这个策略 -- This is an automated

[GitHub] [rocketmq-client-nodejs] tong3jie commented on issue #12: Can't compile with node12

tong3jie commented on issue #12: URL: https://github.com/apache/rocketmq-client-nodejs/issues/12#issuecomment-931187058 kafka吧，这个项目估计又要烂尾 -- 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

[GitHub] [rocketmq] soci166 commented on issue #3391: Probably,LatencyFaultToleranceImpl#pickOneAtLeast result isn't first one When latency items size great to 3.

soci166 commented on issue #3391: URL: https://github.com/apache/rocketmq/issues/3391#issuecomment-931183397 在重试量足够大而且数量变动频繁的情况下该算法没有办法保证执行的顺序 -- 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

[GitHub] [rocketmq] panzhi33 commented on issue #3391: Probably,LatencyFaultToleranceImpl#pickOneAtLeast result isn't first one When latency items size great to 3.

panzhi33 commented on issue #3391: URL: https://github.com/apache/rocketmq/issues/3391#issuecomment-931169343 >  > > 我的理解是错误重试机制在已经分配了权重的情况下应该要按照权重的顺序来执行而不应该保留这种随机性

[GitHub] [rocketmq] soci166 commented on issue #3391: Probably,LatencyFaultToleranceImpl#pickOneAtLeast result isn't first one When latency items size great to 3.

soci166 commented on issue #3391: URL: https://github.com/apache/rocketmq/issues/3391#issuecomment-931126753  我的理解是错误重试机制在已经分配了权重的情况下应该要按照权重的顺序来执行而不应该保留这种随机性 -- This

[GitHub] [rocketmq] panzhi33 commented on issue #3391: Probably,LatencyFaultToleranceImpl#pickOneAtLeast result isn't first one When latency items size great to 3.

panzhi33 commented on issue #3391: URL: https://github.com/apache/rocketmq/issues/3391#issuecomment-931097858 

[RESULT][VOTE]: Release Apache RocketMQ Dashboard 1.0.0 RC1

The Apache RocketMQ Dashboard 1.0.0 vote is now closed and has passed with [3] binding +1s,[1] non-binding +1s and no 0 or -1: *Binding votes +1s:* RongtongJin(jinrongt...@apache.org) ShannonDing(ding...@apache.org) Du Heng(duhengfore...@apache.org) *Non-binding votes +1s:* unclerangoo The

[GitHub] [rocketmq] soci166 commented on issue #3391: Probably,LatencyFaultToleranceImpl#pickOneAtLeast result isn't first one When latency items size great to 3.

soci166 commented on issue #3391: URL: https://github.com/apache/rocketmq/issues/3391#issuecomment-930914885  the earliest start time item will be last execution is expected?

[GitHub] [rocketmq] panzhi33 commented on issue #3391: Probably,LatencyFaultToleranceImpl#pickOneAtLeast result isn't first one When latency items size great to 3.

panzhi33 commented on issue #3391: URL: https://github.com/apache/rocketmq/issues/3391#issuecomment-930833063  polling algorithm, and only get from the first half，this is