Re: [I] 求助 单机通过docker-compose部署5.1.3 [rocketmq-docker]
lorojunk commented on issue #88: URL: https://github.com/apache/rocketmq-docker/issues/88#issuecomment-1951795639 连接的服务应该是 8081 端口 -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[RESULT][VOTE]Release Apache RocketMQ 4.9.8 RC1
The Apache RocketMQ 4.9.8 vote is now closed and has passed with [3] binding +1s, [1] non-binding +1s and no 0 or -1: *Binding votes +1s:* ShannonDing(ding...@apache.org) Zhanhui Li(lizhan...@apache.org) Rongtong Jin(jinrongt...@apache.org) *Non-binding votes +1s:* Gaoyang Cai(csgyt...@163.com) The release will be published soon. Thanks, The Apache RocketMQ Team
[RESULT][VOTE]Release Apache RocketMQ 5.2.0 RC1
The Apache RocketMQ 5.2.0 vote is now closed and has passed with [3] binding +1s, [1] non-binding +1s and no 0 or -1: *Binding votes +1s:* ShannonDing(ding...@apache.org) Zhanhui Li(lizhan...@apache.org) Yubao Fu (fu...@apache.org ) *Non-binding votes +1s:* Gaoyang Cai(csgyt...@163.com) The release will be published soon. Thanks, The Apache RocketMQ Team
Re: [D] RocketMQ 5.x 消息粒度负载均衡 [rocketmq]
GitHub user Yelijah added a comment to the discussion: RocketMQ 5.x 消息粒度负载均衡 实测下来，顺序消息好像会在本地消费者执行失败一定次数后，其他消费者才能提取到 GitHub link: https://github.com/apache/rocketmq/discussions/7826#discussioncomment-8512935 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.x 消息粒度负载均衡 [rocketmq]
GitHub user lizhanhui added a comment to the discussion: RocketMQ 5.x 消息粒度负载均衡 > 我自己的理解是，对顺序队列，应该是能对message > group进行锁定，而不是对这个队列进行锁定。如果是给队列加锁，这岂不就是队列负载均衡了吗，若一个消费者hang住，也会导致整条队列的消息都得不到消费，跟消息粒度负载均衡定义的场景是不吻合的。 可以开个Improvement Proposal，实现这个feature GitHub link: https://github.com/apache/rocketmq/discussions/7826#discussioncomment-8513888 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
Re:[VOTE] Release Apache RocketMQ 4.9.8 RC1
+1 (Non-binding) I've checked: [OK] Checksums and PGP signatures are valid for Source package. [OK] Checksums and PGP signatures are valid for Binary package. [OK] License and Notice are correct in source package. [OK] All files have license headers in source package if necessary. [OK] No compiled archives bundled in source archive. [OK] Hash and Tag in GitHub repo is matching the current artifacts. [OK] The code can be built success in the source package. At 2024-02-13 18:17:38, "jinrongtong" wrote: >Hello RocketMQ Community, > >This is the vote for 4.9.8 of Apache RocketMQ. > >This release fixes some bugs to enhance stability. > >The artifacts: >https://dist.apache.org/repos/dist/dev/rocketmq/4.9.8-rc1/ > >The staging repo: >https://repository.apache.org/content/repositories/orgapacherocketmq-1309 > >Git tag for the release: >https://github.com/apache/rocketmq/tree/release-4.9.8 > >Hash for the release tag: >8b287928fb4c8c565282c019ef668c43e6eb3289 > >Release Notes: >https://rocketmq.apache.org/zh/release-notes/2024/01/29/4.9.8/ > > > >The artifacts have been signed with Key : >EC9F268B4C20590138B11FE701420E4292296EAE, which can be found in the keys file: >https://dist.apache.org/repos/dist/dev/rocketmq/KEYS > >Checklist for reference, >Note that this is not official policy but may help with checking releases. >Fill in the following: > >[] Checksums and PGP signatures are valid for Source package. >[] Checksums and PGP signatures are valid for Binary package. >[] Source code artifacts have correct names matching the current release. >[] Binary artifacts have correct names matching the current release. >[] License and Notice are correct in source package. >[] License and Notice are correct in binary package. >[] All files have license headers in source package if necessary. >[] No compiled archives bundled in source archive. >[] Hash and Tag in GitHub repo is matching the current artifacts. >[] The code can be built success in the source package. >[] Start nameserver and broker according to the quick-start >[] Run clusterList command to see if the version is correct > >And any other check point is welcomed and please feel free to reply to this >email, we sincerely hope to your feedback. > >The vote will be open for at least 72 hours or until 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:[VOTE] Release Apache RocketMQ 5.2.0 RC1
+1 (Non-binding) I checked: [OK] check NOTICE, should have a notice for third-party dependency if necessary [OK] extract the zip and check if the source version is correct [OK] verify the asc(PGP sign),SHA512 [OK] build the source, start nameserver and broker according to the quick-start [OK] run clusterList command to see if the version is correct At 2024-02-13 18:17:54, "jinrongtong" wrote: >Hello RocketMQ Community, > >This is the vote for 5.2.0 RC1 of Apache RocketMQ. > >This release includes fixes for many issues, enhancements to stability, and >also introduces some significant features, including the million-level queue >and the implementation of the jraft controller. > >The artifacts: >https://dist.apache.org/repos/dist/dev/rocketmq/5.2.0-rc1/ > > >The staging repo: >https://repository.apache.org/content/repositories/orgapacherocketmq-1303/ > > >Git tag for the release: >https://github.com/apache/rocketmq/releases/tag/rocketmq-all-5.2.0 > > >Hash for the release tag: >281a7b32f002019525cfa4dd4a4b983b653f070d > > >Release Notes: >https://rocketmq.apache.org/zh/release-notes/2024/01/30/5.2.0/ > > >The artifacts have been signed with Key : >EC9F268B4C20590138B11FE701420E4292296EAE, which can be found in the keys file: >https://dist.apache.org/repos/dist/dev/rocketmq/KEYS > > >Checklist for reference, >Note that this is not an official policy but may help with checking releases. > > >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 >[ ] build the source, start nameserver and broker according to the quick-start >[ ] run clusterList command to see if the version is correct > > >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:[VOTE] Release Apache RocketMQ 4.9.8 RC1
+1，I checked [OK] Hash and Tag in GitHub repo is matching the current artifacts. [OK] The code can be built success in the source package. [OK] Start nameserver and broker according to the quick-start [OK] Run clusterList command to see if the version is correct At 2024-02-13 18:17:38, "jinrongtong" wrote: Hello RocketMQ Community, This is the vote for 4.9.8 of Apache RocketMQ. This release fixes some bugs to enhance stability. The artifacts: https://dist.apache.org/repos/dist/dev/rocketmq/4.9.8-rc1/ The staging repo: https://repository.apache.org/content/repositories/orgapacherocketmq-1309 Git tag for the release: https://github.com/apache/rocketmq/tree/release-4.9.8 Hash for the release tag: 8b287928fb4c8c565282c019ef668c43e6eb3289 Release Notes: https://rocketmq.apache.org/zh/release-notes/2024/01/29/4.9.8/ The artifacts have been signed with Key : EC9F268B4C20590138B11FE701420E4292296EAE, which can be found in the keys file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS Checklist for reference, Note that this is not official policy but may help with checking releases. Fill in the following: [] Checksums and PGP signatures are valid for Source package. [] Checksums and PGP signatures are valid for Binary package. [] Source code artifacts have correct names matching the current release. [] Binary artifacts have correct names matching the current release. [] License and Notice are correct in source package. [] License and Notice are correct in binary package. [] All files have license headers in source package if necessary. [] No compiled archives bundled in source archive. [] Hash and Tag in GitHub repo is matching the current artifacts. [] The code can be built success in the source package. [] Start nameserver and broker according to the quick-start [] Run clusterList command to see if the version is correct And any other check point is welcomed and please feel free to reply to this email, we sincerely hope to your feedback. The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Thanks, The Apache RocketMQ Team
