[STARTUP] Apache RocketMQ Meetup - Hangzhou

[Gosling Von]

Dear Apache RocketMQ Community,

I am excited to call for the meetup in Hangzhou, China at Nov. 24 am., 2018. 
Please have a look at your schedule, and consider submitting a talk to the 
community.  The overarching message about this meetup is “Apache RocketMQ: 
Devops and Multi-lingual Cloud Service“, and we wish to highlight the fact that 
Apache RocketMQ is where tomorrow is invented - you are the ones inventing it.


For further updated about this Meetup, follow us on Twitter, @ApacheRocketMQ, 
or contact me - vongosl...@apache.org - with any questions or concerns.



Thanks!
Von Gosling

Re: RIP-2 Multiple directories support for commitLog storage

[Gosling Von]

Any discussion on it ? If not, I would like to discard  and archive it. IMO, it 
is a good start from the newer storage introduced from the 5.0. 

[1] http://rocketmq.apache.org/community/ 



Best Regards,
Von Gosling

> 在 2018年9月29日，下午10:11，Haiting Jiang  写道：
> 
> Dear Apache RocketMQ Community
> 
> I would like to propose a new feature for Apache RocketMQ: multiple
> directories support for commitLog storage.
> Details is  in the RIP file :
> https://docs.google.com/document/d/1jTPCzyWChc1RVQIAg7x86IVcaWKgAqEwDIODkZhhNuA/edit?usp=sharing
> Any suggestions and comments are welcome!
> 
> Best regards
> Haiting Jiang

[DISCUSS] [RIP] Message Track Trace

[Gosling Von]

+1

Very cool, It seems to the fifth RIP from the community.

Best Regards,
Von Gosling

> 在 2018年11月6日，下午1:52，huzongt...@cmss.chinamobile.com 写道：
> 
> FYI
>  
> 发件人： huzongt...@cmss.chinamobile.com 
> 发送时间： 2018-11-06 13:38
> 收件人： users-subscribe ; commits 
> ; dev-help 
> 
> 主题： About the RIP for new Feature：Message Track Trace
> RIP-1: Message Track Trace
> 
> 1、Status
> Current State: Proposed
> Authors: HuzongTang
> Shepherds: Zhendong
> Mailing List Discussion: 
> Pull Request: #PR_NUMBER
> Released: 
> 2、Background & Motivation
>   What do we need to do
>   Message track trace refers to the consumption processing of a message 
> which is sent from the producer instance has arrived the broker,and then has 
> been consumed by the consumer instance.In the whole process, the information 
> of time, location and other related services(including Client and Broker) is 
> aggregated into the complete link information of message communication.
>   In MQ system, the complete link of a message contains three roles: 
> producer, broker server and consumer.In the process of message communicaton, 
> each role adds relevant information to the track trace link.By aggregating 
> these information,it can provide some powerful support to user.
>  About the Apache RocketMQ project,I will add the feature of message 
> track trace which can help users query every complete link data of a message 
> exactly.This funcation is important to RocketMQ,especially in some  financial 
> application fields.
> 
> 3、Goals
> What problem is this proposal designed to solve?
> Reliability and Availability is the most two important characters for 
> each MQ system.Although RocketMQ does very well in the two fields,it need 
> some other methods to make sure the complete link of a message is no 
> problem.By some ways,we should view the complete link of a messag and find 
> the root cause of failure in process messaging quickly.
> So,if RocketMQ support the feature of Message Track Trace,we can find and 
> analyse the root cause of failure in process messaging easily.And we can 
> query many parameter values,such as sending cost time,consumption cost 
> time,store time in broker and so on.The architecture of Message Track Trace 
> will be introduced in below chapter.
> 
> 4、Non-Goals
> What problem is this proposal NOT designed to solve?
>   Every users who build application by using RocketMQ may lack of a 
> efficient way to  find and analyse the root cause of failure in process 
> messaging easily and quickly.The users may spend much more time and enery on 
> operation of RocketMQ in production enviroment.
> Are there any limits of this proposal?  
>  In order to reduce the impact of message entity content storage in 
> RocketMQ，we redefine a special broker which stores every message track 
> trace.So,if user don't want to use this funcation,he can close it in client 
> by setting a flag.
> 
> 5、Changes
> We need add some codes in client and broker component which include 
> collecting producer and consumer instances' infomation and redefine a special 
> broker node.Read below sections to get more details about the Message Track 
> Trace for RocketMQ.
> 
> 6、Architecture
> We plan to design the function of message track trace including its store 
> part and client instance collecting.The total architecture has two part below:
> （1）Client instance collects the infomation of message track trace
> 
> The design of architecture above as follows:
> （a）."producer and consumer multi-thread module, and Blocking Queue"：here, 
> in client,as a producer model,we can collect the infomation(such as,sending 
> and consuming message cost time,broker store time,broker stored ip address 
> and so on) and put this information into the Blocking Queue.And as s consumer 
> model,use a thread called "MQ-AsyncArrayDispatcher" to take the message track 
> trace infomation from Blocking Queue.Then this asynchronous thread( called 
> "MQ-AsyncArrayDispatcher") pack the message track trace element as 
> AsyncAppenderRequest task and submit to the thead pool.
> Last,the main execution process of  AsyncAppenderRequest task is sending 
> the message track trace infomation which is collected above from client side 
> to a special broker node which is redefined in below chapter.
> （b）.define a new pair hook which is implementation of 
> the“SendMessageHook/ConsumeMessageHook”,from this,we can collect message 
> track trace data  before and after publishing and subscribing messages.
> 
> （2）Redefine a special broker node to store message track trace data
> 
> As shown in the above picture,we can define a specail broker service node 
> which can store the message track trace data in a 

Re: [RIP-4]New feature:RocketMQ Go Client

[Gosling Von]

+1 to support it.

Best Regards,
Von Gosling


> 在 2018年10月31日，下午9:44，Shannon  写道：
> 
> Dear all,
> 
> As the lack of a corresponding client, it is difficult for applications 
> developed using the go language to send or consume messages through RocketMQ. 
> A new feature will be developed to support this case and a new module named 
> rocketmq-client-go will be added too.
> See: 
> https://docs.google.com/document/d/1kngd9fyzgG6g48mMNGgnvm1Cs0f-emik2_ROv_a1ZvY
>  
> 
> 
> You are kindly welcome to review this new module(rocketmq-client-go) and we 
> sincerely look forward to your feedback.
> 
> Best regards,
> Shannon Ding
> 
> 
>  

Re: [RIP-3]New feature:RocketMQ Python Client

[Gosling Von]

Hi,

It would be helpful for the community. I would like to vote +1 for this RIP.


Best Regards,
Von Gosling

> 在 2018年10月29日，下午7:57，Shannon  写道：
> 
> 
> Dear all,
> 
> As the lack of a corresponding client, it is difficult for applications 
> developed using the Python language to send or consume messages through 
> RocketMQ. A new feature will be developed to support this case and a new 
> module named rocketmq-client-python will be added too.
> See:  
> https://docs.google.com/document/d/10jt7wd5NvGiIznsfvFfg_9A1SlFsjbYs6uucX1d7cZc
>  
> 
> 
> You are kindly welcome to review this new module(rocketmq-client-python) and 
> we sincerely look forward to your feedback.
> 
> Best regards,
> Shannon Ding

Re: [DISCUSS][RIP-8] RocketMQ Developer Guide

[Gosling Von]

Hi,

It seems to be a conflict number in RIP-8, could we reassign it ? BTW, It’s 
over 72 hours since we open discussion, what do we plan to do next? Could we 
Shepherd put forward to call for vote ?

Best Regards,
Von Gosling

> 在 2019年1月10日，下午2:15，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
>>  
>> .welcome
>>  to join us . any suggestions or comments are welcome!
>>   Best Wishes
>>qingfeng​
> 
> 

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

[Gosling Von]

+1

A little comment,  I haven’t see the RIP-8 discussion come up in dev email 
list. And please shepherd help to update the wiki as the following[1].

“ Please update the RIP wiki page, and the index below, to reflect the current 
stage of the RIP after a vote. This acts as the permanent record indicating the 
result of the RIP (e.g., Accepted or Rejected). Also, report the result of the 
RIP vote to the voting thread on the mailing list so the conclusion is clear."

[1] https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal


Best Regards,
Von Gosling

> 在 2019年1月16日，下午8:12，Shannon  写道：
> 
> The vote will be open for at least 72 hours or until a necessary number of 
> votes are reached.
> 

Re: [ANNOUNCE] New committer and PMC member for Apache RocketMQ

[Gosling Von]

Congrats, smart community guys I've worked with :-)


Best Regards,
Von Gosling

> 在 2018年12月24日，下午4:34，dongeforever  写道：
> 
> Hi Apache RocketMQ Community,
> 
> The Project Management Committee (PMC) for Apache RocketMQ has invited Heng 
> Du(apache id: duhengforever) to become PMC Member and ShannonDing(apache id: 
> dinglei) to become committer and we are pleased to announce that they have 
> accepted.
> 
> ShannonDing [1][2], who built a client eco-system for Apache RocketMQ 
> Community. With his great work, the community has released a production ready 
> client for CPP and Python. And also the Go Client is on the way.
> 
> Heng Du [3], who spent much time in expanding the community. With his great 
> work, ShannonDing is quickly familiar with Apache Way and doing a pretty job 
> in contributing to the clients. At the same time, he has helped the community 
> to release 4.3.2 and 4.3.1, and the rocketmq-spring 2.0.0. 
>  
> Congrats, guys :-)
> 
> Notice: Being a committer enables easier contribution to the project since 
> there is no need to go via the patch submission process. This should enable 
> better productivity. and being a PMC member enables assistance with the 
> management and to guide the direction of the project.
> 
> 
> [1] 
> https://github.com/apache/rocketmq-client-cpp/pulls?q=is%3Apr+author%3AShannonDing
>  
> 
> [2] 
> https://github.com/apache/rocketmq-client-python/pulls?q=is%3Apr+author%3AShannonDing
>  
> 
> [3] 
> https://lists.apache.org/list.html?d...@rocketmq.apache.org:lte=3M:heng%20du 
> 
> 
> Best Regards,
> Apache RocketMQ Team

Re: [DISCUSS]The graduation of RocketMQ-Spring-Boot

[Gosling Von]

Glad to see the spring project be more maturity, it was with even greater 
delight that I also participate the review with spring community guys, really 
learn more from the spring code geeks. 

I support graduation. From the known data, no doubt about it that this project 
has met the healthy community requirement and really collect some use cases 
from production environment.


Best Regards,
Von Gosling

> 在 2018年12月6日，下午7:03，heng du  写道：
> 
> Hello RocketMQ Community, 
> 
> This is the discussion for the graduation of RocketMQ’s Spring Boot 
> client(https://github.com/apache/rocketmq-spring 
> ).
> 
> RocketMQ-spring-boot provides a kind of Spring-style usage of a client of 
> Apache RocketMQ,  which makes RocketMQ native API transparent with the 
> Spring-Messaging API and takes advantage of Spring annotation and 
> auto-configure. It uses the RocketMQTemplate API to send spring standard 
> messages to RocketMQ Broker as well as uses implementation class which 
> annotated by RocketMQListener to receive messages. 
> 
> After more than 6 months of incubation, the RocketMQ-spring-boot project has 
> been used by several companies and main features have been verified in their 
> production environment, and up to now, there are 3 active contributors from 3 
> 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 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 
>   4）scene
>  Mainly used for system decoupling
>   5)  How long has it been used?
>6 month
>   6）feedback
>  a) It is so convenient to use less code and configuration than 
> traditional API 
>  b) Out of the box to use the spring-starter
> 
> 2. A financial company
>   1）Environment Configuration：
> （1）CentOS 6.x
> （2） 3  broker nodes
>   2) Functions
>  Asynchronous transmission
>  PushConsumer with cluster mode
>  PushConsumer with broadcasting mode
>   3）Business scale
>  N/A
>   4）scene
>  Mainly used for system decoupling, message reliability assurance, 
> resolving to write speed mismatch between redis and Oracle scenarios.  
>   5)  How long has it been used?
>2 months
>   6）Usage description
>   （1）Totally use the starter functions to send and receive the message 
> and verified our required scenarios. 
>   （2）we mainly use the starter as a PoC in the current phase, will 
> normally use it in the next phase and production release.
> 
> 3. An intelligent device company
>   1）Environment Configuration：
> CentOS 7.4 + RocketMQ 4.3
>   2) Functions
>  Asynchronous transmission
>  Synchronous transmission
>  Orderly transmission
>  oneway transmission
>  PushConsumer with cluster mode
>  PushConsumer orderly
>  Send the message in Transaction 
>  Consume transactional message
>   3）Business scale
>  More than 100 thousand per day, ~100B per message 
>   4）scene
>  Mainly used for system decoupling
>   5)  How long has it been used?
>N/A
>   6）feedback
> a) It is quite normal to send and receive messages, no error and 
> exception occur.
> b) The starter is simple and convenient to use. It is compatible with 
> Spring ECO system and useless code and configure to performance the client 
> functions. 
> 
> If you have any suggestion about the graduation of the RocketMQ Spring Boot 
> client, please feel free to reply to this email, we sincerely hope to get 
> your advice.

[ANNOUNCE] Apache RocketMQ Meetup - Hangzhou

[Gosling Von]

Dear Apache RocketMQ Community,

Thanks for your enthusiasm. I would like to announce the sixth meetup register 
for Apache RocketMQ is open[1], and thanks again all the speaker, Looking 
forward to seeing you :-)


[1] https://mp.weixin.qq.com/s/u-CskpmDcYPEzV9GWo7QRw


Best Regards,
Von Gosling


> 在 2018年11月22日，下午10:12，vongosling  写道：
> 
> Dear Apache RocketMQ Community,
> 
> Thanks for your enthusiasm. I would like to announce the sixth meetup 
> register for Apache RocketMQ is open[1], and thanks again all the speaker, 
> Looking forward to seeing you :-)
> 
> 
> 
> [1] https://mp.weixin.qq.com/s/u-CskpmDcYPEzV9GWo7QRw 
> <https://mp.weixin.qq.com/s/u-CskpmDcYPEzV9GWo7QRw>
> 
> 
> Best Regards,
> Von Gosling
> 
> lollipop mailto:lolli...@apache.org>> 于2018年11月19日周一 
> 下午6:01写道：
> Hi all:
> 
> I would like to join the meetup to share a topic named 《Alibaba Cloud
> Message Queue based on RocketMQ》, aimed to introduce some best practices
> Best Regards
> 
> 
> On Wed, Nov 7, 2018 at 11:35 AM Gosling Von  <mailto:fengji...@gmail.com>> wrote:
> 
> > Dear Apache RocketMQ Community,
> >
> > I am excited to call for the meetup in Hangzhou, China at Nov. 24 am.,
> > 2018. Please have a look at your schedule, and consider submitting a talk
> > to the community.  The overarching message about this meetup is “Apache
> > RocketMQ: Devops and Multi-lingual Cloud Service“, and we wish to highlight
> > the fact that Apache RocketMQ is where tomorrow is invented - you are the
> > ones inventing it.
> >
> >
> > For further updated about this Meetup, follow us on Twitter,
> > @ApacheRocketMQ, or contact me - vongosl...@apache.org 
> > <mailto:vongosl...@apache.org> - with any
> > questions or concerns.
> >
> >
> >
> > Thanks!
> > Von Gosling
> 
> 
> -- 
> Nothing is impossible

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

[Gosling Von]

Hi,

It would be helpful if we could summarize before voting :-)

Best Regards,
Von Gosling

> 在 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-go 1.2.0 Release And Graduation

[Gosling Von]

Great, I think this is a effective +1, does anyone could build in Linux and 
MacOX platform?


Best Regards,
Von Gosling

> 在 2019年1月4日，下午3:05，liqipeng  写道：
> 
> 
>   ../rocketmq-client-go/.gitignore
>   ../rocketmq-client-go/CONTRIBUTING.md
>   ../rocketmq-client-go/doc/Introduction.md

Re: [RIP-0] RocketMQ-Improvement-Proposal Introduction

[Gosling Von]

Thanks heng. IMO, it is a good start for doc improvement[1] using RIP prefix. 
In this way, we only have two type of the PRs, one start with ISSUE#?, another 
start with RIP#?. Right? It is really a great improvement to make it easier for 
more guys to participate in the community:-)

[1] https://github.com/apache/rocketmq/pull/663

Best Regards,
Von Gosling

> 在 2019年1月9日，下午6:59，heng du  写道：
> 
> In the last few years, we use the Jira(migrated to Issues) to trace issue or 
> collect new idea from the community. It’s a nice way for a feature request 
> but not very formal and easy to trace and manage. So We introduce the RIP - 
> RocketMQ Improvement Proposal mechanism to replace the current Feature 
> Request Process.

[STARTUP][CFP] Apache RocketMQ Meetup China - Chengdu

[Gosling Von]

Dear Apache RocketMQ Community,

I am excited to call for the Apache RocketMQ Meetup China, Chengdu at  March. 
2, 2019 (Saturday). Please have a look at your schedule, and consider 
submitting a talk to the community[1].  The overarching message about this 
meetup is  “Apache RocketMQ: Cloud-Native Data Processing Infrastructure“, and 
we wish to highlight the fact that Apache RocketMQ is where tomorrow is 
invented - you are the ones inventing it.

For further updated about this Meetup, follow us on Twitter, @ApacheRocketMQ, 
or contact me - vongosl...@apache.org - with any questions or concerns.

[1] http://alibabadeveloper.mikecrm.com/q4Zio1r 


P.S.: this email is free to be shared publicly if you want to.

Best Regards,
Von Gosling

Re: [VOTE][RIP-11]RocketMQ Architecture Evolution

[Gosling Von]

+1

Best Regards,
Von Gosling

> 在 2019年2月14日，上午10:23，heng du  写道：
> 
> Hello RocketMQ Community,
> 
> This is the vote for the kickoff of RIP-11 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 members can be involved in.
> 
> You can find the detail of the RIP-11 in the link below:
> https://docs.google.com/document/d/1B1cHjwfOEyU-_W_pikUD__mH48zb3vDoNmy1zqJVcss/edit?usp=sharing
>  
> 
> 
> 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][RIP-11]RocketMQ Architecture Evolution

[Gosling Von]

Great, Thanks heng’s RIP work for the next generation evolution of the Apache 
RocketMQ. I would like to hear some voice from the community. Even though it is 
a demand :-)


Best Regards,
Von Gosling

> 在 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: [RESTART][VOTE][#1]RocketMQ spring 2.0.3 release.

[Gosling Von]

+1

> On May 31, 2019, at 7:45 PM, ShannonDing  wrote:
> 
> 
> 
> 
> Hello RocketMQ Community,
> 
> 
> 
> 
> This is the vote for the 2.0.3 release of Apache rocketmq-spring
> 
> 
> 
> 
> Github repo:
> 
> https://github.com/apache/rocketmq-spring
> 
> 
> 
> 
> The staging repo:
> 
> https://repository.apache.org/content/repositories/orgapacherocketmq-1027/
> 
> 
> 
> 
> The main goal of this release is to align with RocketMQ Client 4.5.1 and
> 
> supports the new features, e.g. connect name server with domain and set delay 
> level in async model. and besides this,
> 
> this release also will bring some enhancements for usability.
> 
> 
> 
> 
> New Feature:
> 
> *  [Feature-36](https://github.com/apache/rocketmq-spring/issues/36)Support 
> delay level configuration in async mode
> 
> *  [Feature-46](https://github.com/apache/rocketmq-spring/issues/46)Support 
> multiple RocketMQTemplate & name-server overrides Consumer Listener 
> 
> *  [Feature-59](https://github.com/apache/rocketmq-spring/issues/59)Sending 
> batch messages with RocketMQTemplate
> 
> 
> 
> 
> Improvement:
> 
> *  [ISSUE-61](https://github.com/apache/rocketmq-spring/pull/61) Generate 
> spring-configuration-metadata.json for easy configuration tips.
> 
> *  [ISSUE-63](https://github.com/apache/rocketmq-spring/issues/63) Update 
> README_zh_CN.md
> 
> *  [ISSUE-74](https://github.com/apache/rocketmq-spring/issues/74) Add acl 
> examples compile in the project
> 
> *  [ISSUE-78](https://github.com/apache/rocketmq-spring/issues/78) Add new 
> accessChannel property for both producer/consumer @since RMQ 4.5.1
> 
> 
> 
> Bug
> 
> *  [ISSUE-53](https://github.com/apache/rocketmq-spring/issues/53) Raise a 
> warning log message if no property 'rocketmq.name-server' is defined in 
> application.property
> 
> *  [ISSUE-67](https://github.com/apache/rocketmq-spring/issues/67) Fix typo 
> in example readme file
> 
> 
> 
> 
> 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
> 
> 
> 
> 
> | |
> Shannon
> |
> |
> ding...@apache.org
> |
> 签名由网易邮箱大师定制
> 

Re: [VOTE]Open the ISSUE module for Apache RocketMQ Sub Project

[Gosling Von]

+1

> On Jun 4, 2019, at 12:40 PM, ShannonDing  wrote:
> 
> Hello RocketMQ Community,
> 
> This is the vote for Opening the Issue module of RocketMQ’s subproject, and 
> it is list below:
> https://github.com/apache/rocketmq-docker 
>  
> https://github.com/apache/rocketmq-exporter 
>  
> https://github.com/apache/rocketmq-operator 
>  
> 
> These projects are very important parts of Apache RocketMQ and enrich the 
> RocketMQ ecosystem.
> The issue module is an efficient way to manage the questions and features of 
> projects
> So we need to open the ISSUE modules of these projects.
> 
> 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: [ANNOUCE] New committer Jonnxu

[Gosling Von]

Congrats Jonnxu:-)


Best Regards,
Von Gosling

> On Jun 11, 2019, at 9:22 AM, heng du  wrote:
> 
> Hi Apache RocketMQ Community,
> 
> The Project Management Committee (PMC) for Apache RocketMQ has invited 
> Jonnxu(apache id: xujiang) to become a committer and we are pleased to 
> announce that they have accepted. Congrats, guy :-)
> 
> Notice: Being a committer enables easier contribution to the project since 
> there is no need to go via the patch submission process. This should enable 
> better productivity. and being a PMC member enables assistance with the 
> management and to guide the direction of the project.
> 
> 
> Best Regards,
> Henry

Re: [VOTE][RIP-16]RocketMQ RPC(Request-Response model) Support

[Gosling Von]

+1 

Glad to see the strong desire for microservice/servicemesh in community. Let it 
be native in RocketMQ :-)

Best Regards,
Von Gosling

> On Sep 6, 2019, at 11:35 AM, heng du  wrote:
> 
> 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 mailto:duhengfore...@gmail.com>> 
> 于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 mailto:sxian.w...@gmail.com>> 
> 于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 mailto:duhengfore...@gmail.com>> 
> 于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 

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

[Gosling Von]

+1

Best Regards,
Von Gosling

> On Jul 21, 2019, at 1:40 AM, ShannonDing  wrote:
> 
> 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: [ANNOUNCE] Release Apache RocketMQ 4.6.0

[Gosling Von]

Great job, this release comes from a very active community cooperation.



Best Regards,
Von Gosling



> On Nov 25, 2019, at 10:01 PM, ShannonDing  wrote:
> 
> is release adds a lightweight pull consumer and added fully support for IPv6 
> environments. This release also provides a request-reply feature to support 
> micro-services. In addition, this release also fixed some issues and further 
> improved the stability of related modules such as tr

Re: [VOTE]Release Apache RocketMQ Client Go(Cgo) 1.2.4 RC1.

[Gosling Von]

+1,

I’v checked:

- 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.



Best Regards,
Von Gosling

> On Nov 21, 2019, at 7:20 PM, ShannonDing  wrote:
> 
> Hello RocketMQ Community,
> 
> This is the vote for version 1.2.4 of Apache RocketMQ Client Go(Cgo).
> 
> 
> 
> The artifacts:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-go/1.2.4-rc1/ 
> 
> Git tag for the release:
> 
> https://github.com/apache/rocketmq-client-go/releases/tag/v1.2.4 
> 
> Hash for the release tag:
> 
> 6bb52431a5eede4b3781d13a90120dea46779669
> 
> Release Notes:
> 
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-1.2.4/
>  
> 
> 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.6.0 RC1.

[Gosling Von]

+1,

I’v checked:

- Checksums and PGP signatures are valid for Binary & Source package.
- Source code artifacts have correct names matching the current release.
- License and Notice are correct in Binary & Source package.
- Go pass according to quick start.


Best Regards,
Von Gosling

> On Nov 21, 2019, at 7:51 PM, ShannonDing  wrote:
> 
> Hello RocketMQ Community,
> 
> 
> 
> This is the vote for 4.6.0 of Apache RocketMQ.
> 
> 
> 
> This release adds a lightweight pull consumer and added fully support for 
> IPv6 environments. This release also provides a request-reply feature to 
> support micro-services. In addition, this release also fixed some issues and 
> further improved the stability of related modules such as transaction 
> messages and abnormal recovery.
> 
> 
> 
> The artifacts:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/4.6.0-rc1/ 
> 
> 
> The staging repo:
> 
> https://repository.apache.org/content/repositories/orgapacherocketmq-1033/ 
> 
> 
> Git tag for the release:
> 
> https://github.com/apache/rocketmq/tree/release-4.6.0 
> 
> 
> Hash for the release tag:
> 
> d1b4e47c26576cf4fa543bbdd8c6f09643220bed
> 
> 
> 
> Release Notes:
> 
> https://rocketmq.apache.org/release_notes/release-notes-4.6.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 
> 
> 
> 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: [ANNOUNCE]New Committers of Apache RocketMQ: Chen Guangsheng, Jin Rongtong and Fang Jian

[Gosling Von]

Great, congrats ~

Thanks very much for every active participation and look forward to more 
cooperation works from Apache RocketMQ community. That's a great community ~


Best Regards,
Von Gosling

> On Dec 20, 2019, at 12:08 PM, ShannonDing  wrote:
> 
> Hi Apache RocketMQ Community,
> 
> 
> 
> The Project Management Committee (PMC) for Apache RocketMQ has invited
> 
>   Chen Guangsheng(apache id: chenguangsheng),
> 
>   Jin Rongtong(apache id: jinrongtong),
> 
>   Fang Jian(apache id: fangjian0423)
> 
> to become a committer, and we are pleased to announce that both of them have 
> accepted. 
> 
> 
> 
> Congrats, guys :-)
> 
> 
> 
> Notice: Being a committer enables easier contribution to the project since 
> there is no need to go via the patch submission process. This should enable 
> better productivity. 
> 
> 
> 
> Best Wishes,
> 
> ShannonDing
> 
> 
> 
> 

Re: [DISCUSS] RIP-14 RocketMQ Community Operation Conventions

[Gosling Von]

Hi,

Thanks jin. I don't have problem with the proposal. Convention upgrade is very 
pressing and important, we could use it to guide RocketMQ 5.0 architectural 
upgrades. 

But I would like to hear something different from our users, contributors, 
committers, pmc members and release managers. After all, this proposal involves 
how do we work together :-)

Best Regards,
Von Gosling

> On Jul 2, 2020, at 10:06 AM, jinrongtong5  wrote:
> 
> Hi RocketMQ Community,
> 
> Currently, Apache RocketMQ is becoming more and more active, and developers 
> from all over the world are involved in the construction of Apache RocketMQ, 
> but at the same time, we also found some problems:
> 
> Chaotic commit messages
> Confusing name of issues and pull requests
> Irregular merging behavior
> Confusing labels on issues and pull requests
> 
> These problems hindered the healthy development of RocketMQ Community.
> 
> So I think it is a good choice to start a new RIP to standardize contributor 
> and committer behavior.
> 
> I submitted RIP-14 RocketMQ Community Operation Conventions, which describes 
> the specific conventions in more detail.  I hope to hear more voices from the 
> community. So please tell me your thoughts by replying to this email or 
> commenting on google docs.
> 
> 
> 
> Best Regards!
> Rongtong Jin
> 
> 
> RIP-14 RocketMQ Community Operation Conventions
> https://docs.google.com/document/d/1fo_Z4_nUOyykkmQOE2kEmxcLwhhFiQENQwQiy852XUM/edit#heading=h.nwczedg8v2na