Re: [VOTE] RIP-19 RocketMQ Pop Consuming

[liqipeng]

+1
> 在 2021年1月18日，下午2:37，heng du  写道：
> 
> Hi RocketMQ Community,
> 
> This is the vote for the kickoff of RIP-19 RocketMQ Pop Consuming.
> 
> In order to better implement a lightweight client, @ayanamist proposes a
> new consumption model, and at the same time transfers the load balancing
> logic of the original client to the broker, which not only solves the
> original queue occupancy problem but also It can also avoid the consumption
> delay caused by a certain consumer hangs.
> 
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> 
> 
> 
> Best Regards!
> Henry
> 
> ayanamist  于2021年1月8日周五 上午11:25写道：
> 
>> # RIP-19 RocketMQ Pop Consuming
>> 
>> # Status
>> 
>> - Current State: Proposed
>> - Authors: [ayanamist]([
>> https://github.com/ayanamist/](https://github.com/ayanamist/))
>> - Shepherds: [duhengforever]([
>> https://github.com/duhenglucky/](https://github.com/duhengforever/))
>> - Mailing List discussion: dev@rocketmq.apache.org;
>> us...@rocketmq.apache.org
>> - Pull Request: RIP-19
>> - Released: -
>> 
>> # Background & Motivation
>> 
>> ### What do we need to do
>> 
>> - Will we add a new module?
>> 
>>No.
>> 
>> - Will we add new APIs?
>> 
>>Yes.
>> 
>> - Will we add new feature?
>> 
>>Yes.
>> 
>> ### Why should we do that
>> 
>> - Are there any problems of our current project?
>> 
>>The current subscription load balancing strategy is based on the
>> dimension of message queue. All behaviors are owned by the client side.
>> There are three main steps:
>> 
>>1. Each consumer regularly obtains the total number of topic message
>> queues and all consumers.
>>2. Using a general algorithm to sort the queues by consumer ip and
>> queue index to calculate which message queue is allocated to which
>> consumer.
>>3. Each consumer pulls messages using allocated orders described above.
>> 
>>According to this allocation method, if an abnormality occurs in a
>> consumer (the application itself is abnormal, or a broker is upgrading) so
>> that it causes slow subscription, messages will be accumulated, but this
>> queue will not be re-allocated to another consumer, so the accumulation
>> will become more and more serious.
>> 
>> 
>>Chinese version:
>> 
>>当前的消费负载均衡策略是以队列的维度来进行，所有行为全部是由客户端主动来完成，主要分为三步：
>> 
>>1. 每个consumer定时去获取消费的topic的队列总数，以及consumer总数
>>2. 将队列按编号、consumer按ip排序，用统一的分配算法计算该consumer分配哪些消费队列
>>3. 每个consumer去根据算法分配出来的队列，拉取消息消费
>> 
>> 
>> 
>> 按照这个分配方式，如果有一个队列有异常（应用自身异常，或某个broker在升级）导致消费较慢或者停止，该队列会出现堆积现象，因为队列不会被分配给其他机器，因此如果长时间不处理，队列的堆积会越来越严重。
>> 
>> - What can we benefit proposed changes?
>> 
>>The accumulated messages will be subscribed by other consumers if one
>> consumer behaves abnormally.
>> 
>>Chinese version:
>> 
>>在某个队列消费异常的情况下，可以快速的由其它消费者接手进行消费，缓解堆积状态。
>> 
>> # Goals
>> 
>> - What problem is this proposal designed to solve?
>> 
>>The accumulated messages will be subscribed by other consumers if one
>> consumer behaves abnormally.
>> 
>>Chinese version:
>> 
>>在某个队列消费异常的情况下，可以快速的由其它消费者接手进行消费，缓解堆积状态。
>> 
>> - To what degree should we solve the problem?
>> 
>>This RIP must guarantee below point:
>> 
>>1. High availablity: Subscription of one message queue will not be
>> affected by single consumer failure.
>>2. High performance: This implementation affects latency and throughput
>> less than 10%.
>> 
>> 
>>Chinese version:
>> 
>>新方案需要保证两点：
>> 
>>1. 高可用：单一队列的消费能力不受某个消费客户端异常的影响
>>2. 高性能：POP订阅对消息消费的延迟和吞吐的影响在10%以内
>> 
>> # Non-Goals
>> 
>> - What problem is this proposal NOT designed to solve?
>> 
>>Improve client-side load balancing.
>> 
>> - Are there any limits of this proposal?
>> 
>>Nothing specific.
>> 
>> # Changes
>> 
>> ## Architecture
>> 
>> Current "Pull mode":
>> ![pull](
>> 
>> https://user-images.githubusercontent.com/406779/103756075-cc93b900-5049-11eb-8fae-cfe5398ebaad.png
>> )
>> 
>> Proposed "Pop mode":
>> ![pop](
>> 
>> https://user-images.githubusercontent.com/406779/103757230-6d36a880-504b-11eb-95d5-7e8cff8cdef1.png
>> )
>> 
>> Move inter-queue balance of one topic from client side to server side.
>> Clients make pull request without specified queues to broker, and broker
>> fetch messages from queues internally and returns, which ensures one queue
>> will be consumed by multiple clients. The whole behavior is like a queue
>> pop process.
>> 
>> It will add a new request command querying queue assignments in broker, and
>> add pop-feature-support flag to pull request which makes broker use pop
>> mode.
>> 
>> ## Interface Design/Change
>> 
>> - Method signature changes
>> 
>>Nothing specific.
>> 
>> - Method behavior changes
>> 
>>Nothing specific.
>> 
>> - CLI command changes
>> 
>>Add `setConsumeMode` for admin to switch between old pull mode and new
>> pop mode for one subscription.
>> 
>> - Log 

Re: [VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

[liqipeng]

+1, 
I checked
-  Checksums and PGP signatures are valid for Source package.
-  Checksums and PGP signatures are valid for Binary package.
-  License and Notice are correct in source package.
-  No compiled archives bundled in source archive.
-  Hash and Tag in GitHub repo is matching the current artifacts.
-  Source code artifacts have correct names matching the current release.
-  Binary artifacts have correct names matching the current release.


> 在 2020年4月7日，上午9:44，ShannonDing  写道：
> 
> Hello RocketMQ Community,
> This is the vote for version 2.2.0 of Apache RocketMQ Client CPP.
> This release support TLS mode with OpenSSL for sending messages in sync model 
> and consuming messages by push model and use an separate producer to send 
> trace messages. 
> 
> 
> The artifacts:
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.2.0-rc1/
> Git tag for the release:
> https://github.com/apache/rocketmq-client-cpp/releases/tag/2.2.0
> Hash for the release tag:
> 6579eb637f81bca29f59f1e8645897a8c12a0871
> Release Notes:
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.2.0/
> The artifacts have been signed with Key :
> BC9E172DE1BA5B24EBB4A628177B55985D75751B, 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.
> 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 Client Go Native 2.0.0.

[liqipeng]

+1 
I checked
- Checksums and PGP signatures are valid for Source package.
-  License and Notice are correct in source 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.
> 在 2020年3月31日，下午9:35，ShannonDing  写道：
> 
> Hello RocketMQ Community,
> 
> 
> This is the vote for version 2.0.0 of Apache RocketMQ Client Go Native.
> For the first product ready RocketMQ Client in pure go, it supports almost 
> the full features of Apache RocketMQ, such as pub and sub messages, ACL, 
> message tracing and so on.
> The artifacts:
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-go/2.0.0-rc3/
> Git tag for the release:
> https://github.com/apache/rocketmq-client-go/releases/tag/v2.0.0
> Hash for the release tag:
> be579956f83854915f9742578e8db81860b71112
> Release Notes:
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.0.0/
> The artifacts have been signed with Key :
> BC9E172DE1BA5B24EBB4A628177B55985D75751B, 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.
> [ ]  Source code artifacts have correct names matching the current release.
> [ ]  License and Notice are correct in source 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.
> As we don’t release binary package for Apache RocketMQ Go SDK, the binary 
> package checklist should not be followed.
> 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 4.7.0 RC1

[liqipeng]

+1 binding
[ok]  Checksums and PGP signatures are valid for Source package.
[ok]  Checksums and PGP signatures are valid for Binary package.
[ok]  Source code artifacts have correct names matching the current release.
[ok]  Binary artifacts have correct names matching the current release.
[ok]  License and Notice are correct in source package.
[ok]  License and Notice are correct in binary package.
[ok]  No compiled archives bundled in source archive.


> 在 2020年3月5日，下午9:17，Rongtong Jin  写道：
> 
> []  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

Re: [VOTE]Release RocketMQ Spring 2.1.0 RC1

[liqipeng]

+1
checked
[1]  Source code artifacts have correct names matching the current release.
[2]  License and Notice is ok 
[3]  The code can be built success.
> 在 2020年2月13日，下午2:00，Rongtong Jin  写道：
> 
> Hello RocketMQ Community,
> 
> 
> 
> 
> 
> 
> 
> This is the vote for the 2.1.0 release of Apache rocketmq-spring
> 
> 
> 
> 
> 
> 
> 
> The artifacts:
> 
> 
> 
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-spring/2.1.0-rc1/
> 
> 
> 
> 
> 
> 
> 
> The staging repo:
> 
> 
> 
> 
> https://repository.apache.org/content/repositories/orgapacherocketmq-1040
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Git tag for the release:
> 
> 
> 
> 
> https://github.com/apache/rocketmq-spring/releases/tag/rocketmq-spring-all-2.1.0
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Hash for the release tag:
> 
> 
> 
> 
> 6c8fc6ef596f114dfbaf6bbcc077eefb73b7
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Release Notes:
> 
> 
> 
> 
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-spring-2.1.0/
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> The artifacts have been signed with Key :
> 
> 
> 
> 
> D606079AF789227A1F39928A02C8C9527DDD1959, 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.
> 
> [ ]  Source code artifacts have correct names matching the current release.
> 
> [ ]  License and Notice are correct in source 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.
> 
> 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 a 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.6.1 RC1

[liqipeng]

+1  (binding)

I checked:
[1] license  ok 
[2] release notice   ok 
[3] admin tools test  ok 
[4] send message   ok 
[5] receive message  ok 
[6] no unexpected binary files

> 在 2020年2月7日，下午12:41，金融通  写道：
> 
> Hello RocketMQ Community,
> 
> 
> 
> This is the vote for 4.6.1 of Apache RocketMQ.
> 
> 
> 
> This release made some enhancements, such as refactoring the logic of 
> updating consume offset for pull consumer, using IPv4 first when choosing 
> local IP, etc. This release also fixed some issues about pull consume, 
> message tracing, transactional messages, etc. 
> 
> 
> 
> 
> The artifacts:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/4.6.1-rc1/
> 
> 
> 
> 
> The staging repo:
> 
> https://repository.apache.org/content/repositories/orgapacherocketmq-1039
> 
> 
> 
> Git tag for the release:
> 
> https://github.com/apache/rocketmq/tree/release-4.6.1
> 
> 
> 
> Hash for the release tag:
> 
> 73bb4b402a5da02faf9feded8f4d79dd1ba88348
> 
> 
> 
> Release Notes:
> 
> https://rocketmq.apache.org/release_notes/release-notes-4.6.1/
> 
> 
> 
> The artifacts have been signed with Key :
> 
> D606079AF789227A1F39928A02C8C9527DDD1959, which can be found in the keys file:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
> 
> 
> 
> 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 Client CPP 1.2.4 RC1.

[liqipeng]

+1
> 在 2019年11月14日，上午11:44，ShannonDing  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for version 1.2.4 of Apache RocketMQ Client CPP.
> 
> The artifacts:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.4-rc1/
> 
> Git tag for the release:
> 
> https://github.com/apache/rocketmq-client-cpp/releases/tag/1.2.4
> 
> Hash for the release tag:
> 
> bc369cdb1ffbe0dc710d8359c28ec36f4b94188c
> 
> Release Notes:
> 
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.4/
> 
> The artifacts have been signed with Key :
> 
> BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
> 
> 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][DISCUSS][RIP-17]RocketMQ HTTP Proxy Support

[liqipeng]

+1
> 在 2019年9月16日，下午6:57，heng du  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the kickoff of RIP-17 RocketMQ HTTP Proxy Support
> 
> RocketMQ has different clients written in different languages. In order to 
> meet the needs of heterogeneous systems to access RocketMQ, this proposal 
> solves this problem by adding an HTTP proxy module. At the same time, some 
> logic such as flow control/ACL on the broker and some processing logic on the 
> client can be moved to the proxy, which makes the broker and client lighter.
> 
> 
> The vote will be open for at least 72 hours or until a necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve 
> [ ] +0 no opinion 
> [ ] -1 disapprove with the reason
> 
> 
> Thanks,
> The Apache RocketMQ Team
> 
> heng du mailto:duhengfore...@gmail.com>> 
> 于2019年9月16日周一 下午6:55写道：
> @aliomaidi419
> 
> producer 跟 consumer端都可以使用http-proxy
> 
> huzongt...@cmss.chinamobile.com  
> mailto:huzongt...@cmss.chinamobile.com>> 
> 于2019年9月12日周四 上午10:47写道：
> This rip sounds very wonderful.It make RocketMQ may access clients written in 
> different languages.We can join in this rip together.
> 
> 
> 
> huzongt...@cmss.chinamobile.com 
> 
> From: heng du
> Date: 2019-09-12 09:41
> To: dev; users
> Subject: [DISCUSS][RIP-17]RocketMQ HTTP Proxy Support
> Dear Apache RocketMQ Community:
> 
> We would like to propose a RIP-17 about RocketMQ HTTP Proxy.
> 
> RocketMQ may access clients written in different languages. In order to meet 
> the needs of heterogeneous systems to access RocketMQ, this proposal solves 
> this problem by adding an HTTP proxy module. At the same time, some logic 
> such as flow control/ACL on the broker and some process logic on the client 
> can be moved to the proxy, which makes the broker and client lighter.
> 
> So we would like to provide an HTTP proxy to provide a proxy for HTTP so that 
> users can quickly access the RocketMQ with a lightweight HTTP client.
> 
> The following is the relevant information about this RIP and we are listed 
> directly below for your convenience, hope everyone can give more suggestions. 
> 
> Thanks,
> The Apache RocketMQ Team
> 
> Status
> ●  Current State: Proposed
> ●  Authors: qqeasonchen
> ●  Shepherds: duhengforever
> ●  Mailing List discussion: dev@rocketmq.apache.org 
> ; us...@rocketmq.apache.org 
> 
> ●  Pull Request: RIP-17
> ●  Released: 4.7.0（rocketmq-external first）
> Background & Motivation
> What do we need to do
> 
> RocketMQ may access clients written in different languages. In order to meet 
> the needs of heterogeneous systems to access RocketMQ, this proposal solve 
> this problem by adding HTTP proxy module. At the same time, some logic such 
> as flow control/ACL on broker and some process logic on client can be moved 
> to proxy, which makes the broker and client lighter.
> Goals
> ●  What problem is this proposal designed to solve?
> In the future, RocketMQ may access clients written in different languages. At 
> present, due to the complexity of the client logic, it takes a lot of effort 
> to rewrite the client in different languages. And the persistent connection 
> in RocketMQ is based on TCP, and the ability to resist network jitter is bad. 
> HTTP connection can better resist network jitter. In order to write and 
> access clients in different languages better, this proposal provides an HTTP 
> sending proxy, which simplifies the processing logic of the client and 
> implements a more lightweight client.
> Non-Goals
> ●  What problem is this proposal NOT designed to solve?
> Nothing specific
> ●Are there any limits of this proposal?
> User need deploy proxy before use it. It will add a little complexity for 
> operation and maintenance.
> Changes
> Adding a proxy module to achieve message proxy.
> 
> This RIP will be divided into two phases. 
> 
> The first phase will not have any impact on the existing architecture, 
> including the nameserver, depending on the service discovery configured to do 
> the proxy.
> 
> The second phase will decide whether to do proxy service discovery based on 
> community feedback or provide a lightweight http client.
> Architecture
> 
> 
> In our proposal, there are 3 features in the proxy:
> (1)   We realize group proxy in producer group/consumer group level
> (2)   The proxy receives HTTP packets sent by HTTP producer, which realizes 
> HTTP proxy and reduces the impact of network jitter.
> (3)   The proxy simplify processing logic in client and achieve lighter 
> client.
> 
> 
> 

Re: [RESTART][VOTE][#1] Release Apache RocketMQ Client CPP 1.2.3 RC2.

[liqipeng]

+1,I have checked

[OK]  Checksums and PGP signatures are valid for Source package.

[OK]  Checksums and PGP signatures are valid for Binary package.

[OK]  Source code artifacts have correct names matching the current release.

[OK]  Binary artifacts have correct names matching the current release.

[OK]  License and Notice are correct in source package.

[OK]  License and Notice are correct in binary package.

> 在 2019年8月29日，下午7:40，ShannonDing  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
> 
> 
> 
> This release included main futures below:
> 
> Support transaction message.
> Support C style batch message sending.
> Support getting error information when C API returns false.
> Polish the TCP transport layer.
> Remove useless code and fix compile warnings.
> For detail info, please see the release note.
> 
> 
> 
> The artifacts:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
>  
> 
> 
> Git tag for the release:
> 
> https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3 
> 
> 
> Hash for the release tag:
> 
> dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
> 
> 
> 
> Release Notes:
> 
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
>  
> 
> 
> The artifacts have been signed with Key :
> 
> BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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. 
> 
> 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][RIP-16]RocketMQ RPC(Request-Response model) Support

[liqipeng]

+1
> 在 2019年9月6日，上午11:35，heng du  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the kickoff of RIP-16 RocketMQ Request-Response model
> support
> 
> RPC is a powerful technique for constructing distributed, client-server
> based applications. Many companies use the MQ system to constructing their
> service bus, especially in the financial industry. We need to implement an
> RPC client based on MQ system ourselves because the MQ system doesn’t
> support RPC naturally. In the current version of rocketmq project, producer
> client only support to send a message to the broker and cannot wait a
> response message replied from the consumer. We wish RocketMQ can provide an
> RPC client implement to help developers building their applications
> conveniently and effectively.
> 
> 
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> 
> Thanks,
> The Apache RocketMQ Team
> 
> heng du  于2019年9月6日周五 上午11:32写道：
> 
>> @wenfeng
>> 
>> Actually, Building RPC based on message queue is a very traditional
>> approach, especially in the previous ESB, SOA era. Of course, in today's
>> micro-services, there are many benefits to building micro-services based on
>> MQ.
>> 
>> For example, at the transport layer level, MQ can provide true
>> asynchronous communication for RPC. In terms of visualization, MQ can also
>> provide better visibility and make it easier to replay traffic to locate or
>> fix issues, which is very important in event-driven architectures. Most
>> important of all, direct RPC will make the access relationship between
>> services become mesh, but based on MQ, the problem of network mesh calls
>> are solved. In many industries, such as the financial industry, it is
>> difficult to provide all the network access.
>> Moreover, the request-response model can be used to make RocketMQ
>> integrate well into various infrastructures. In addition, many of the same
>> types of message middleware also provide request-response access methods.
>> 
>> So I think that supporting the request-response model will increase the
>> competitiveness of RocketMQ and better expand the usage scenario.
>> 
>> 
>> wenfeng wang  于2019年8月27日周二 下午6:15写道：
>> 
>>> IMO, The most popular scenario of MQ System is that decouple complex
>>> distributed system and process message asynchronous. If a user wants low
>>> latency or explicit response from downstream, he should use an RPC
>>> Framework instead of MQ, like Dubbo, gRPC, etc. so I vote for -1.
>>> 
>>> 
>>> heng du  于2019年8月27日周二 下午5:54写道：
>>> 
 Dear Apache RocketMQ Community:
 
 We would like to propose a RIP[16] about RocketMQ RPC(Request-Response
 model) Support. Many companies use the MQ system to constructing their
 service bus, especially in the financial industry. We wish RocketMQ can
 provide an RPC client implement to help developers building their
 applications conveniently and effectively.
 
 
 Status
 
 Current State: Proposed
 
 Authors: qqeasonchen
 
 Shepherds: duhengforever
 
 Mailing List discussion: dev, users
 
 Pull Request: none
 
 Released: 4.6.0
 
 Background & Motivation
 
 RPC is a powerful technique for constructing distributed, client-server
 based applications. Many companies use the MQ system to constructing their
 service bus, especially in the financial industry. We need to implement an
 RPC client based on MQ system ourselves because the MQ system doesn’t
 support RPC naturally. In the current version of rocketmq project, producer
 client only support to send a message to the broker and cannot wait a
 response message replied from the consumer. We wish RocketMQ can provide an
 RPC client implement to help developers building their applications
 conveniently and effectively.
 
 Goals
 
   - What problem is this proposal designed to solve?
 
 (1) Design and implement an RPC interface based on RocketMQ Producer,
 which support send a message and then wait a response message replied from
 the consumer.
 
 (2) Design and Implement a consumer which can automatically or manually
 send a reply message.
 
 (3) Enable the broker to push a message to an explicit producer.
 
 
 
   - To what degree should we solve the problem?
 
 We wish developers can use RocketMQ easily to constructing their
 distributed applications which need RPC call.
 
 Non-Goals
 
   - What problem is this proposal NOT designed to solve?
 
 In this phase, this rip only supports a usable RPC call in most common
 scenarios.
 
   - Are there any limits to this proposal?
 
 Users may need to tune some client and broker’s configurations to
 achieve better performance.
 

Re: [VOTE]:Release Apache RocketMQ 4.5.2 RC1.

[liqipeng]

+1
> 在 2019年8月5日，上午10:27，huzongt...@cmss.chinamobile.com 写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for 4.5.2 of Apache RocketMQ.
> 
> This release is to improve some features for apache rocketmq,such as adding 
> new mqadmin API for ACL configuration,enhancing transactional msg by putting 
> messages that exceed max check times to system topic,enhancing share netty 
> handler in the remoting module and fixed some bugs,further improved the 
> stability of RocketMQ.
> 
> The artifacts:
> https://dist.apache.org/repos/dist/dev/rocketmq/4.5.2-rc1/
> 
> The staging repo:
> https://repository.apache.org/content/repositories/orgapacherocketmq-1030/
> 
> Git tag for the release:
> https://github.com/apache/rocketmq/tree/release-4.5.2
> 
> Hash for the release tag:
> d63678dc507e5d341a125f95a99859d2fdafa408
> 
> Release Notes:
> https://rocketmq.apache.org/release_notes/release-notes-4.5.2/
> 
> The artifacts have been signed with Key :
> 5C7C4040979F32543B624C631DA2409169DAF54B, which can be found in the keys
> file:
> https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
> 
> 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
> 
> 
> 
> huzongt...@cmss.chinamobile.com

Re: [VOTE] Release Apache RocketMQ Go Native Client 2.0.0-alpha2.

[liqipeng]

+1
> 在 2019年7月21日，上午1:40，ShannonDing  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the release of Apache RocketMQ Go Native Client 
> 2.0.0-alpha2.
> 
> 
> 
> 
> The main goal of this release is to support some new features, e.g. send the 
> message by async model and pull consumer. and besides this,
> 
> this release also will bring some unit tests for functionality.
> 
> 
> 
> 
> Github repo: https://github.com/apache/rocketmq-client-go/tree/native
> 
> Many features have not an independent issue, you can find them in Roadmap 
> issue: [2.0.0-alpha2 
> Roadmap](https://github.com/apache/rocketmq-client-go/issues/75)
> 
> 
> 
> 
> ### Feature
> 
> - [[PR-86](https://github.com/apache/rocketmq-client-go/issues/86)] - Support 
> Interceptor  
> 
> - [[PR-96](https://github.com/apache/rocketmq-client-go/pull/96)] - Support 
> multiple NameServer  
> 
> - [[PR-102](https://github.com/apache/rocketmq-client-go/pull/102)] - Support 
> QueueSelector  
> 
> - [[PR-100](https://github.com/apache/rocketmq-client-go/pull/100)] - Support 
> SendAsync  
> 
> - [[PR-106](https://github.com/apache/rocketmq-client-go/pull/106)] - Support 
> PullConsumer  
> 
> - [[PR-113](https://github.com/apache/rocketmq-client-go/pull/113)] - Support 
> Statistics of client  
> 
> - [[PR-115](https://github.com/apache/rocketmq-client-go/pull/115)] - Support 
> order message in PushConsumer  
> 
> - [[PR-117](https://github.com/apache/rocketmq-client-go/pull/117)] - Support 
> ACL 
> 
> - [[PR-119](https://github.com/apache/rocketmq-client-go/pull/119/)] - 
> Support retry when consume failed in PushConsumer  
> 
> 
> 
> 
> ### Improvement
> 
> - [[ISSUE-93](https://github.com/apache/rocketmq-client-go/issues/93)] - 
> Refactor API to make more usability.
> 
> - [[PR-107](https://github.com/apache/rocketmq-client-go/pull/107)] - Change 
> the log level from fatal to error in `start()`   
> 
> - [[PR-109](https://github.com/apache/rocketmq-client-go/pull/109)] - Add 
> unit test for producer
> 
> - [[PR-116](https://github.com/apache/rocketmq-client-go/pull/116)] - Add 
> unit test for internal/route.go
> 
> 
> 
> 
> ### Bug
> 
> - [[ISSUE-65](https://github.com/apache/rocketmq-client-go/issues/65)] - 
> Fixed the issue that Missing Tag and Properties in Message when use producer.
> 
> - [[PR-97](https://github.com/apache/rocketmq-client-go/pull/97)] - Fixed the 
> issue that The timeout of RPC doesn't work and The InvokeAsync doesn't work
> 
> 
> 
> 
> For more information about this release, you can refer to 
> https://github.com/apache/rocketmq-client-go/releases/tag/2.0.0-alpha2
> 
> 
> 
> 
> The vote will be open for at least 72 hours or until a 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]rocketmq-ons 1.0.0 release

[liqipeng]

+1
> 在 2019年7月12日，下午1:49，heng du  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the 1.0.0 release of Apache ONS client, and it's also
> the first release of apache rocketmq-ons.
> 
> Github repo: *https://github.com/apache/rocketmq-
> ons*
> 
> Based on the discussion previous[1], the Apache RocketMQ community developed
> a lightweight client named as ONS. Currently, this client has implemented
> all the basic features related to Producer/Consumer, and at the same time,
> order/batch/transactional message, etc. advanced features are also
> supported in this client. This also indicates that the client already has a
> high maturity. So, in order to continually improve this lightweight
> client, we hope to release the first version and optimize the client based
> on the problems found during the actual production environment use process.
> 
> In summary, in this release, those features below are supported:
> 
>   - Produce messages, including normal, transactional, delayed messages,
>   in synchronously, asynchronously and oneway model.
>   - Consume messages, in cluster or broadcast model, concurrently and
>   orderly with push consumer
>   - Automatically rebalanced, both in producing and consuming process.
>   - Reliability, any downtime broker or name server has no impact on the
>   client.
> 
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> [1]
> https://lists.apache.org/thread.html/0b2dfbb3b722bb8d710d8bd9d264d51013153608934d1a1c90c810de@%3Cusers.rocketmq.apache.org%3E
> ,
> Thanks,
> The Apache RocketMQ Team
> 
> 
> -- Forwarded message -
> 发件人： heng du 
> Date: 2019年7月5日周五 下午3:14
> Subject: [DISCUSS]rocketmq-ons 1.0.0 release
> To: dev 
> Cc: users 
> 
> 
> Hello RocketMQ Community,
> 
> This is the discussion for the release of rocketmq-ons 1.0.0.
> 
> As discussed in the mailing list:
> https://lists.apache.org/thread.html/0b2dfbb3b722bb8d710d8bd9d264d51013153608934d1a1c90c810de@%3Cusers.rocketmq.apache.org%3E,
> most of rocketmq users think it would be nice if there's a lightweight
> client. and most of rocketmq users agree that the light-weight client
> should be a high-level client that provides better abstraction and hide the
> internal concepts and
> implementation details as much as possible. Most important of all, to be on
> the safe side, the new client should remove the admin interface, because of
> the admin interface directly expose to the ordinary developer will pose a
> risk to the server side.
> 
> Based on the discussion above, the rocketmq community developed a
> lightweight client named as ONS. Currently, this client has implemented all
> the basic features related to Producer/Consumer, and at the same time,
> order/batch/transactional message, etc. advanced features are also
> supported in this client. This also indicates that the client already has a
> high maturity. So, in order to continually improve this lightweight
> client, we hope to release the first version and optimize the client based
> on the problems found during the actual production environment use process.
> 
> Welcome everyone to comment in this email, and if no other sounds, I would
> like to call for a vote for this release :-)
> 
> Thanks,
> The Apache RocketMQ Team

[DISCUSS]2019 Alibaba Summer of Code

[liqipeng]

Hello RocketMQ Community,
This is the discussion for 2019 Alibaba Summer of Code[1], which is the global 
programming plan.It is a good opportunity to attract  developer over the world 
to participate our community, so we want to join it .
​If you have any suggestion about , please feel free to reply to this email, we 
sincerely hope to get  your advice.​
[1]https://developer.aliyun.com/summerofcode2019 

Re: [VOTE]Release Apache rocketmq-client-cpp 1.2.2 RC1

[liqipeng]

+1
> 在 2019年4月17日，下午1:22，Shannon  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the release of rocketmq-client-cpp 1.2.2 RC1.
> 
> This release will support sending a message by the orderly model and batch 
> model, support connect MQ endpoint with ACL, polish the unit test cases and 
> transport layer, and fixed some bugs, further improved the stability of the 
> CPP core.
> 
> You can find the release note  by below link:
> https://github.com/apache/rocketmq-client-cpp/releases/tag/1.2.2-rc1
> 
> The vote will be open for at least 72 hours or until a necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve 
> [ ] +0 no opinion 
> [ ] -1 disapprove with the reason
> 
> Thanks.

[RESULT][VOTE]: Release Apache RocketMQ 4.5.0 RC1

[liqipeng]

Hello RocketMQ Community,

The vote for Apache RocketMQ 4.5.0 is now closed and has passed with [3] 
binding +1s, [9] non-binding +1s and no 0 or -1:


Binding votes +1s:

vongosling (vongosling)  
heng du (duhengforever)  
duhengforever（dongeforever）

Non-binding votes +1s:

wlliqipeng(wlliqipeng)
Zongtanghu（huzongtang）
wenfeng wang
xueqinwu667
Eks OU
Li Martin
刘建刚
丁威
陈晓东


The release will be published soon.

Thanks, 
The Apache RocketMQ Team

Re: [VOTE] Release Apache RocketMQ 4.5.0 RC1.

[liqipeng]

+1
> 在 2019年3月29日，下午3:42，liqipeng  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for 4.5.0 of Apache RocketMQ.
> 
> This release implemented the new features of Dledgerand also publish the 
> RocketMQ's User Guide, and fixed some bugs,
> further improved the stability of RocketMQ.
> 
> The artifacts:
> https://dist.apache.org/repos/dist/dev/rocketmq/4.5.0-rc1/
> 
> The staging repo:
> https://repository.apache.org/content/repositories/orgapacherocketmq-1020/
> 
> Git tag for the release:
> https://github.com/apache/rocketmq/tree/release-4.5.0
> 
> Hash for the release tag:
> 16293c33062757ff0627666c3eddd123153af3b6
> 
> Release Notes:
> https://rocketmq.apache.org/release_notes/release-notes-4.5.0/
> 
> The artifacts have been signed with Key :
> 0FB04112692FB2B3A6D9A6815A069FF0C938893A, which can be found in the keys
> file:
> https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
> 
> 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
> 

[VOTE] Release Apache RocketMQ 4.5.0 RC1.

[liqipeng]

Hello RocketMQ Community,

This is the vote for 4.5.0 of Apache RocketMQ.

This release implemented the new features of Dledgerand also publish the 
RocketMQ's User Guide, and fixed some bugs,
further improved the stability of RocketMQ.

The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/4.5.0-rc1/

The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1020/

Git tag for the release:
https://github.com/apache/rocketmq/tree/release-4.5.0

Hash for the release tag:
16293c33062757ff0627666c3eddd123153af3b6

Release Notes:
https://rocketmq.apache.org/release_notes/release-notes-4.5.0/

The artifacts have been signed with Key :
0FB04112692FB2B3A6D9A6815A069FF0C938893A, which can be found in the keys
file:
https://dist.apache.org/repos/dist/dev/rocketmq/KEYS

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: [DISCUSS][RIP-11]RocketMQ Architecture Evolution

[liqipeng]

It was so wonderful to see RIP-11.I also think  it is very necessary to make 
some adjustments to the architecture of RocketMQ .I am very willing to join in.

Best Regards,
Qing Feng

> 在 2019年2月1日，下午3:23，heng du  写道：
> 
> Dear Apache RocketMQ Community:
> 
> We would like to propose a RIP11 [1] about RocketMQ Architecture Evolution.
> In order to better serve cloud computing in the next decade, IMO, we should
> make more architectural adjustments to meet the needs of cloud computing
> and the IOT,  and I hope more community students can get involved.
> 
> 
> [1]*https://docs.google.com/document/d/1B1cHjwfOEyU-_W_pikUD__mH48zb3vDoNmy1zqJVcss/edit?usp=sharing
> *
> 
> Best Regards
> Heng Du

Re: [Vote] [RIP-10]RocketMQ Unit Test

[liqipeng]

+1
> 在 2019年1月28日，上午10:43，Shannon  写道：
> 
> Hello RocketMQ Community,
> 
> 
> This is the vote for the kickoff of RIP-10 RocketMQ Unit Test.
> You can find the detail of the RIP-10 by below link:
> https://docs.google.com/document/d/1DG3nR1j_eQu61mlGa2SLvLDoRfamSVX7Xo8CSJnKE98/
> 
> 
> For RocketMQ project, Unit Test is very important. It can improve code 
> quality by increase code coverage. So we're going to add unit tests for 
> RocketMQ.
> 
> 
> The vote will be open for at least 72 hours or until a 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-client-cpp 1.2.1

[liqipeng]

+1
> 在 2019年1月23日，下午10:19，Shannon  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the release of rocketmq-client-cpp 1.2.1.
> 
> This release will support sending a message by the async model using C API, 
> and fixed some bugs,further improved the stability of the CPP core.
> 
> You can find the release note  by below link:
> https://github.com/apache/rocketmq-client-cpp/releases/tag/1.2.1
> 
> The vote will be open for at least 72 hours or until a necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve 
> [ ] +0 no opinion 
> [ ] -1 disapprove with the reason
> 
> Thanks.
> 

[DISCUSS][RIP-10] RocketMQ Unit Test

[liqipeng]

Dear Apache RocketMQ Community:
We would like to propose a RIP[1] about RocketMQ Unit Test. IMO,unit test is 
very important,which can improve code quality by increase code coverage.So 
we're going to add unit test for RocketMQ.Welcome to join us.

[1]https://docs.google.com/document/d/1DG3nR1j_eQu61mlGa2SLvLDoRfamSVX7Xo8CSJnKE98/edit?usp=sharing
 


Best Regards
qingfeng & houdao Chen

Re: [Vote] [RIP-9]RocketMQ Developer Guide

[liqipeng]

+1
> 在 2019年1月16日，下午8:12，Shannon  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the kickoff of RIP-9 RocketMQ Developer Guide.
> You can find detail of the RIP-9 by below link:
> https://docs.google.com/document/d/1fQXOgFZ1IOatVbuwtQd9ftI4Vn0_I3fdFEAGV14fVAQ/edit#heading=h.nwczedg8v2na
>  
> 
> 
> For RocketMQ users, the developer  guide is undoubtedly very important, which 
> can help developers quickly learn RocketMQ. So we begain to write the 
> developer  guide for RocketMQ.
> 
> The vote will be open for at least 72 hours or until a necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve 
> [ ] +0 no opinion 
> [ ] -1 disapprove with the reason
> 
> Thanks,
> The Apache RocketMQ Team

[DISCUSS][RIP-8] RocketMQ Developer Guide

[liqipeng]

Sorry,I forget to discuss.
> 在 2019年1月10日，下午1:35，liqipeng  写道：
> 
> Dear Apache RocketMQ Community
> My name is qingfeng. I'm very interested in open source. I have organized 
> some project about RocketMQ, such as RocketMQ multilingual client. For 
> RocketMQ users, the developer  guide is undoubtedly very important,which can 
> help developers quickly learn rocketmq. So we're going to write the developer 
>  guide for RocketMQ.
> Details is in the RIP 
> file:https://docs.google.com/document/d/1fQXOgFZ1IOatVbuwtQd9ftI4Vn0_I3fdFEAGV14fVAQ/edit#heading=h.nwczedg8v2na
>  
> <https://docs.google.com/document/d/1fQXOgFZ1IOatVbuwtQd9ftI4Vn0_I3fdFEAGV14fVAQ/edit#heading=h.nwczedg8v2na>.welcome
>  to join us . any suggestions or comments are welcome!
>Best Wishes
> qingfeng​

Re: [DISCUSS]The graduation of RocketMQ's golang client

[liqipeng]

Very good news. Hope it come soon
> 在 2019年1月3日，下午10:30，Shannon  写道：
> 
> Hello RocketMQ Community,
> 
> This is the discussion for the graduation of RocketMQ’s golang client(
> https://github.com/apache/rocketmq-client-go 
> ).
> 
> RocketMQ-client-go is the golang client of Apache RocketMQ, The
> RocketMQ golang client library is built on the existing CPP client
> library and exposes almost all of the features in CPP client.
> 
> As the CPP client has been used by several companies and main features have
> been verified in their production environment, therefore, we have reason to
> believe that golang client has the same stability with CPP client. and the
> most important of all, up to now, there are 9 active contributors from 6
> organizations in the community.
> So we think it has reached the graduation standard, but in order to ensure
> the quality of the project, we still investigated the usage information of
> three companies from different industries, the information shows below:
> 1 An Express Company
>1）Environment Configuration：
>   CentOS 7
>   2) Functions
>Synchronous transmission with binlog messages
>Consume message with Pull mode
>  3）scene
>Mainly used for system decoupling, data synchronization.
>  4）Usage description
>Go SDK is relatively stable and there is no problem for the
> time being.
> 2 A technology company
>   1）Environment Configuration：
>   CentOS 6.8
>   2) Functions
>Synchronous transmission 
>Consume message with Pull mode
>   3）Usage description
> there is no problem for the time being.
> 
> 3 Database department of Alibaba
>   1）Environment Configuration：
>   Linux Core 3.10
>   2) Functions
>PushConsumer with cluster mode
>  3）scene
>Mainly used for receiving server state change information from 
> RocketMQ, so as to facilitate some automatic operation and maintenance 
> decisions.
> 
> If you have any suggestion about the graduation of the Golang client, please 
> feel free to reply to this email, we sincerely hope to get your advice.

Re: [VOTE] RocketMQ-client-cpp 1.2.0 Release And Graduation

[liqipeng]

+1
> 在 2018年12月6日，上午11:28，Shannon  写道：
> 
> 
> 
> 
> 
> +1, no binding.
> 
> 
> 
> 
> 
> At 2018-12-06 11:21:13, "heng du"  wrote:
>> Hello RocketMQ Community,
>> 
>> This is the vote for the 1.2.0 release and the graduation of Apache 
>> RocketMQ-client-cpp.
>> 
>> Github repo: https://github.com/apache/rocketmq-client-cpp 
>> 
>> This release is a huge step forward in cpp 1.0.1. It   
>> provides two kinds of interfaces in C++ and C-style, and a bunch of other 
>> language bindings will be built on top of it, including python, 
>> Node.js,C#,golang and so on.We simplified the process of project compilation 
>> in this version,and you can compile the whole project with just one command.
>> 
>> new feature
>>  C-Style API was added to support multilingual client, such as 
>> python,node.js, golang, which has not yet implemented all the functions of 
>> C++ API. The following are the major functions of C-Style API :
>> 
>> 
>> 1 Support  reliable synchronous,  one-way  and order transmission 
>> 2 Support push consumer and pull consumer.
>> 3 Support setDelayTimeLevel.
>> 4 Support message compression.
>> 5 Support setting up message consumption mode.
>> Improvement:
>> 1  Enhanced the capability of multi-platform support, such as linux, 
>> window,macOS.
>> 2  The compilation method of the project is simplified. You can compile the 
>> entire project with one command.
>> Bug:
>> 1 Fix an issue about the unique key. When a message is sent, the producer 
>> cannot get unique.
>> 
>> The vote will be open for at least 72 hours or until a 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: [DISCUSS]The graduation of RocketMQ's CPP client.

[liqipeng]

As far as I know, RocketMQ-Client-CPP has been able to support multiple 
operating systems, such as centos, redhat, ubuntu, windows, and has been used 
online by many companies. I look forward to graduating from the CPP client as 
soon as possible.
> 在 2018年11月29日，下午10:45，heng du  写道：
> 
> Hello RocketMQ Community, 
> 
> This is the discussion for the graduation of RocketMQ’s CPP 
> client(https://github.com/apache/rocketmq-client-cpp).
> 
> RocketMQ-Client-CPP is the C/C++ client of Apache RocketMQ,  which provides 
> two kinds of interfaces in C++ and C-style, almost have all the features 
> included in the Java client, and it’s also the core of other language’s 
> client, other language’s client will be built on top of it, including python, 
> Nodejs, C#, golang and so on.
> 
> After many years of incubation, the CPP client has been used by several 
> companies  and main features have been verified in their production 
> environment, and up to now, there are 6 active contributors from 5 
> organizations in the community.
> 
> So we think it has reached the graduation standard, but in order to ensure 
> the quality of the project, we still investigated the usage information of 
> three companies from different industries, the information shows below:
> 
>   1 A financial company
> 1）Environment Configuration：
> （1）Red Hat Enterprise Linux Server release 6.58*CPU   32G Memory
> （2） 2 * Master + 2 * Slave
>   (3) Three subsystems were deployed, including six producer 
> instances and six consumer instances.
> 2) Functions
>  Asynchronous transmission
>  PushConsumer with cluster mode
>  PushConsumer with broadcasting mode
>3）scene
>  Mainly used for system decoupling, message reliability assurance, 
> resolving write speed mismatch between redis and Oracle scenarios.  
>   4)  How long has it been used?
>6 months
>  5）Usage description
>   （1) The compilation of the original CPP SDK is tedious, and many tools 
> and dependency libraries need to be installed. The optimized version of 
> public beta is easy to compile and get started.
>   （2) example is more detailed, the main use scenarios have examples, can 
> easily guide the basic use, follow-up use of SDK programming is simple and 
> easy to use.
>   （3) the SDK and server sides are relatively stable, basically there is 
> no problem after the line.
> 
> 2 An education company
>1）Environment Configuration：
> CentOS 7.x
> 2) Functions
>  Asynchronous transmission
>  Synchronous transmission
>  Orderly transmission
>  oneway transmission
>  PushConsumer with cluster mode
>  PushConsumer orderly
>3）Business scale
>  100 million per day​​
>3）scene
>  Mainly used for system decoupling
>   4)  How long has it been used?
>1 year
>  5）feedback
>   CPP client is relatively stable, there is basically no problem Online
> 
> 3   Alibaba
> 1）Environment Configuration：
>   （1）Ubuntu Server 16.048*CPU   16G Memory
>   （2） 2 * Master + 2 * Slave
> (3) two producer instances and three consumer instances.
> 2) Functions
>  （1）C++  
> Asynchronous transmission
> PushConsumer with cluster mode
>  （2）C
> Asynchronous transmission
> PushConsumer with cluster mode
>3）scene
>  Mainly used for system decoupling
>4)  How long has it been used?
>1 year
> 5）feedback
>   （1）CPP client and Java client can send and receive each other.
>  （2）Messages can be sent and consumed normally.
> 
> 
> If you have any suggestion about the graduation of the CPP client, please 
> feel free to reply to this email, we sincerely hope to get your advice.
> 
> 
> 
>