Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (binding). Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Oct 30, 2019 at 9:48 AM David Nalley wrote: > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== > > Tencent is committed
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 On Tue, Oct 29, 2019 at 21:30, Saisai Shao wrote: > +1 (non-binding). > > Thanks > Saisai > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > +1 binding > > Good luck. > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > +1 (binding) > > > > > > Go TubeMQ. > > > > > > Regards, > > > Dave > > > > > > Sent from my iPhone > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > > > Hi folks, > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > > > Apache Incubator. > > > > > > > > Please cast your vote: > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > [ ] +0, I don't care either way > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > =Abstract= > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > > > Tencent Big Data since 2013. It focuses on high-performance storage > > > > and transmission of massive data in big data scenarios.After nearly > > > > seven years of massive data precipitation, TubeMQ has certain > > > > advantages in production practice (stability + performance) and low > > > > cost compared to many open source MQ projects. > > > > > > > > =Proposal= > > > > > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > > > small amount of data loss scenarios under abnormal conditions, such > as > > > > massive log collection, indicator statistics and monitoring, etc. > > > > TubeMQ does not support highly reliable data transmission services > > > > yet. It could be on a future project roadmap, as many other MQs. but > > > > not today. > > > > > > > > =Rationale= > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > publish-subscribe pattern, aka pub-sub. > > > > In this pattern, producers publish messages to topics while consumers > > > > subscribe to those topics. After incoming messages get proceeded, > > > > consumers send an acknowledgement back to producer. Once a > > > > subscription has been created, all messages will be tracked and > > > > retained by TubeMQ, even if the consumer go offline for some reasons. > > > > Retained messages will be discarded only when a consumer acknowledges > > > > that they've been successfully processed. > > > > > > > > Portal is responsible for interact with user and admin system which > > > > include two parts: API and web portal. > > > > > > > > Master is controller of the cluster, which include one or multiple > > > > master node(s) which is responsible for managing state of cluster, > > > > resource scheduling, authentication check and maintaining of > metadata. > > > > As a reliable system, TubeMQ provides HA solution for master node. > > > > > > > > Broker is responsible for data store which include a cluster of > broker > > > > nodes. Every broker node is managing a set of topics, include: > append, > > > > delete, update, query of topic information. In TubeMQ, these brokers > > > > can be horizontal scaled and can be very large size for massive data > > > > case. > > > > > > > > Client is responsible for producing and consuming messages. When a > > > > pub-sub topic get setup, we can support two ways (push and pull) for > > > > delivering message from producers to consumers. > > > > > > > > Zookeeper is for storing offset of messages which is used to recover > > > > topic during some components get failed. > > > > > > > > > > > > =Initial Goals= > > > > > > > > The initial goal will be to move the current codebase in github’s > > > > repository under Tencent account to Apache and integrate with the > > > > Apache development process and infrastructure. > > > > A primary goal of incubation will be to grow and diversify the TubeMQ > > > > community. We are well aware that the project community is largely > > > > comprised of individuals from a single company. We aim to change that > > > > during incubation. > > > > > > > > =Current Status= > > > > > > > > As previously mentioned, TubeMQ is under active development at > > > > Tencent, and is being used in processing large volumes of data for > > > > most services and products. > > > > > > > > =Meritocracy= > > > > > > > > We value meritocracy and we understand that it is the basis for an > > > > open community that encourages multiple companies and individuals to > > > > contribute and be invested in the project’s future. We will encourage > > > > and monitor participation and make sure to extend privileges and > > > > responsibilities to all contributors. > > > > > > > > =Community= > > > > > > > > TubeMQ is currently being used by developers at Tencent and a growing > > > > number of users are actively using it in production environments. > > > > TubeMQ has received contributions from developers
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1（non-binding） > > -- Forwarded message - > 发件人： David Nalley > Date: 2019年10月30日周三 上午9:48 > Subject: [VOTE] Accept TubeMQ into the Apache Incubator > To: > > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > >
ตอบกลับ: Re: [VOTE] Accept TubeMQ into the Apache Incubator
ส่งจากสมาร์ทโฟน Samsung Galaxy ของฉัน ข้อความดั้งเดิม จาก: Kenneth Knowles วันที่: 31/10/19 11:19 (GMT+07:00) ถึง: general เรื่อง: Re: [VOTE] Accept TubeMQ into the Apache Incubator +1 (binding) On Wed, Oct 30, 2019 at 8:07 PM Goson zhang wrote: > +1（non-binding） > > 发件人： David Nalley > Date: 2019年10月30日周三 上午9:48 > Subject: [VOTE] Accept TubeMQ into the Apache Incubator > To: > > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, i
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (binding) On Wed, Oct 30, 2019 at 8:07 PM Goson zhang wrote: >+1（non-binding） > > 发件人： David Nalley > Date: 2019年10月30日周三 上午9:48 > Subject: [VOTE] Accept TubeMQ into the Apache Incubator > To: > > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1（non-binding） 发件人： David Nalley Date: 2019年10月30日周三 上午9:48 Subject: [VOTE] Accept TubeMQ into the Apache Incubator To: Hi folks, The [DISCUSS] thread on TubeMQ has died down. Accordingly, I would like to call a VOTE to accept TubeMQ into the Apache Incubator. Please cast your vote: [ ] +1, bring TubeMQ into the Incubator [ ] +0, I don't care either way [ ] -1, do not bring TubeMQ into the Incubator, because... The vote will open at least for 72 hours and only votes from the Incubator PMC are binding, but votes from everyone are welcome. =Abstract= TubeMQ is a distributed messaging queue (MQ) system developed by Tencent Big Data since 2013. It focuses on high-performance storage and transmission of massive data in big data scenarios.After nearly seven years of massive data precipitation, TubeMQ has certain advantages in production practice (stability + performance) and low cost compared to many open source MQ projects. =Proposal= TubeMQ is suitable for high concurrency, massive data and tolerates a small amount of data loss scenarios under abnormal conditions, such as massive log collection, indicator statistics and monitoring, etc. TubeMQ does not support highly reliable data transmission services yet. It could be on a future project roadmap, as many other MQs. but not today. =Rationale= Just like other message queue systems, TubeMQ is built on the publish-subscribe pattern, aka pub-sub. In this pattern, producers publish messages to topics while consumers subscribe to those topics. After incoming messages get proceeded, consumers send an acknowledgement back to producer. Once a subscription has been created, all messages will be tracked and retained by TubeMQ, even if the consumer go offline for some reasons. Retained messages will be discarded only when a consumer acknowledges that they've been successfully processed. Portal is responsible for interact with user and admin system which include two parts: API and web portal. Master is controller of the cluster, which include one or multiple master node(s) which is responsible for managing state of cluster, resource scheduling, authentication check and maintaining of metadata. As a reliable system, TubeMQ provides HA solution for master node. Broker is responsible for data store which include a cluster of broker nodes. Every broker node is managing a set of topics, include: append, delete, update, query of topic information. In TubeMQ, these brokers can be horizontal scaled and can be very large size for massive data case. Client is responsible for producing and consuming messages. When a pub-sub topic get setup, we can support two ways (push and pull) for delivering message from producers to consumers. Zookeeper is for storing offset of messages which is used to recover topic during some components get failed. =Initial Goals= The initial goal will be to move the current codebase in github’s repository under Tencent account to Apache and integrate with the Apache development process and infrastructure. A primary goal of incubation will be to grow and diversify the TubeMQ community. We are well aware that the project community is largely comprised of individuals from a single company. We aim to change that during incubation. =Current Status= As previously mentioned, TubeMQ is under active development at Tencent, and is being used in processing large volumes of data for most services and products. =Meritocracy= We value meritocracy and we understand that it is the basis for an open community that encourages multiple companies and individuals to contribute and be invested in the project’s future. We will encourage and monitor participation and make sure to extend privileges and responsibilities to all contributors. =Community= TubeMQ is currently being used by developers at Tencent and a growing number of users are actively using it in production environments. TubeMQ has received contributions from developers working outside of Tencent since it was open sourced on github in September 2019 By bringing TubeMQ to Apache we aim to assure current and future contributors that the TubeMQ community is neutral, meritocratic, and open, in order to broaden and diversity the user and developer community. =Core Developers= TubeMQ was initially developed at Tencent and is under active development. We believe Tencent will be of interest to a broad range of users and developers and that incubating the project at the ASF will help us build a diverse, sustainable community. =Alignment= TubeMQ utilizes other Apache projects such as Hadoop, HBase and Zookeeper. We anticipate integration with additional Apache projects as the TubeMQ community and interest in the project grows. =Known Risks= ==Orphaned Products== Tencent is committed to the future development of TubeMQ and understands that graduation to a TLP, while preferable, is not the only positive outcome of incubation. Should the TubeMQ project be accepted by the Incubator,
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1, binding Best Regards, Von Gosling > On Oct 30, 2019, at 9:48 AM, David Nalley wrote: > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== > > Tencent is
Re: [VOTE] Accept TubeMQ into the Apache Incubator
On Wed, Oct 30, 2019 at 2:48 AM David Nalley wrote: > ...I would like to call a VOTE to accept TubeMQ into the > Apache Incubator +1, binding -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (binding) Regards, Woonsan On Wed, Oct 30, 2019 at 10:48 AM David Nalley wrote: > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== > > Tencent is committed to the future development of
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 Binding -KAM On 10/30/2019 3:08 AM, Kevin Ratnasekera wrote: > +1 ( binding ) > > On Wed, Oct 30, 2019 at 10:38 AM vintagewang wrote: > >> +1 >> >> On Wed, Oct 30, 2019 at 9:48 AM David Nalley wrote: >> >>> Hi folks, >>> >>> The [DISCUSS] thread on TubeMQ has died down. >>> >>> Accordingly, I would like to call a VOTE to accept TubeMQ into the >>> Apache Incubator. >>> >>> Please cast your vote: >>> >>> [ ] +1, bring TubeMQ into the Incubator >>> [ ] +0, I don't care either way >>> [ ] -1, do not bring TubeMQ into the Incubator, because... >>> >>> The vote will open at least for 72 hours and only votes from the >>> Incubator PMC are binding, but votes from everyone are welcome. >>> >>> =Abstract= >>> >>> TubeMQ is a distributed messaging queue (MQ) system developed by >>> Tencent Big Data since 2013. It focuses on high-performance storage >>> and transmission of massive data in big data scenarios.After nearly >>> seven years of massive data precipitation, TubeMQ has certain >>> advantages in production practice (stability + performance) and low >>> cost compared to many open source MQ projects. >>> >>> =Proposal= >>> >>> TubeMQ is suitable for high concurrency, massive data and tolerates a >>> small amount of data loss scenarios under abnormal conditions, such as >>> massive log collection, indicator statistics and monitoring, etc. >>> TubeMQ does not support highly reliable data transmission services >>> yet. It could be on a future project roadmap, as many other MQs. but >>> not today. >>> >>> =Rationale= >>> >>> Just like other message queue systems, TubeMQ is built on the >>> publish-subscribe pattern, aka pub-sub. >>> In this pattern, producers publish messages to topics while consumers >>> subscribe to those topics. After incoming messages get proceeded, >>> consumers send an acknowledgement back to producer. Once a >>> subscription has been created, all messages will be tracked and >>> retained by TubeMQ, even if the consumer go offline for some reasons. >>> Retained messages will be discarded only when a consumer acknowledges >>> that they've been successfully processed. >>> >>> Portal is responsible for interact with user and admin system which >>> include two parts: API and web portal. >>> >>> Master is controller of the cluster, which include one or multiple >>> master node(s) which is responsible for managing state of cluster, >>> resource scheduling, authentication check and maintaining of metadata. >>> As a reliable system, TubeMQ provides HA solution for master node. >>> >>> Broker is responsible for data store which include a cluster of broker >>> nodes. Every broker node is managing a set of topics, include: append, >>> delete, update, query of topic information. In TubeMQ, these brokers >>> can be horizontal scaled and can be very large size for massive data >>> case. >>> >>> Client is responsible for producing and consuming messages. When a >>> pub-sub topic get setup, we can support two ways (push and pull) for >>> delivering message from producers to consumers. >>> >>> Zookeeper is for storing offset of messages which is used to recover >>> topic during some components get failed. >>> >>> >>> =Initial Goals= >>> >>> The initial goal will be to move the current codebase in github’s >>> repository under Tencent account to Apache and integrate with the >>> Apache development process and infrastructure. >>> A primary goal of incubation will be to grow and diversify the TubeMQ >>> community. We are well aware that the project community is largely >>> comprised of individuals from a single company. We aim to change that >>> during incubation. >>> >>> =Current Status= >>> >>> As previously mentioned, TubeMQ is under active development at >>> Tencent, and is being used in processing large volumes of data for >>> most services and products. >>> >>> =Meritocracy= >>> >>> We value meritocracy and we understand that it is the basis for an >>> open community that encourages multiple companies and individuals to >>> contribute and be invested in the project’s future. We will encourage >>> and monitor participation and make sure to extend privileges and >>> responsibilities to all contributors. >>> >>> =Community= >>> >>> TubeMQ is currently being used by developers at Tencent and a growing >>> number of users are actively using it in production environments. >>> TubeMQ has received contributions from developers working outside of >>> Tencent since it was open sourced on github in September 2019 By >>> bringing TubeMQ to Apache we aim to assure current and future >>> contributors that the TubeMQ community is neutral, meritocratic, and >>> open, in order to broaden and diversity the user and developer >>> community. >>> >>> =Core Developers= >>> >>> TubeMQ was initially developed at Tencent and is under active >>> development. We believe Tencent will be of interest to a broad range >>> of users and developers and that incubating the project at the ASF >>> will help us build a diverse,
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 ( binding ) On Wed, Oct 30, 2019 at 10:38 AM vintagewang wrote: > +1 > > On Wed, Oct 30, 2019 at 9:48 AM David Nalley wrote: > > > Hi folks, > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > Apache Incubator. > > > > Please cast your vote: > > > > [ ] +1, bring TubeMQ into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > > Incubator PMC are binding, but votes from everyone are welcome. > > > > =Abstract= > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > Tencent Big Data since 2013. It focuses on high-performance storage > > and transmission of massive data in big data scenarios.After nearly > > seven years of massive data precipitation, TubeMQ has certain > > advantages in production practice (stability + performance) and low > > cost compared to many open source MQ projects. > > > > =Proposal= > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > small amount of data loss scenarios under abnormal conditions, such as > > massive log collection, indicator statistics and monitoring, etc. > > TubeMQ does not support highly reliable data transmission services > > yet. It could be on a future project roadmap, as many other MQs. but > > not today. > > > > =Rationale= > > > > Just like other message queue systems, TubeMQ is built on the > > publish-subscribe pattern, aka pub-sub. > > In this pattern, producers publish messages to topics while consumers > > subscribe to those topics. After incoming messages get proceeded, > > consumers send an acknowledgement back to producer. Once a > > subscription has been created, all messages will be tracked and > > retained by TubeMQ, even if the consumer go offline for some reasons. > > Retained messages will be discarded only when a consumer acknowledges > > that they've been successfully processed. > > > > Portal is responsible for interact with user and admin system which > > include two parts: API and web portal. > > > > Master is controller of the cluster, which include one or multiple > > master node(s) which is responsible for managing state of cluster, > > resource scheduling, authentication check and maintaining of metadata. > > As a reliable system, TubeMQ provides HA solution for master node. > > > > Broker is responsible for data store which include a cluster of broker > > nodes. Every broker node is managing a set of topics, include: append, > > delete, update, query of topic information. In TubeMQ, these brokers > > can be horizontal scaled and can be very large size for massive data > > case. > > > > Client is responsible for producing and consuming messages. When a > > pub-sub topic get setup, we can support two ways (push and pull) for > > delivering message from producers to consumers. > > > > Zookeeper is for storing offset of messages which is used to recover > > topic during some components get failed. > > > > > > =Initial Goals= > > > > The initial goal will be to move the current codebase in github’s > > repository under Tencent account to Apache and integrate with the > > Apache development process and infrastructure. > > A primary goal of incubation will be to grow and diversify the TubeMQ > > community. We are well aware that the project community is largely > > comprised of individuals from a single company. We aim to change that > > during incubation. > > > > =Current Status= > > > > As previously mentioned, TubeMQ is under active development at > > Tencent, and is being used in processing large volumes of data for > > most services and products. > > > > =Meritocracy= > > > > We value meritocracy and we understand that it is the basis for an > > open community that encourages multiple companies and individuals to > > contribute and be invested in the project’s future. We will encourage > > and monitor participation and make sure to extend privileges and > > responsibilities to all contributors. > > > > =Community= > > > > TubeMQ is currently being used by developers at Tencent and a growing > > number of users are actively using it in production environments. > > TubeMQ has received contributions from developers working outside of > > Tencent since it was open sourced on github in September 2019 By > > bringing TubeMQ to Apache we aim to assure current and future > > contributors that the TubeMQ community is neutral, meritocratic, and > > open, in order to broaden and diversity the user and developer > > community. > > > > =Core Developers= > > > > TubeMQ was initially developed at Tencent and is under active > > development. We believe Tencent will be of interest to a broad range > > of users and developers and that incubating the project at the ASF > > will help us build a diverse, sustainable community. > > > > =Alignment= > > > > TubeMQ utilizes other
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 On Wed, Oct 30, 2019 at 9:48 AM David Nalley wrote: > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== > > Tencent is committed to the future development of TubeMQ and > understands that
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding) -- Anu On Tue, Oct 29, 2019 at 9:59 PM 李响 wrote: > +1 > > > > 发件人： David Nalley > > Date: 2019年10月30日周三 上午9:48 > > Subject: [VOTE] Accept TubeMQ into the Apache Incubator > > To: > > > > > > Hi folks, > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > Apache Incubator. > > > > Please cast your vote: > > > > [ ] +1, bring TubeMQ into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > > Incubator PMC are binding, but votes from everyone are welcome. > > > > =Abstract= > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > Tencent Big Data since 2013. It focuses on high-performance storage > > and transmission of massive data in big data scenarios.After nearly > > seven years of massive data precipitation, TubeMQ has certain > > advantages in production practice (stability + performance) and low > > cost compared to many open source MQ projects. > > > > =Proposal= > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > small amount of data loss scenarios under abnormal conditions, such as > > massive log collection, indicator statistics and monitoring, etc. > > TubeMQ does not support highly reliable data transmission services > > yet. It could be on a future project roadmap, as many other MQs. but > > not today. > > > > =Rationale= > > > > Just like other message queue systems, TubeMQ is built on the > > publish-subscribe pattern, aka pub-sub. > > In this pattern, producers publish messages to topics while consumers > > subscribe to those topics. After incoming messages get proceeded, > > consumers send an acknowledgement back to producer. Once a > > subscription has been created, all messages will be tracked and > > retained by TubeMQ, even if the consumer go offline for some reasons. > > Retained messages will be discarded only when a consumer acknowledges > > that they've been successfully processed. > > > > Portal is responsible for interact with user and admin system which > > include two parts: API and web portal. > > > > Master is controller of the cluster, which include one or multiple > > master node(s) which is responsible for managing state of cluster, > > resource scheduling, authentication check and maintaining of metadata. > > As a reliable system, TubeMQ provides HA solution for master node. > > > > Broker is responsible for data store which include a cluster of broker > > nodes. Every broker node is managing a set of topics, include: append, > > delete, update, query of topic information. In TubeMQ, these brokers > > can be horizontal scaled and can be very large size for massive data > > case. > > > > Client is responsible for producing and consuming messages. When a > > pub-sub topic get setup, we can support two ways (push and pull) for > > delivering message from producers to consumers. > > > > Zookeeper is for storing offset of messages which is used to recover > > topic during some components get failed. > > > > > > =Initial Goals= > > > > The initial goal will be to move the current codebase in github’s > > repository under Tencent account to Apache and integrate with the > > Apache development process and infrastructure. > > A primary goal of incubation will be to grow and diversify the TubeMQ > > community. We are well aware that the project community is largely > > comprised of individuals from a single company. We aim to change that > > during incubation. > > > > =Current Status= > > > > As previously mentioned, TubeMQ is under active development at > > Tencent, and is being used in processing large volumes of data for > > most services and products. > > > > =Meritocracy= > > > > We value meritocracy and we understand that it is the basis for an > > open community that encourages multiple companies and individuals to > > contribute and be invested in the project’s future. We will encourage > > and monitor participation and make sure to extend privileges and > > responsibilities to all contributors. > > > > =Community= > > > > TubeMQ is currently being used by developers at Tencent and a growing > > number of users are actively using it in production environments. > > TubeMQ has received contributions from developers working outside of > > Tencent since it was open sourced on github in September 2019 By > > bringing TubeMQ to Apache we aim to assure current and future > > contributors that the TubeMQ community is neutral, meritocratic, and > > open, in order to broaden and diversity the user and developer > > community. > > > > =Core Developers= > > > > TubeMQ was initially developed at Tencent and is under active > > development. We believe Tencent will be of interest to a broad range > > of users and developers and that incubating the project at the ASF > > will help us build a diverse,
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 > 发件人： David Nalley > Date: 2019年10月30日周三 上午9:48 > Subject: [VOTE] Accept TubeMQ into the Apache Incubator > To: > > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== > > Tencent is
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (binding) Good luck ! Regards JB On 30/10/2019 02:48, David Nalley wrote: Hi folks, The [DISCUSS] thread on TubeMQ has died down. Accordingly, I would like to call a VOTE to accept TubeMQ into the Apache Incubator. Please cast your vote: [ ] +1, bring TubeMQ into the Incubator [ ] +0, I don't care either way [ ] -1, do not bring TubeMQ into the Incubator, because... The vote will open at least for 72 hours and only votes from the Incubator PMC are binding, but votes from everyone are welcome. =Abstract= TubeMQ is a distributed messaging queue (MQ) system developed by Tencent Big Data since 2013. It focuses on high-performance storage and transmission of massive data in big data scenarios.After nearly seven years of massive data precipitation, TubeMQ has certain advantages in production practice (stability + performance) and low cost compared to many open source MQ projects. =Proposal= TubeMQ is suitable for high concurrency, massive data and tolerates a small amount of data loss scenarios under abnormal conditions, such as massive log collection, indicator statistics and monitoring, etc. TubeMQ does not support highly reliable data transmission services yet. It could be on a future project roadmap, as many other MQs. but not today. =Rationale= Just like other message queue systems, TubeMQ is built on the publish-subscribe pattern, aka pub-sub. In this pattern, producers publish messages to topics while consumers subscribe to those topics. After incoming messages get proceeded, consumers send an acknowledgement back to producer. Once a subscription has been created, all messages will be tracked and retained by TubeMQ, even if the consumer go offline for some reasons. Retained messages will be discarded only when a consumer acknowledges that they've been successfully processed. Portal is responsible for interact with user and admin system which include two parts: API and web portal. Master is controller of the cluster, which include one or multiple master node(s) which is responsible for managing state of cluster, resource scheduling, authentication check and maintaining of metadata. As a reliable system, TubeMQ provides HA solution for master node. Broker is responsible for data store which include a cluster of broker nodes. Every broker node is managing a set of topics, include: append, delete, update, query of topic information. In TubeMQ, these brokers can be horizontal scaled and can be very large size for massive data case. Client is responsible for producing and consuming messages. When a pub-sub topic get setup, we can support two ways (push and pull) for delivering message from producers to consumers. Zookeeper is for storing offset of messages which is used to recover topic during some components get failed. =Initial Goals= The initial goal will be to move the current codebase in github’s repository under Tencent account to Apache and integrate with the Apache development process and infrastructure. A primary goal of incubation will be to grow and diversify the TubeMQ community. We are well aware that the project community is largely comprised of individuals from a single company. We aim to change that during incubation. =Current Status= As previously mentioned, TubeMQ is under active development at Tencent, and is being used in processing large volumes of data for most services and products. =Meritocracy= We value meritocracy and we understand that it is the basis for an open community that encourages multiple companies and individuals to contribute and be invested in the project’s future. We will encourage and monitor participation and make sure to extend privileges and responsibilities to all contributors. =Community= TubeMQ is currently being used by developers at Tencent and a growing number of users are actively using it in production environments. TubeMQ has received contributions from developers working outside of Tencent since it was open sourced on github in September 2019 By bringing TubeMQ to Apache we aim to assure current and future contributors that the TubeMQ community is neutral, meritocratic, and open, in order to broaden and diversity the user and developer community. =Core Developers= TubeMQ was initially developed at Tencent and is under active development. We believe Tencent will be of interest to a broad range of users and developers and that incubating the project at the ASF will help us build a diverse, sustainable community. =Alignment= TubeMQ utilizes other Apache projects such as Hadoop, HBase and Zookeeper. We anticipate integration with additional Apache projects as the TubeMQ community and interest in the project grows. =Known Risks= ==Orphaned Products== Tencent is committed to the future development of TubeMQ and understands that graduation to a TLP, while preferable, is not the only positive outcome of incubation. Should the TubeMQ project be accepted by the Incubator, the prospective PPMC would be willing to agree
Re: [VOTE] Accept TubeMQ into the Apache Incubator
Hi, +1 (binding) Kind Regards, Furkan KAMACI 30 Eki 2019 Çar, saat 06:12 tarihinde Junjie Chen şunu yazdı: > +1 (non-binding) > > > ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > > > > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" < > dolphinsched...@gmail.com> > > เขียนว่า > > > > > +1 (non-binding). > > > good luck！ > > > > > > — > > > > > > *DolphinScheduler(Incubator) *PPMC > > > *Lidong Dai * > > > > > > lidong@outlook.com > > > > > > — > > > > > > On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao > > > wrote: > > > > > > > +1 (non-binding). > > > > > > > > Thanks > > > > Saisai > > > > > > > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > > > > > > > +1 binding > > > > > Good luck. > > > > > > > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > Go TubeMQ. > > > > > > > > > > > > Regards, > > > > > > Dave > > > > > > > > > > > > Sent from my iPhone > > > > > > > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley > wrote: > > > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into > the > > > > > > > Apache Incubator. > > > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > > > > [ ] +0, I don't care either way > > > > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > > > > > > > The vote will open at least for 72 hours and only votes from > the > > > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > > > > > =Abstract= > > > > > > > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed > by > > > > > > > Tencent Big Data since 2013. It focuses on high-performance > storage > > > > > > > and transmission of massive data in big data scenarios.After > nearly > > > > > > > seven years of massive data precipitation, TubeMQ has certain > > > > > > > advantages in production practice (stability + performance) > and low > > > > > > > cost compared to many open source MQ projects. > > > > > > > > > > > > > > =Proposal= > > > > > > > > > > > > > > TubeMQ is suitable for high concurrency, massive data and > > > tolerates a > > > > > > > small amount of data loss scenarios under abnormal conditions, > such > > > > as > > > > > > > massive log collection, indicator statistics and monitoring, > etc. > > > > > > > TubeMQ does not support highly reliable data transmission > services > > > > > > > yet. It could be on a future project roadmap, as many other > MQs. > > > but > > > > > > > not today. > > > > > > > > > > > > > > =Rationale= > > > > > > > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > > > > publish-subscribe pattern, aka pub-sub. > > > > > > > In this pattern, producers publish messages to topics while > > > consumers > > > > > > > subscribe to those topics. After incoming messages get > proceeded, > > > > > > > consumers send an acknowledgement back to producer. Once a > > > > > > > subscription has been created, all messages will be tracked and > > > > > > > retained by TubeMQ, even if the consumer go offline for some > > > reasons. > > > > > > > Retained messages will be discarded only when a consumer > > > acknowledges > > > > > > > that they've been successfully processed. > > > > > > > > > > > > > > Portal is responsible for interact with user and admin system > which > > > > > > > include two parts: API and web portal. > > > > > > > > > > > > > > Master is controller of the cluster, which include one or > multiple > > > > > > > master node(s) which is responsible for managing state of > cluster, > > > > > > > resource scheduling, authentication check and maintaining of > > > > metadata. > > > > > > > As a reliable system, TubeMQ provides HA solution for master > node. > > > > > > > > > > > > > > Broker is responsible for data store which include a cluster of > > > > broker > > > > > > > nodes. Every broker node is managing a set of topics, include: > > > > append, > > > > > > > delete, update, query of topic information. In TubeMQ, these > > > brokers > > > > > > > can be horizontal scaled and can be very large size for massive > > > data > > > > > > > case. > > > > > > > > > > > > > > Client is responsible for producing and consuming messages. > When a > > > > > > > pub-sub topic get setup, we can support two ways (push and > pull) > > > for > > > > > > > delivering message from producers to consumers. > > > > > > > > > > > > > > Zookeeper is for storing offset of messages which is used to > > > recover > > > > > > > topic during some components get failed. > > > > > > > > > > > > > > > > > > > > > =Initial Goals= > > > > > > > > > > > > > > The initial goal will be to move the current codebase in > github’s > > > > > > > repository under Tencent
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding) ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" > เขียนว่า > > > +1 (non-binding). > > good luck！ > > > > — > > > > *DolphinScheduler(Incubator) *PPMC > > *Lidong Dai * > > > > lidong@outlook.com > > > > — > > > > On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao > > wrote: > > > > > +1 (non-binding). > > > > > > Thanks > > > Saisai > > > > > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > > > > > +1 binding > > > > Good luck. > > > > > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > > > > > +1 (binding) > > > > > > > > > > Go TubeMQ. > > > > > > > > > > Regards, > > > > > Dave > > > > > > > > > > Sent from my iPhone > > > > > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > > > > > Apache Incubator. > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > > > [ ] +0, I don't care either way > > > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > > > =Abstract= > > > > > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > > > > > Tencent Big Data since 2013. It focuses on high-performance storage > > > > > > and transmission of massive data in big data scenarios.After nearly > > > > > > seven years of massive data precipitation, TubeMQ has certain > > > > > > advantages in production practice (stability + performance) and low > > > > > > cost compared to many open source MQ projects. > > > > > > > > > > > > =Proposal= > > > > > > > > > > > > TubeMQ is suitable for high concurrency, massive data and > > tolerates a > > > > > > small amount of data loss scenarios under abnormal conditions, such > > > as > > > > > > massive log collection, indicator statistics and monitoring, etc. > > > > > > TubeMQ does not support highly reliable data transmission services > > > > > > yet. It could be on a future project roadmap, as many other MQs. > > but > > > > > > not today. > > > > > > > > > > > > =Rationale= > > > > > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > > > publish-subscribe pattern, aka pub-sub. > > > > > > In this pattern, producers publish messages to topics while > > consumers > > > > > > subscribe to those topics. After incoming messages get proceeded, > > > > > > consumers send an acknowledgement back to producer. Once a > > > > > > subscription has been created, all messages will be tracked and > > > > > > retained by TubeMQ, even if the consumer go offline for some > > reasons. > > > > > > Retained messages will be discarded only when a consumer > > acknowledges > > > > > > that they've been successfully processed. > > > > > > > > > > > > Portal is responsible for interact with user and admin system which > > > > > > include two parts: API and web portal. > > > > > > > > > > > > Master is controller of the cluster, which include one or multiple > > > > > > master node(s) which is responsible for managing state of cluster, > > > > > > resource scheduling, authentication check and maintaining of > > > metadata. > > > > > > As a reliable system, TubeMQ provides HA solution for master node. > > > > > > > > > > > > Broker is responsible for data store which include a cluster of > > > broker > > > > > > nodes. Every broker node is managing a set of topics, include: > > > append, > > > > > > delete, update, query of topic information. In TubeMQ, these > > brokers > > > > > > can be horizontal scaled and can be very large size for massive > > data > > > > > > case. > > > > > > > > > > > > Client is responsible for producing and consuming messages. When a > > > > > > pub-sub topic get setup, we can support two ways (push and pull) > > for > > > > > > delivering message from producers to consumers. > > > > > > > > > > > > Zookeeper is for storing offset of messages which is used to > > recover > > > > > > topic during some components get failed. > > > > > > > > > > > > > > > > > > =Initial Goals= > > > > > > > > > > > > The initial goal will be to move the current codebase in github’s > > > > > > repository under Tencent account to Apache and integrate with the > > > > > > Apache development process and infrastructure. > > > > > > A primary goal of incubation will be to grow and diversify the > > TubeMQ > > > > > > community. We are well aware that the project community is largely > > > > > > comprised of individuals from a single company. We aim to change > > that > > > > > > during incubation. > > > > > > > > > > > > =Current Status= > > > > > > > > > >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 在 2019/10/30 上午10:00，“Dave Fisher” 写入: +1 (binding) Go TubeMQ. Regards, Dave Sent from my iPhone > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 On Wed, Oct 30, 2019 at 11:09 AM tison wrote: > +1 (non-binding) > > Best, > tison. > > > ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > > > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" < > dolphinsched...@gmail.com> > > เขียนว่า > > > > > +1 (non-binding). > > > good luck！ > > > > > > — > > > > > > *DolphinScheduler(Incubator) *PPMC > > > *Lidong Dai * > > > > > > lidong@outlook.com > > > > > > — > > > > > > On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao > > > wrote: > > > > > > > +1 (non-binding). > > > > > > > > Thanks > > > > Saisai > > > > > > > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > > > > > > > +1 binding > > > > > Good luck. > > > > > > > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > Go TubeMQ. > > > > > > > > > > > > Regards, > > > > > > Dave > > > > > > > > > > > > Sent from my iPhone > > > > > > > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley > wrote: > > > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into > > the > > > > > > > Apache Incubator. > > > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > > > > [ ] +0, I don't care either way > > > > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > > > > > > > The vote will open at least for 72 hours and only votes from > the > > > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > > > > > =Abstract= > > > > > > > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed > by > > > > > > > Tencent Big Data since 2013. It focuses on high-performance > > storage > > > > > > > and transmission of massive data in big data scenarios.After > > nearly > > > > > > > seven years of massive data precipitation, TubeMQ has certain > > > > > > > advantages in production practice (stability + performance) and > > low > > > > > > > cost compared to many open source MQ projects. > > > > > > > > > > > > > > =Proposal= > > > > > > > > > > > > > > TubeMQ is suitable for high concurrency, massive data and > > > tolerates a > > > > > > > small amount of data loss scenarios under abnormal conditions, > > such > > > > as > > > > > > > massive log collection, indicator statistics and monitoring, > etc. > > > > > > > TubeMQ does not support highly reliable data transmission > > services > > > > > > > yet. It could be on a future project roadmap, as many other > MQs. > > > but > > > > > > > not today. > > > > > > > > > > > > > > =Rationale= > > > > > > > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > > > > publish-subscribe pattern, aka pub-sub. > > > > > > > In this pattern, producers publish messages to topics while > > > consumers > > > > > > > subscribe to those topics. After incoming messages get > proceeded, > > > > > > > consumers send an acknowledgement back to producer. Once a > > > > > > > subscription has been created, all messages will be tracked and > > > > > > > retained by TubeMQ, even if the consumer go offline for some > > > reasons. > > > > > > > Retained messages will be discarded only when a consumer > > > acknowledges > > > > > > > that they've been successfully processed. > > > > > > > > > > > > > > Portal is responsible for interact with user and admin system > > which > > > > > > > include two parts: API and web portal. > > > > > > > > > > > > > > Master is controller of the cluster, which include one or > > multiple > > > > > > > master node(s) which is responsible for managing state of > > cluster, > > > > > > > resource scheduling, authentication check and maintaining of > > > > metadata. > > > > > > > As a reliable system, TubeMQ provides HA solution for master > > node. > > > > > > > > > > > > > > Broker is responsible for data store which include a cluster of > > > > broker > > > > > > > nodes. Every broker node is managing a set of topics, include: > > > > append, > > > > > > > delete, update, query of topic information. In TubeMQ, these > > > brokers > > > > > > > can be horizontal scaled and can be very large size for massive > > > data > > > > > > > case. > > > > > > > > > > > > > > Client is responsible for producing and consuming messages. > When > > a > > > > > > > pub-sub topic get setup, we can support two ways (push and > pull) > > > for > > > > > > > delivering message from producers to consumers. > > > > > > > > > > > > > > Zookeeper is for storing offset of messages which is used to > > > recover > > > > > > > topic during some components get failed. > > > > > > > > > > > > > > > > > > > > > =Initial Goals= > > > > > > > > > > > > > > The initial goal will be to move the current codebase in > github’s > > > > > > > repository under Tencent account to Apache and
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding) Best, tison. ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com> 于2019年10月30日周三 上午11:01写道： > เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" > เขียนว่า > > > +1 (non-binding). > > good luck！ > > > > — > > > > *DolphinScheduler(Incubator) *PPMC > > *Lidong Dai * > > > > lidong@outlook.com > > > > — > > > > On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao > > wrote: > > > > > +1 (non-binding). > > > > > > Thanks > > > Saisai > > > > > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > > > > > +1 binding > > > > Good luck. > > > > > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > > > > > +1 (binding) > > > > > > > > > > Go TubeMQ. > > > > > > > > > > Regards, > > > > > Dave > > > > > > > > > > Sent from my iPhone > > > > > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into > the > > > > > > Apache Incubator. > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > > > [ ] +0, I don't care either way > > > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > > > =Abstract= > > > > > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > > > > > Tencent Big Data since 2013. It focuses on high-performance > storage > > > > > > and transmission of massive data in big data scenarios.After > nearly > > > > > > seven years of massive data precipitation, TubeMQ has certain > > > > > > advantages in production practice (stability + performance) and > low > > > > > > cost compared to many open source MQ projects. > > > > > > > > > > > > =Proposal= > > > > > > > > > > > > TubeMQ is suitable for high concurrency, massive data and > > tolerates a > > > > > > small amount of data loss scenarios under abnormal conditions, > such > > > as > > > > > > massive log collection, indicator statistics and monitoring, etc. > > > > > > TubeMQ does not support highly reliable data transmission > services > > > > > > yet. It could be on a future project roadmap, as many other MQs. > > but > > > > > > not today. > > > > > > > > > > > > =Rationale= > > > > > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > > > publish-subscribe pattern, aka pub-sub. > > > > > > In this pattern, producers publish messages to topics while > > consumers > > > > > > subscribe to those topics. After incoming messages get proceeded, > > > > > > consumers send an acknowledgement back to producer. Once a > > > > > > subscription has been created, all messages will be tracked and > > > > > > retained by TubeMQ, even if the consumer go offline for some > > reasons. > > > > > > Retained messages will be discarded only when a consumer > > acknowledges > > > > > > that they've been successfully processed. > > > > > > > > > > > > Portal is responsible for interact with user and admin system > which > > > > > > include two parts: API and web portal. > > > > > > > > > > > > Master is controller of the cluster, which include one or > multiple > > > > > > master node(s) which is responsible for managing state of > cluster, > > > > > > resource scheduling, authentication check and maintaining of > > > metadata. > > > > > > As a reliable system, TubeMQ provides HA solution for master > node. > > > > > > > > > > > > Broker is responsible for data store which include a cluster of > > > broker > > > > > > nodes. Every broker node is managing a set of topics, include: > > > append, > > > > > > delete, update, query of topic information. In TubeMQ, these > > brokers > > > > > > can be horizontal scaled and can be very large size for massive > > data > > > > > > case. > > > > > > > > > > > > Client is responsible for producing and consuming messages. When > a > > > > > > pub-sub topic get setup, we can support two ways (push and pull) > > for > > > > > > delivering message from producers to consumers. > > > > > > > > > > > > Zookeeper is for storing offset of messages which is used to > > recover > > > > > > topic during some components get failed. > > > > > > > > > > > > > > > > > > =Initial Goals= > > > > > > > > > > > > The initial goal will be to move the current codebase in github’s > > > > > > repository under Tencent account to Apache and integrate with the > > > > > > Apache development process and infrastructure. > > > > > > A primary goal of incubation will be to grow and diversify the > > TubeMQ > > > > > > community. We are well aware that the project community is > largely > > > > > > comprised of individuals from a single company. We aim to change > > that > > > > > > during incubation. > > > > > > > > > > > >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
เมื่อ 30 ต.ค. 2019 9:49 AM "Scheduler dolphin" เขียนว่า > +1 (non-binding). > good luck！ > > — > > *DolphinScheduler(Incubator) *PPMC > *Lidong Dai * > > lidong@outlook.com > > — > > On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao > wrote: > > > +1 (non-binding). > > > > Thanks > > Saisai > > > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > > > +1 binding > > > Good luck. > > > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > > > +1 (binding) > > > > > > > > Go TubeMQ. > > > > > > > > Regards, > > > > Dave > > > > > > > > Sent from my iPhone > > > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > > > > > Hi folks, > > > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > > > > Apache Incubator. > > > > > > > > > > Please cast your vote: > > > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > > [ ] +0, I don't care either way > > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > =Abstract= > > > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > > > > Tencent Big Data since 2013. It focuses on high-performance storage > > > > > and transmission of massive data in big data scenarios.After nearly > > > > > seven years of massive data precipitation, TubeMQ has certain > > > > > advantages in production practice (stability + performance) and low > > > > > cost compared to many open source MQ projects. > > > > > > > > > > =Proposal= > > > > > > > > > > TubeMQ is suitable for high concurrency, massive data and > tolerates a > > > > > small amount of data loss scenarios under abnormal conditions, such > > as > > > > > massive log collection, indicator statistics and monitoring, etc. > > > > > TubeMQ does not support highly reliable data transmission services > > > > > yet. It could be on a future project roadmap, as many other MQs. > but > > > > > not today. > > > > > > > > > > =Rationale= > > > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > > publish-subscribe pattern, aka pub-sub. > > > > > In this pattern, producers publish messages to topics while > consumers > > > > > subscribe to those topics. After incoming messages get proceeded, > > > > > consumers send an acknowledgement back to producer. Once a > > > > > subscription has been created, all messages will be tracked and > > > > > retained by TubeMQ, even if the consumer go offline for some > reasons. > > > > > Retained messages will be discarded only when a consumer > acknowledges > > > > > that they've been successfully processed. > > > > > > > > > > Portal is responsible for interact with user and admin system which > > > > > include two parts: API and web portal. > > > > > > > > > > Master is controller of the cluster, which include one or multiple > > > > > master node(s) which is responsible for managing state of cluster, > > > > > resource scheduling, authentication check and maintaining of > > metadata. > > > > > As a reliable system, TubeMQ provides HA solution for master node. > > > > > > > > > > Broker is responsible for data store which include a cluster of > > broker > > > > > nodes. Every broker node is managing a set of topics, include: > > append, > > > > > delete, update, query of topic information. In TubeMQ, these > brokers > > > > > can be horizontal scaled and can be very large size for massive > data > > > > > case. > > > > > > > > > > Client is responsible for producing and consuming messages. When a > > > > > pub-sub topic get setup, we can support two ways (push and pull) > for > > > > > delivering message from producers to consumers. > > > > > > > > > > Zookeeper is for storing offset of messages which is used to > recover > > > > > topic during some components get failed. > > > > > > > > > > > > > > > =Initial Goals= > > > > > > > > > > The initial goal will be to move the current codebase in github’s > > > > > repository under Tencent account to Apache and integrate with the > > > > > Apache development process and infrastructure. > > > > > A primary goal of incubation will be to grow and diversify the > TubeMQ > > > > > community. We are well aware that the project community is largely > > > > > comprised of individuals from a single company. We aim to change > that > > > > > during incubation. > > > > > > > > > > =Current Status= > > > > > > > > > > As previously mentioned, TubeMQ is under active development at > > > > > Tencent, and is being used in processing large volumes of data for > > > > > most services and products. > > > > > > > > > > =Meritocracy= > > > > > > > > > > We value meritocracy and we understand that it is the basis for an > > > > > open community that encourages multiple companies
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding). Scheduler dolphin 于2019年10月30日周三 上午10:49写道： > +1 (non-binding). > good luck！ > > — > > *DolphinScheduler(Incubator) *PPMC > *Lidong Dai * > > lidong@outlook.com > > — > > On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao > wrote: > > > +1 (non-binding). > > > > Thanks > > Saisai > > > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > > > +1 binding > > > Good luck. > > > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > > > +1 (binding) > > > > > > > > Go TubeMQ. > > > > > > > > Regards, > > > > Dave > > > > > > > > Sent from my iPhone > > > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > > > > > Hi folks, > > > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > > > > Apache Incubator. > > > > > > > > > > Please cast your vote: > > > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > > [ ] +0, I don't care either way > > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > =Abstract= > > > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > > > > Tencent Big Data since 2013. It focuses on high-performance storage > > > > > and transmission of massive data in big data scenarios.After nearly > > > > > seven years of massive data precipitation, TubeMQ has certain > > > > > advantages in production practice (stability + performance) and low > > > > > cost compared to many open source MQ projects. > > > > > > > > > > =Proposal= > > > > > > > > > > TubeMQ is suitable for high concurrency, massive data and > tolerates a > > > > > small amount of data loss scenarios under abnormal conditions, such > > as > > > > > massive log collection, indicator statistics and monitoring, etc. > > > > > TubeMQ does not support highly reliable data transmission services > > > > > yet. It could be on a future project roadmap, as many other MQs. > but > > > > > not today. > > > > > > > > > > =Rationale= > > > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > > publish-subscribe pattern, aka pub-sub. > > > > > In this pattern, producers publish messages to topics while > consumers > > > > > subscribe to those topics. After incoming messages get proceeded, > > > > > consumers send an acknowledgement back to producer. Once a > > > > > subscription has been created, all messages will be tracked and > > > > > retained by TubeMQ, even if the consumer go offline for some > reasons. > > > > > Retained messages will be discarded only when a consumer > acknowledges > > > > > that they've been successfully processed. > > > > > > > > > > Portal is responsible for interact with user and admin system which > > > > > include two parts: API and web portal. > > > > > > > > > > Master is controller of the cluster, which include one or multiple > > > > > master node(s) which is responsible for managing state of cluster, > > > > > resource scheduling, authentication check and maintaining of > > metadata. > > > > > As a reliable system, TubeMQ provides HA solution for master node. > > > > > > > > > > Broker is responsible for data store which include a cluster of > > broker > > > > > nodes. Every broker node is managing a set of topics, include: > > append, > > > > > delete, update, query of topic information. In TubeMQ, these > brokers > > > > > can be horizontal scaled and can be very large size for massive > data > > > > > case. > > > > > > > > > > Client is responsible for producing and consuming messages. When a > > > > > pub-sub topic get setup, we can support two ways (push and pull) > for > > > > > delivering message from producers to consumers. > > > > > > > > > > Zookeeper is for storing offset of messages which is used to > recover > > > > > topic during some components get failed. > > > > > > > > > > > > > > > =Initial Goals= > > > > > > > > > > The initial goal will be to move the current codebase in github’s > > > > > repository under Tencent account to Apache and integrate with the > > > > > Apache development process and infrastructure. > > > > > A primary goal of incubation will be to grow and diversify the > TubeMQ > > > > > community. We are well aware that the project community is largely > > > > > comprised of individuals from a single company. We aim to change > that > > > > > during incubation. > > > > > > > > > > =Current Status= > > > > > > > > > > As previously mentioned, TubeMQ is under active development at > > > > > Tencent, and is being used in processing large volumes of data for > > > > > most services and products. > > > > > > > > > > =Meritocracy= > > > > > > > > > > We value meritocracy and we understand that it is the basis for an > > > > > open community that encourages multiple
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding). good luck！ — *DolphinScheduler(Incubator) *PPMC *Lidong Dai * lidong@outlook.com — On Wed, Oct 30, 2019 at 10:30 AM Saisai Shao wrote: > +1 (non-binding). > > Thanks > Saisai > > Sheng Wu 于2019年10月30日周三 上午10:03写道： > > > +1 binding > > Good luck. > > > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > > > +1 (binding) > > > > > > Go TubeMQ. > > > > > > Regards, > > > Dave > > > > > > Sent from my iPhone > > > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > > > Hi folks, > > > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > > > Apache Incubator. > > > > > > > > Please cast your vote: > > > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > > [ ] +0, I don't care either way > > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > =Abstract= > > > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > > > Tencent Big Data since 2013. It focuses on high-performance storage > > > > and transmission of massive data in big data scenarios.After nearly > > > > seven years of massive data precipitation, TubeMQ has certain > > > > advantages in production practice (stability + performance) and low > > > > cost compared to many open source MQ projects. > > > > > > > > =Proposal= > > > > > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > > > small amount of data loss scenarios under abnormal conditions, such > as > > > > massive log collection, indicator statistics and monitoring, etc. > > > > TubeMQ does not support highly reliable data transmission services > > > > yet. It could be on a future project roadmap, as many other MQs. but > > > > not today. > > > > > > > > =Rationale= > > > > > > > > Just like other message queue systems, TubeMQ is built on the > > > > publish-subscribe pattern, aka pub-sub. > > > > In this pattern, producers publish messages to topics while consumers > > > > subscribe to those topics. After incoming messages get proceeded, > > > > consumers send an acknowledgement back to producer. Once a > > > > subscription has been created, all messages will be tracked and > > > > retained by TubeMQ, even if the consumer go offline for some reasons. > > > > Retained messages will be discarded only when a consumer acknowledges > > > > that they've been successfully processed. > > > > > > > > Portal is responsible for interact with user and admin system which > > > > include two parts: API and web portal. > > > > > > > > Master is controller of the cluster, which include one or multiple > > > > master node(s) which is responsible for managing state of cluster, > > > > resource scheduling, authentication check and maintaining of > metadata. > > > > As a reliable system, TubeMQ provides HA solution for master node. > > > > > > > > Broker is responsible for data store which include a cluster of > broker > > > > nodes. Every broker node is managing a set of topics, include: > append, > > > > delete, update, query of topic information. In TubeMQ, these brokers > > > > can be horizontal scaled and can be very large size for massive data > > > > case. > > > > > > > > Client is responsible for producing and consuming messages. When a > > > > pub-sub topic get setup, we can support two ways (push and pull) for > > > > delivering message from producers to consumers. > > > > > > > > Zookeeper is for storing offset of messages which is used to recover > > > > topic during some components get failed. > > > > > > > > > > > > =Initial Goals= > > > > > > > > The initial goal will be to move the current codebase in github’s > > > > repository under Tencent account to Apache and integrate with the > > > > Apache development process and infrastructure. > > > > A primary goal of incubation will be to grow and diversify the TubeMQ > > > > community. We are well aware that the project community is largely > > > > comprised of individuals from a single company. We aim to change that > > > > during incubation. > > > > > > > > =Current Status= > > > > > > > > As previously mentioned, TubeMQ is under active development at > > > > Tencent, and is being used in processing large volumes of data for > > > > most services and products. > > > > > > > > =Meritocracy= > > > > > > > > We value meritocracy and we understand that it is the basis for an > > > > open community that encourages multiple companies and individuals to > > > > contribute and be invested in the project’s future. We will encourage > > > > and monitor participation and make sure to extend privileges and > > > > responsibilities to all contributors. > > > > > > > > =Community= > > > > > > > > TubeMQ is currently being used by developers at Tencent and a growing > > >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
เมื่อ 30 ต.ค. 2019 8:48 AM "David Nalley" เขียนว่า > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== > > Tencent is committed to the future development of TubeMQ and > understands that graduation
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (non-binding). Thanks Saisai Sheng Wu 于2019年10月30日周三 上午10:03写道： > +1 binding > Good luck. > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > +1 (binding) > > > > Go TubeMQ. > > > > Regards, > > Dave > > > > Sent from my iPhone > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > > > Hi folks, > > > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > > Apache Incubator. > > > > > > Please cast your vote: > > > > > > [ ] +1, bring TubeMQ into the Incubator > > > [ ] +0, I don't care either way > > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > > > The vote will open at least for 72 hours and only votes from the > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > =Abstract= > > > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > > Tencent Big Data since 2013. It focuses on high-performance storage > > > and transmission of massive data in big data scenarios.After nearly > > > seven years of massive data precipitation, TubeMQ has certain > > > advantages in production practice (stability + performance) and low > > > cost compared to many open source MQ projects. > > > > > > =Proposal= > > > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > > small amount of data loss scenarios under abnormal conditions, such as > > > massive log collection, indicator statistics and monitoring, etc. > > > TubeMQ does not support highly reliable data transmission services > > > yet. It could be on a future project roadmap, as many other MQs. but > > > not today. > > > > > > =Rationale= > > > > > > Just like other message queue systems, TubeMQ is built on the > > > publish-subscribe pattern, aka pub-sub. > > > In this pattern, producers publish messages to topics while consumers > > > subscribe to those topics. After incoming messages get proceeded, > > > consumers send an acknowledgement back to producer. Once a > > > subscription has been created, all messages will be tracked and > > > retained by TubeMQ, even if the consumer go offline for some reasons. > > > Retained messages will be discarded only when a consumer acknowledges > > > that they've been successfully processed. > > > > > > Portal is responsible for interact with user and admin system which > > > include two parts: API and web portal. > > > > > > Master is controller of the cluster, which include one or multiple > > > master node(s) which is responsible for managing state of cluster, > > > resource scheduling, authentication check and maintaining of metadata. > > > As a reliable system, TubeMQ provides HA solution for master node. > > > > > > Broker is responsible for data store which include a cluster of broker > > > nodes. Every broker node is managing a set of topics, include: append, > > > delete, update, query of topic information. In TubeMQ, these brokers > > > can be horizontal scaled and can be very large size for massive data > > > case. > > > > > > Client is responsible for producing and consuming messages. When a > > > pub-sub topic get setup, we can support two ways (push and pull) for > > > delivering message from producers to consumers. > > > > > > Zookeeper is for storing offset of messages which is used to recover > > > topic during some components get failed. > > > > > > > > > =Initial Goals= > > > > > > The initial goal will be to move the current codebase in github’s > > > repository under Tencent account to Apache and integrate with the > > > Apache development process and infrastructure. > > > A primary goal of incubation will be to grow and diversify the TubeMQ > > > community. We are well aware that the project community is largely > > > comprised of individuals from a single company. We aim to change that > > > during incubation. > > > > > > =Current Status= > > > > > > As previously mentioned, TubeMQ is under active development at > > > Tencent, and is being used in processing large volumes of data for > > > most services and products. > > > > > > =Meritocracy= > > > > > > We value meritocracy and we understand that it is the basis for an > > > open community that encourages multiple companies and individuals to > > > contribute and be invested in the project’s future. We will encourage > > > and monitor participation and make sure to extend privileges and > > > responsibilities to all contributors. > > > > > > =Community= > > > > > > TubeMQ is currently being used by developers at Tencent and a growing > > > number of users are actively using it in production environments. > > > TubeMQ has received contributions from developers working outside of > > > Tencent since it was open sourced on github in September 2019 By > > > bringing TubeMQ to Apache we aim to assure current and future > > > contributors that the TubeMQ community is neutral, meritocratic, and > > > open, in order to broaden and diversity the user and developer > > >
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 binding Good luck. Dave Fisher 于2019年10月30日 周三上午7:30写道： > +1 (binding) > > Go TubeMQ. > > Regards, > Dave > > Sent from my iPhone > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > > Hi folks, > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > Apache Incubator. > > > > Please cast your vote: > > > > [ ] +1, bring TubeMQ into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > > Incubator PMC are binding, but votes from everyone are welcome. > > > > =Abstract= > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > Tencent Big Data since 2013. It focuses on high-performance storage > > and transmission of massive data in big data scenarios.After nearly > > seven years of massive data precipitation, TubeMQ has certain > > advantages in production practice (stability + performance) and low > > cost compared to many open source MQ projects. > > > > =Proposal= > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > small amount of data loss scenarios under abnormal conditions, such as > > massive log collection, indicator statistics and monitoring, etc. > > TubeMQ does not support highly reliable data transmission services > > yet. It could be on a future project roadmap, as many other MQs. but > > not today. > > > > =Rationale= > > > > Just like other message queue systems, TubeMQ is built on the > > publish-subscribe pattern, aka pub-sub. > > In this pattern, producers publish messages to topics while consumers > > subscribe to those topics. After incoming messages get proceeded, > > consumers send an acknowledgement back to producer. Once a > > subscription has been created, all messages will be tracked and > > retained by TubeMQ, even if the consumer go offline for some reasons. > > Retained messages will be discarded only when a consumer acknowledges > > that they've been successfully processed. > > > > Portal is responsible for interact with user and admin system which > > include two parts: API and web portal. > > > > Master is controller of the cluster, which include one or multiple > > master node(s) which is responsible for managing state of cluster, > > resource scheduling, authentication check and maintaining of metadata. > > As a reliable system, TubeMQ provides HA solution for master node. > > > > Broker is responsible for data store which include a cluster of broker > > nodes. Every broker node is managing a set of topics, include: append, > > delete, update, query of topic information. In TubeMQ, these brokers > > can be horizontal scaled and can be very large size for massive data > > case. > > > > Client is responsible for producing and consuming messages. When a > > pub-sub topic get setup, we can support two ways (push and pull) for > > delivering message from producers to consumers. > > > > Zookeeper is for storing offset of messages which is used to recover > > topic during some components get failed. > > > > > > =Initial Goals= > > > > The initial goal will be to move the current codebase in github’s > > repository under Tencent account to Apache and integrate with the > > Apache development process and infrastructure. > > A primary goal of incubation will be to grow and diversify the TubeMQ > > community. We are well aware that the project community is largely > > comprised of individuals from a single company. We aim to change that > > during incubation. > > > > =Current Status= > > > > As previously mentioned, TubeMQ is under active development at > > Tencent, and is being used in processing large volumes of data for > > most services and products. > > > > =Meritocracy= > > > > We value meritocracy and we understand that it is the basis for an > > open community that encourages multiple companies and individuals to > > contribute and be invested in the project’s future. We will encourage > > and monitor participation and make sure to extend privileges and > > responsibilities to all contributors. > > > > =Community= > > > > TubeMQ is currently being used by developers at Tencent and a growing > > number of users are actively using it in production environments. > > TubeMQ has received contributions from developers working outside of > > Tencent since it was open sourced on github in September 2019 By > > bringing TubeMQ to Apache we aim to assure current and future > > contributors that the TubeMQ community is neutral, meritocratic, and > > open, in order to broaden and diversity the user and developer > > community. > > > > =Core Developers= > > > > TubeMQ was initially developed at Tencent and is under active > > development. We believe Tencent will be of interest to a broad range > > of users and developers and that incubating the project at the ASF > > will help us build a diverse, sustainable
Re: [VOTE] Accept TubeMQ into the Apache Incubator
Thanks David for calling the vote! I am giving my binding +1. Thanks, Junping David Nalley 于2019年10月30日周三 上午9:48写道： > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== > > Tencent is committed
Re: [VOTE] Accept TubeMQ into the Apache Incubator
+1 (binding) Go TubeMQ. Regards, Dave Sent from my iPhone > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with additional Apache projects > as the TubeMQ community and interest in the project grows. > > =Known Risks= > > ==Orphaned Products== >
