[GitHub] [rocketmq] lukaszwawrzyk added a comment to the discussion: Introduce Bazel Steward - a tool for keeping dependencies up to date in Bazel

GitHub user lukaszwawrzyk added a comment to the discussion: Introduce Bazel Steward - a tool for keeping dependencies up to date in Bazel @ShadowySpirits Ok, it seems that the major problem is that bots may not push commits to the repository. But what about dependabot that you seem to be

[GitHub] [rocketmq] echooymxq added a comment to the discussion: ExamineConsumeStats这个API返回数据的问题

GitHub user echooymxq added a comment to the discussion: ExamineConsumeStats这个API返回数据的问题 可以用正则表达式取每一对{"brokerName":"broker-a","queueId":7,"topic":"evidence-sync-cloud"}:{"brokerOffset":0,"consumerOffset":0,"lastTimestamp":0}这样的数据，然后单独反序列化具体每一对数据。 GitHub link:

[GitHub] [rocketmq] fuyou001 added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊

GitHub user fuyou001 added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊 技术上，因历史原因，当前并没有做强制限制。延迟可以发普通消息、普通消息也可以发延迟消息。 但从运维角度，建议不要混用，避免给运维带来额外的成本。 GitHub link: https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5836285 This is an automatically sent email

[GitHub] [rocketmq] wushimang1 added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊

GitHub user wushimang1 added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊 我试过了，发送到普通主题也是一样能定时消费的，我看文档写的是3.x和4.x不强制校验，可以混用，但是我实测5.x也可以混用，不知道为什么 GitHub link: https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5834902 This is an automatically sent email

[GitHub] [rocketmq] quattro-abc added a comment to the discussion: CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER

GitHub user quattro-abc added a comment to the discussion: CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER > @quattro-abc How to solve it > > this is conf > > brokerClusterName = Cluster brokerName = rocket01 brokerId = -1 brokerRole = > ASYNC_MASTER

[GitHub] [rocketmq] yijieyu added a comment to the discussion: CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER

GitHub user yijieyu added a comment to the discussion: CODE: 2 DESC: [REJECTREQUEST]system busy, start flow control for a while BROKER okkk GitHub link: https://github.com/apache/rocketmq/discussions/6432#discussioncomment-5835918 This is an automatically sent email for

[GitHub] [rocketmq] echooymxq added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊

GitHub user echooymxq added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊 Broker应该是没有进行校验，如果是使用5.x，那么在Proxy层会进行主题消息类型的校验。 GitHub link: https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5837358 This is an automatically sent email for

[GitHub] [rocketmq] joeCarf added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊

GitHub user joeCarf added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊 我理解延迟消息只有被写到延迟主题中才会发挥作用。由于延迟消息的实现原理是延迟主题下的消息定时重新投递，所以如果发送到普通主题的话，应该与普通消息无异。 GitHub link: https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5834870 This is an automatically sent

[GitHub] [rocketmq] joeCarf added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊

GitHub user joeCarf added a comment to the discussion: 延迟消息不是只能发到延迟消息主题吗，为什么我的测试都可以啊 个人理解，欢迎指正～ GitHub link: https://github.com/apache/rocketmq/discussions/6717#discussioncomment-5834872 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an

[GitHub] [rocketmq] pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点

GitHub user pxd98 added a comment to the discussion: rocketmq 将从节点切换成主节点 我使用的rocketmq是4.9.1版本，暂时不考虑使用dledger方式 GitHub link: https://github.com/apache/rocketmq/discussions/6721#discussioncomment-5844454 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe,

[GitHub] [rocketmq] weihubeats edited a comment on the discussion: rocketmq broker keeps printing the following error: schedule CQ offset invalid. offset=62857, cqMinOffset=0, cqMaxOffset=0, queueId=2

GitHub user weihubeats edited a comment on the discussion: rocketmq broker keeps printing the following error: schedule CQ offset invalid. offset=62857, cqMinOffset=0, cqMaxOffset=0, queueId=2 The command sh bin/mqadmin getSyncStateSet finds the node **NotInSyncReplica**. Checking the sync

[GitHub] [rocketmq] weihubeats added a comment to the discussion: rocketmq broker keeps printing the following error: schedule CQ offset invalid. offset=62857, cqMinOffset=0, cqMaxOffset=0, queueId=2

GitHub user weihubeats added a comment to the discussion: rocketmq broker keeps printing the following error: schedule CQ offset invalid. offset=62857, cqMinOffset=0, cqMaxOffset=0, queueId=2 The command sh bin/mqadmin getSyncStateSet finds the node NotInSyncReplica. Checking the sync log has