Re: [GSOC][ROCKETMQ-380] Provide a modern and friendly console for RocketMQ

[Ahmed Ifhaam]

hi yukon,

I've been working on the requirements. When i listed the features available
in cli admin tool but not in the console i found the following list. I
would like some feedback on the list before i start next step.
1. brokerConfigurationUpdate
2. BrokerConsume Stats
3. CleanExpiredCQ
4. CleanUnusedTopic
5. WipeWritePermissions
6. updateOrderConf
7. UpdateKvConf
8. DeleteKVConf
9. CheckMsgSendRT
10. clusterRT
11. CloneGroupOffset
12. ResetOffsetByTimeStamp

This is the list which i think i should implement. But i have seen in the
system labels differ a bit from the *'adminTool'*. Also though i tried the
tool i may have missed something. In that case i just want to confirm these
are not already there in the current console and these are the only things
that are not in the current console.

Thank you

On Sun, Mar 18, 2018 at 8:43 AM, yukon  wrote:

> Hi,
>
> Yes, most of the user-related features already exist, but we also need an
> operations console, more details please refer to our admin client:
> http://rocketmq.apache.org/docs/cli-admin-tool/
>
> Regards
>
> On Sun, Mar 18, 2018 at 1:03 AM, Ahmed Ifhaam 
> wrote:
>
> > hi yukon,
> >
> > I tried the commercial product. There is not much change in both except
> the
> > user interface, most of the features are already there, organizing and
> look
> > and feel of the commercial one is looking better. Before i draft the
> design
> > for my changes, I need to know whether the changes you expect are totally
> > on UI Design ? Or a new feature on analytics kind of thing ?
> >
> > Thank you
> >
> > On Fri, Mar 16, 2018 at 7:47 AM, yukon  wrote:
> >
> > > Hi,
> > >
> > > This is a commercial version[1] of apache rocketmq and could be your
> > > reference.
> > >
> > > After trying this console, hope you could draft the design ASAP and
> then
> > we
> > > can discuss based on i.
> > >
> > >
> > > Regards,
> > > yukon
> > >
> > > [1]. https://www.alibabacloud.com/product/mq
> > >
> > > On Fri, Mar 16, 2018 at 2:41 AM, Ahmed Ifhaam 
> > > wrote:
> > >
> > > > Hi yukon,
> > > >
> > > > I checked the console and after you asked I have re checked it as
> > well. I
> > > > used it with the CLI tool in parallel too.
> > > > In the requirement specification there was a reference console which
> I
> > > > mentioned in my earlier mail that I couldn't get it to run. So I'm
> not
> > > > exactly clear with the requirements. It would be a great help if
> > someone
> > > > can point me to a place where i can find the requirements. As I have
> to
> > > > prepare the proposal (27th March) please kindly take a look at this
> > ASAP.
> > > >
> > > > Thank you
> > > >
> > > > On Fri, Mar 9, 2018 at 9:05 PM, yukon  wrote:
> > > >
> > > > > Edit the subject!
> > > > >
> > > > > On Fri, Mar 9, 2018 at 10:47 PM, yukon  wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > ```
> > > > > > The other thing is what are the expected features in the new
> > console?
> > > > > > ```
> > > > > >
> > > > > > Do you check out the features in the current console[1]?
> > > > > >
> > > > > > You may have ideas about the features after trying this console
> and
> > > the
> > > > > > `admin` tool[2], then make a design and let's discuss based on
> it.
> > > > > >
> > > > > > Regards,
> > > > > > yukon
> > > > > >
> > > > > > [1]. https://github.com/apache/rocketmq-externals/tree/
> > > > > > master/rocketmq-console
> > > > > > [2].https://github.com/apache/rocketmq/blob/master/
> > > > > > distribution/bin/mqadmin
> > > > > >
> > > > > > On Thu, Mar 8, 2018 at 7:26 PM, Ahmed Ifhaam <
> > ahmedifha...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > >> HI,
> > > > > >> Regarding this RocketMQ-380,
> > > > > >> I have issues in running the referenced console when ever i try
> to
> > > > enter
> > > > > >> my
> > > > > >> personal details page is automatically redirected to home page.
> > > > > >> Hence i'm not being able to activate the messaging service
> which i
> > > > > believe
> > > > > >> should work.
> > > > > >> https://mns.console.aliyun.com/?spm=5176.2020520130.0.0.4db6
> > > > > >> 3db5cHTXtU#/list/cn-hangzhou
> > > > > >> From this link when i click activate button it is redirecting to
> > the
> > > > > home
> > > > > >> page. but according to the documentation it should take me to a
> > form
> > > > to
> > > > > >> fill my personal details. I created an account and i can login
> to
> > my
> > > > > >> account as well. Please help on this.
> > > > > >>
> > > > > >> The other thing is what are the expected features in the new
> > > console?
> > > > > >> Please give a short description.
> > > > > >>
> > > > > >> Thanks in advance.
> > > > > >>
> > > > > >> On Wed, Mar 7, 2018 at 12:40 AM, Ahmed Ifhaam <
> > > ahmedifha...@gmail.com
> > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Ok sorry, changing on bin/runbrocker.sh worked Thank you
> > > > > >> >
> > > > > >> > On Wed, Mar 7, 2018 at 12:27 AM, Sohaib Iftikhar <
> > > > > sohaib1...@gmail.com>
> > > > > >> > wrote:

Re: 答复: 答复: 答复: [GSOC|ROCKETMQ-123]Support Distributed Transactional Messaging

[yukon]

+ riven

Hi Dexin,

Riven is a very senior engineer in RocketMQ community, especially in
distributed transaction area. He is enthusiastic and will help you finished
the design.

Regards,
yukon

On Fri, Mar 16, 2018 at 10:13 PM, 李 德鑫  wrote:

> 😓Sorry, I forgot to add the link
>
>  https://docs.google.com/document/d/1HGQYPc3YtPga-jATx6whMYS7e11NQ6_
> r3tzC3yl4ulI/edit?usp=sharing
>
> 
> 发件人: 李 德鑫 
> 发送时间: 2018年3月16日 14:11:38
> 收件人: dev@rocketmq.apache.org
> 主题: 答复: 答复: 答复: [GSOC|ROCKETMQ-123]Support Distributed Transactional
> Messaging
>
> Hi yukon
>
> I've wrote a design doc about this topic, please have a look.
>
>
>
> Regards,
> Dexin
>
> 
> 发件人: yukon 
> 发送时间: 2018年3月9日 15:11:01
> 收件人: dev
> 主题: Re: 答复: 答复: [GSOC|ROCKETMQ-123]Support Distributed Transactional
> Messaging
>
> Hi Dexin,
>
> ```
> 1.  Does the transactional messaging need to be "exactly only once"
> delivered?
> ```
>
> Please check out https://issues.apache.org/jira/browse/ROCKETMQ-124
>
> ```
> 2.  Where to store the transaction state? Since the state must be
> persistent and also updated.
> ```
>
> We could reuse the rocketmq-store model to store the transaction state.
>
> And, don't worry about the dirty pages if you follow the rule: Append Only.
>
> Regards,
> yukon
>
>
>
> On Wed, Mar 7, 2018 at 12:11 PM, 李 德鑫  wrote:
>
> > Thank you, Yukon!
> >
> >
> > I still have some question about transactional messaging
> >
> >   1.  Does the transactional messaging need to be "exactly only once"
> > delivered?
> >   2.  Where to store the transaction state? Since the state must be
> > persistent and also updated.
> >
> >
> > About the second question, I've considered about some methods
> >
> >   1.  Inside of the message. But it is said that this would generate lots
> > of dirty pages on the OS.
> >   2.  In a database, especially an SQL database. Since class
> > JDBCTransactionStore already exists. But I want to know whether the DB
> will
> > be the bottleneck of performance or scalability.
> >   3.  Like Kafka, use an internal topic called Transaction log. It will
> > record all the operation about transaction states. And store the latest
> > states in the memory. If a partition crashed, It will read the log to
> > recover. But the recovery would be slow.
> >   4.  Similar to 3, store and the transaction state in the Transaction
> > log. But if there's a lot of transaction message, (I guess)this would be
> > like 1 to generate many dirty pages.
> >
> >
> > Regards,
> > Dexin
> > 
> > 发件人: yukon 
> > 发送时间: 2018年3月5日 12:28:47
> > 收件人: dev
> > 主题: Re: 答复: [GSOC|ROCKETMQ-123]Support Distributed Transactional
> Messaging
> >
> > Hi,
> >
> > The links you mentioned just are interfaces, we should implement these
> > APIs.
> >
> > Regards,
> > yukon
> >
> > On Tue, Feb 27, 2018 at 12:07 PM, 李 德鑫  wrote:
> >
> > > My previous email didn't clarify the question clearly, so I'll try to
> > make
> > > it in detail.
> > >
> > >
> > > In this jira's(https://issues.apache.org/jira/browse/ROCKETMQ-123)
> > > description:
> > >
> > >
> > >
> > >
> > > Implement a TransactionProducer and LocalTransactionChecker, guarantee
> > > message delivery and local transaction operations are atomic.
> > >
> > > The following is the simple transactional messaging flow:
> > >
> > > 1. TransactionProducer sends a half message to the broker. A half
> message
> > > means it's not confirmed and can't be delivered to the consumer.
> > >
> > > 2. TransactionProducer executes the specific local transaction.
> > >
> > > 3. Commit or Rollback the half message according to the status of the
> > > local transaction. A half message will be deleted if it's rollbacked
> and
> > > delivered to the consumer if it's committed.
> > >
> > >
> > >
> > > The 1st step I found in https://github.com/apache/
> > > rocketmq/blob/master/client/src/main/java/org/apache/
> > > rocketmq/client/impl/producer/DefaultMQProducerImpl.java#L964
> > >
> > > The 2nd step I found in https://github.com/apache/
> > > rocketmq/blob/master/client/src/main/java/org/apache/
> > > rocketmq/client/impl/producer/DefaultMQProducerImpl.java#L977
> > >
> > > The 3rd step I found in https://github.com/apache/
> > > rocketmq/blob/master/client/src/main/java/org/apache/
> > > rocketmq/client/impl/producer/DefaultMQProducerImpl.java#L1026 for
> > client
> > > and https://github.com/apache/rocketmq/blob/master/broker/
> > > src/main/java/org/apache/rocketmq/broker/processor/
> > > EndTransactionProcessor.java#L49 for broker
> > >
> > >
> > > And my question is what is the part to be implemented for this issue?
> Is
> > > there anything I missed?
> > >
> > >
> > >
> > > 
> > > 发件人: 李 德鑫 
> > > 发送时间: 2018年2月23日 9:35:17
> > > 收件人: dev@rocketmq.apache.org
> > > 主题: [GSOC|ROCKETMQ-123]Support Distributed Transactional Messaging
> > >
> > > Hi,
> > >
> > > I am working on this issue
> > > (https://issues.ap

Re: [GSOC][ROCKETMQ-380] Provide a modern and friendly console for RocketMQ

[yukon]

Yeah, it's important to include these feature in our console.

BTW, what's your idea about how to handle user features and operations
features?  Integrate these features in one console with two kinds of
role(user and admin), or provide two independent consoles?

Regards,
yukon

On Mon, Mar 19, 2018 at 4:23 PM, Ahmed Ifhaam 
wrote:

> hi yukon,
>
> I've been working on the requirements. When i listed the features available
> in cli admin tool but not in the console i found the following list. I
> would like some feedback on the list before i start next step.
> 1. brokerConfigurationUpdate
> 2. BrokerConsume Stats
> 3. CleanExpiredCQ
> 4. CleanUnusedTopic
> 5. WipeWritePermissions
> 6. updateOrderConf
> 7. UpdateKvConf
> 8. DeleteKVConf
> 9. CheckMsgSendRT
> 10. clusterRT
> 11. CloneGroupOffset
> 12. ResetOffsetByTimeStamp
>
> This is the list which i think i should implement. But i have seen in the
> system labels differ a bit from the *'adminTool'*. Also though i tried the
> tool i may have missed something. In that case i just want to confirm these
> are not already there in the current console and these are the only things
> that are not in the current console.
>
> Thank you
>
> On Sun, Mar 18, 2018 at 8:43 AM, yukon  wrote:
>
> > Hi,
> >
> > Yes, most of the user-related features already exist, but we also need an
> > operations console, more details please refer to our admin client:
> > http://rocketmq.apache.org/docs/cli-admin-tool/
> >
> > Regards
> >
> > On Sun, Mar 18, 2018 at 1:03 AM, Ahmed Ifhaam 
> > wrote:
> >
> > > hi yukon,
> > >
> > > I tried the commercial product. There is not much change in both except
> > the
> > > user interface, most of the features are already there, organizing and
> > look
> > > and feel of the commercial one is looking better. Before i draft the
> > design
> > > for my changes, I need to know whether the changes you expect are
> totally
> > > on UI Design ? Or a new feature on analytics kind of thing ?
> > >
> > > Thank you
> > >
> > > On Fri, Mar 16, 2018 at 7:47 AM, yukon  wrote:
> > >
> > > > Hi,
> > > >
> > > > This is a commercial version[1] of apache rocketmq and could be your
> > > > reference.
> > > >
> > > > After trying this console, hope you could draft the design ASAP and
> > then
> > > we
> > > > can discuss based on i.
> > > >
> > > >
> > > > Regards,
> > > > yukon
> > > >
> > > > [1]. https://www.alibabacloud.com/product/mq
> > > >
> > > > On Fri, Mar 16, 2018 at 2:41 AM, Ahmed Ifhaam <
> ahmedifha...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi yukon,
> > > > >
> > > > > I checked the console and after you asked I have re checked it as
> > > well. I
> > > > > used it with the CLI tool in parallel too.
> > > > > In the requirement specification there was a reference console
> which
> > I
> > > > > mentioned in my earlier mail that I couldn't get it to run. So I'm
> > not
> > > > > exactly clear with the requirements. It would be a great help if
> > > someone
> > > > > can point me to a place where i can find the requirements. As I
> have
> > to
> > > > > prepare the proposal (27th March) please kindly take a look at this
> > > ASAP.
> > > > >
> > > > > Thank you
> > > > >
> > > > > On Fri, Mar 9, 2018 at 9:05 PM, yukon  wrote:
> > > > >
> > > > > > Edit the subject!
> > > > > >
> > > > > > On Fri, Mar 9, 2018 at 10:47 PM, yukon  wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > ```
> > > > > > > The other thing is what are the expected features in the new
> > > console?
> > > > > > > ```
> > > > > > >
> > > > > > > Do you check out the features in the current console[1]?
> > > > > > >
> > > > > > > You may have ideas about the features after trying this console
> > and
> > > > the
> > > > > > > `admin` tool[2], then make a design and let's discuss based on
> > it.
> > > > > > >
> > > > > > > Regards,
> > > > > > > yukon
> > > > > > >
> > > > > > > [1]. https://github.com/apache/rocketmq-externals/tree/
> > > > > > > master/rocketmq-console
> > > > > > > [2].https://github.com/apache/rocketmq/blob/master/
> > > > > > > distribution/bin/mqadmin
> > > > > > >
> > > > > > > On Thu, Mar 8, 2018 at 7:26 PM, Ahmed Ifhaam <
> > > ahmedifha...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > >> HI,
> > > > > > >> Regarding this RocketMQ-380,
> > > > > > >> I have issues in running the referenced console when ever i
> try
> > to
> > > > > enter
> > > > > > >> my
> > > > > > >> personal details page is automatically redirected to home
> page.
> > > > > > >> Hence i'm not being able to activate the messaging service
> > which i
> > > > > > believe
> > > > > > >> should work.
> > > > > > >> https://mns.console.aliyun.com/?spm=5176.2020520130.0.0.4db6
> > > > > > >> 3db5cHTXtU#/list/cn-hangzhou
> > > > > > >> From this link when i click activate button it is redirecting
> to
> > > the
> > > > > > home
> > > > > > >> page. but according to the documentation it should take me to
> a
> > > form
> > > > > to
> > > > > > >> fill my per

Re: [GSOC][ROCKETMQ-380] Provide a modern and friendly console for RocketMQ

[Von Gosling]

Hi,

Nice, I would like to recommend using simple ACL according to Roles :-)

Best Regards,
Von Gosling

> 在 2018年3月19日，17:05，yukon  写道：
> 
> Yeah, it's important to include these feature in our console.
> 
> BTW, what's your idea about how to handle user features and operations
> features?  Integrate these features in one console with two kinds of
> role(user and admin), or provide two independent consoles?
> 
> Regards,
> yukon
> 
> On Mon, Mar 19, 2018 at 4:23 PM, Ahmed Ifhaam 
> wrote:
> 
>> hi yukon,
>> 
>> I've been working on the requirements. When i listed the features available
>> in cli admin tool but not in the console i found the following list. I
>> would like some feedback on the list before i start next step.
>> 1. brokerConfigurationUpdate
>> 2. BrokerConsume Stats
>> 3. CleanExpiredCQ
>> 4. CleanUnusedTopic
>> 5. WipeWritePermissions
>> 6. updateOrderConf
>> 7. UpdateKvConf
>> 8. DeleteKVConf
>> 9. CheckMsgSendRT
>> 10. clusterRT
>> 11. CloneGroupOffset
>> 12. ResetOffsetByTimeStamp
>> 
>> This is the list which i think i should implement. But i have seen in the
>> system labels differ a bit from the *'adminTool'*. Also though i tried the
>> tool i may have missed something. In that case i just want to confirm these
>> are not already there in the current console and these are the only things
>> that are not in the current console.
>> 
>> Thank you
>> 
>> On Sun, Mar 18, 2018 at 8:43 AM, yukon  wrote:
>> 
>>> Hi,
>>> 
>>> Yes, most of the user-related features already exist, but we also need an
>>> operations console, more details please refer to our admin client:
>>> http://rocketmq.apache.org/docs/cli-admin-tool/
>>> 
>>> Regards
>>> 
>>> On Sun, Mar 18, 2018 at 1:03 AM, Ahmed Ifhaam 
>>> wrote:
>>> 
 hi yukon,
 
 I tried the commercial product. There is not much change in both except
>>> the
 user interface, most of the features are already there, organizing and
>>> look
 and feel of the commercial one is looking better. Before i draft the
>>> design
 for my changes, I need to know whether the changes you expect are
>> totally
 on UI Design ? Or a new feature on analytics kind of thing ?
 
 Thank you
 
 On Fri, Mar 16, 2018 at 7:47 AM, yukon  wrote:
 
> Hi,
> 
> This is a commercial version[1] of apache rocketmq and could be your
> reference.
> 
> After trying this console, hope you could draft the design ASAP and
>>> then
 we
> can discuss based on i.
> 
> 
> Regards,
> yukon
> 
> [1]. https://www.alibabacloud.com/product/mq
> 
> On Fri, Mar 16, 2018 at 2:41 AM, Ahmed Ifhaam <
>> ahmedifha...@gmail.com>
> wrote:
> 
>> Hi yukon,
>> 
>> I checked the console and after you asked I have re checked it as
 well. I
>> used it with the CLI tool in parallel too.
>> In the requirement specification there was a reference console
>> which
>>> I
>> mentioned in my earlier mail that I couldn't get it to run. So I'm
>>> not
>> exactly clear with the requirements. It would be a great help if
 someone
>> can point me to a place where i can find the requirements. As I
>> have
>>> to
>> prepare the proposal (27th March) please kindly take a look at this
 ASAP.
>> 
>> Thank you
>> 
>> On Fri, Mar 9, 2018 at 9:05 PM, yukon  wrote:
>> 
>>> Edit the subject!
>>> 
>>> On Fri, Mar 9, 2018 at 10:47 PM, yukon  wrote:
>>> 
 Hi,
 
 ```
 The other thing is what are the expected features in the new
 console?
 ```
 
 Do you check out the features in the current console[1]?
 
 You may have ideas about the features after trying this console
>>> and
> the
 `admin` tool[2], then make a design and let's discuss based on
>>> it.
 
 Regards,
 yukon
 
 [1]. https://github.com/apache/rocketmq-externals/tree/
 master/rocketmq-console
 [2].https://github.com/apache/rocketmq/blob/master/
 distribution/bin/mqadmin
 
 On Thu, Mar 8, 2018 at 7:26 PM, Ahmed Ifhaam <
 ahmedifha...@gmail.com
>> 
 wrote:
 
> HI,
> Regarding this RocketMQ-380,
> I have issues in running the referenced console when ever i
>> try
>>> to
>> enter
> my
> personal details page is automatically redirected to home
>> page.
> Hence i'm not being able to activate the messaging service
>>> which i
>>> believe
> should work.
> https://mns.console.aliyun.com/?spm=5176.2020520130.0.0.4db6
> 3db5cHTXtU#/list/cn-hangzhou
> From this link when i click activate button it is redirecting
>> to
 the
>>> home
> page. but according to the documentation it should take me to
>> a
 form
>> to
> fill my personal details. I created an account and i can login
>>> to
 my

Re: [GSOC][ROCKETMQ-380] Provide a modern and friendly console for RocketMQ

[Ahmed Ifhaam]

hi Gosling,Yukon,

On my understanding even if we implement two different consoles we should
implement an authentication method because most of these commands may cause
considerable problems if used without proper understanding. And then we
have to implement the same already available features in the new console as
well. so i think its better to implement role based one in the same console
I had a doubt and i was waiting to clarify from you,Currently
Authentication is optional, so if we are to do role based one, the idea i
had was when we are changing to ops tab we can ask for authentication. Is
it fine or we change the console to request for login every time it
starts(Mandatory login) ?

Thank you.

On Mon, Mar 19, 2018 at 2:38 PM, Von Gosling  wrote:

> Hi,
>
> Nice, I would like to recommend using simple ACL according to Roles :-)
>
> Best Regards,
> Von Gosling
>
> > 在 2018年3月19日，17:05，yukon  写道：
> >
> > Yeah, it's important to include these feature in our console.
> >
> > BTW, what's your idea about how to handle user features and operations
> > features?  Integrate these features in one console with two kinds of
> > role(user and admin), or provide two independent consoles?
> >
> > Regards,
> > yukon
> >
> > On Mon, Mar 19, 2018 at 4:23 PM, Ahmed Ifhaam 
> > wrote:
> >
> >> hi yukon,
> >>
> >> I've been working on the requirements. When i listed the features
> available
> >> in cli admin tool but not in the console i found the following list. I
> >> would like some feedback on the list before i start next step.
> >> 1. brokerConfigurationUpdate
> >> 2. BrokerConsume Stats
> >> 3. CleanExpiredCQ
> >> 4. CleanUnusedTopic
> >> 5. WipeWritePermissions
> >> 6. updateOrderConf
> >> 7. UpdateKvConf
> >> 8. DeleteKVConf
> >> 9. CheckMsgSendRT
> >> 10. clusterRT
> >> 11. CloneGroupOffset
> >> 12. ResetOffsetByTimeStamp
> >>
> >> This is the list which i think i should implement. But i have seen in
> the
> >> system labels differ a bit from the *'adminTool'*. Also though i tried
> the
> >> tool i may have missed something. In that case i just want to confirm
> these
> >> are not already there in the current console and these are the only
> things
> >> that are not in the current console.
> >>
> >> Thank you
> >>
> >> On Sun, Mar 18, 2018 at 8:43 AM, yukon  wrote:
> >>
> >>> Hi,
> >>>
> >>> Yes, most of the user-related features already exist, but we also need
> an
> >>> operations console, more details please refer to our admin client:
> >>> http://rocketmq.apache.org/docs/cli-admin-tool/
> >>>
> >>> Regards
> >>>
> >>> On Sun, Mar 18, 2018 at 1:03 AM, Ahmed Ifhaam 
> >>> wrote:
> >>>
>  hi yukon,
> 
>  I tried the commercial product. There is not much change in both
> except
> >>> the
>  user interface, most of the features are already there, organizing and
> >>> look
>  and feel of the commercial one is looking better. Before i draft the
> >>> design
>  for my changes, I need to know whether the changes you expect are
> >> totally
>  on UI Design ? Or a new feature on analytics kind of thing ?
> 
>  Thank you
> 
>  On Fri, Mar 16, 2018 at 7:47 AM, yukon  wrote:
> 
> > Hi,
> >
> > This is a commercial version[1] of apache rocketmq and could be your
> > reference.
> >
> > After trying this console, hope you could draft the design ASAP and
> >>> then
>  we
> > can discuss based on i.
> >
> >
> > Regards,
> > yukon
> >
> > [1]. https://www.alibabacloud.com/product/mq
> >
> > On Fri, Mar 16, 2018 at 2:41 AM, Ahmed Ifhaam <
> >> ahmedifha...@gmail.com>
> > wrote:
> >
> >> Hi yukon,
> >>
> >> I checked the console and after you asked I have re checked it as
>  well. I
> >> used it with the CLI tool in parallel too.
> >> In the requirement specification there was a reference console
> >> which
> >>> I
> >> mentioned in my earlier mail that I couldn't get it to run. So I'm
> >>> not
> >> exactly clear with the requirements. It would be a great help if
>  someone
> >> can point me to a place where i can find the requirements. As I
> >> have
> >>> to
> >> prepare the proposal (27th March) please kindly take a look at this
>  ASAP.
> >>
> >> Thank you
> >>
> >> On Fri, Mar 9, 2018 at 9:05 PM, yukon  wrote:
> >>
> >>> Edit the subject!
> >>>
> >>> On Fri, Mar 9, 2018 at 10:47 PM, yukon  wrote:
> >>>
>  Hi,
> 
>  ```
>  The other thing is what are the expected features in the new
>  console?
>  ```
> 
>  Do you check out the features in the current console[1]?
> 
>  You may have ideas about the features after trying this console
> >>> and
> > the
>  `admin` tool[2], then make a design and let's discuss based on
> >>> it.
> 
>  Regards,
>  yukon
> 
>  [1]. https://github.com/apache/rocketmq-extern

Re: [GSoC][ROCKETMQ-372] Providing a REST Proxy to Support HTTP/2 Protocol

[Menuka Warushavithana]

Hi,
Thanks for the info. Are we going to use Linkerd [1] directly in
implementing the proxy server, or is it only to be used as a reference?

[1] https://linkerd.io/


Best Regards,
Menuka

On 19 March 2018 at 07:13, yukon https://mltrk.io/link/mailto%3Ayukon%40apache.org/QE9YmLinIw2A3pLINZj4>>
wrote:

> Hi, the current protocol is customized, please see:
>
> 
> https://github.com/apache/rock
> 
> etmq/tree/master/remoting/src/main/java/org/apache/rocketmq/
> remoting/protocol
>
> On Mon, Mar 19, 2018 at 2:06 AM, Menuka Warushavithana <
> menuka...@cse.mrt.ac.lk
> >
> wrote:
>
> > Hi Yukon,
> > It is mentioned in the JIRA issue [1] that, "So far, RocketMQ uses a
> > customized communication protocol between client and server which is
> > efficient but limited". However, I could not find the said method in the
> > documentation. It would be appreciated if you could help me understand
> the
> > current communication protocol, please.
> >
> >
> > [1]
> 
> https://issues.apache.org/jira
> 
> /browse/ROCKETMQ-372
> > <
> 
> https://mltrk.io/link/https%3A%2F%2Fissues.apache.org%2Fjir
> a%2Fbrowse%2FROCKETMQ-372/QItHTjI9X8newkTsyIw0>
> >
> > Best Regards,
> > Menuka
> >
> > On 17 March 2018 at 14:19, Menuka Warushavithana <
> menuka...@cse.mrt.ac.lk
> 
> >
> > wrote:
> >
> >> Hi Yukon,
> >> I will continue the discussion (which was started on JIRA) here. I went
> >> through all examples described in the docs [1] and I'm currently
> studying
> >> Linkerd [2] to get an idea of implementing the proxy server.
> >>
> >> In the meantime, I would appreciate your ideas on designing the REST
> APIs
> >> to produce/consume messages.
> >>
> >>
> >> [1]
> 
> https://rocketmq.apache.org/do
> 
> cs/quick-start/
> >> <
> 
> https://mltrk.io/link/https%3A%2F%2Frocketmq.apache.org%2Fd
> ocs%2Fquick-start%2F/lFINZX2DO0vBptcSPse6>
> >> [2] https://linkerd.io/
> 
> >> <
> 
> https://mltrk.io/link/https%3A%2F%2Flinkerd.io%2F/lFINZX2DO0vBptcSPse6>
> >>
> >> Thank You,
> >> --
> >> Menuka Warushavithana
> >> Final Year Undergraduate
> >> Department of Computer Science and Engineering
> >> University of Moratuwa, Sri Lanka.
> >> LinkedIn:
> 
> https://www.linkedin.com/in/me
> 
> nukawarushavithana
> >> <
> 
> https://mltrk.io/link/https%3A%2F%2Fwww.linkedin.com%2Fin%2
> Fmenukawarushavithana/lFINZX2DO0vBptcSPse6>
> >> GitHub:
> 
> https://www.github.com/menuka9
> 
> 4
> >> <
> 
> https://mltrk.io/link/https%3A%2F%2Fwww.github.com%2Fmenuka
> 94/lFINZX2DO0vBptcSPse6>
> >>
> >>
> >
> >
> > --
> > Menuka Warushavithana
> > LinkedIn:
> 
> https://www.linkedin.com/in/me
> 
> nukawarushavithana
> > GitHub:
> 
> https://www.github.com/menuka9
> 
> 4
> >
> >
>



-- 
Menuka Warushavithana
LinkedIn:

https://www 

Re: [GSOC][ROCKETMQ-127]Providing a rocketmq-proxy to support MQTT protocol

[Sudaraka Yasindu]

Hi Yukon and Von,
I found Vert.x MQTT server[1] provides a nice way of implementing MQTT
broker functionality. I just played around and created a simple mqtt broker
with it. The repo is on github[2]  and I have uploaded a short screencast
to the google drive[3]. I used MQTTLens[4] as the MQTT client here. Thank
you

[1] http://vertx.io/docs/vertx-mqtt-server/java/
[2] https://github.com/sudaraka94/mqtt-broker-test
[3] https://drive.google.com/open?id=1W4QOCRsONYr4Tl7RSDolqQHnNgRwJQUY
[4] https://chrome.google.com/webstore/detail/mqttlens/
hemojaaeigabkbcookmlgmdigohjobjm

Regards,
Sudaraka Jayathilaka
*Undergraduate*
Department of Computer Science and Engineering
University of Moratuwa


On Tue, Mar 20, 2018 at 12:08 AM, Sudaraka Yasindu <
sudarakayasi...@gmail.com> wrote:

> Hi Yukon and Von,
> I found Vert.x MQTT server[1] provides a nice way of implementing MQTT
> broker functionality. I just played around and created a simple mqtt broker
> with it. The repo is on github[2]  and I have attached a short screen cast
> with this email. I used MQTTLens[3] as the MQTT client here. Thank you
>
> [1] http://vertx.io/docs/vertx-mqtt-server/java/
> [2] https://github.com/sudaraka94/mqtt-broker-test
> [3] https://chrome.google.com/webstore/detail/mqttlens/
> hemojaaeigabkbcookmlgmdigohjobjm
>
> Regards,
> Sudaraka Jayathilaka
> *Undergraduate*
> Department of Computer Science and Engineering
> University of Moratuwa
>
>
> On Sat, Mar 17, 2018 at 2:27 PM, yukon  wrote:
>
>> Cool, looking forward to your design and reuse code is ok if the license
>> is compatible with ASF license. More details please refer to
>> https://www.apache.org/legal/resolved.html
>> 
>>
>> Sudaraka Yasindu 于2018年3月17日 周六下午3:53写道：
>>
>>> Hi Yukon and Von Gosling,
>>> I read the research paper you mentioned in the thread and got a brief
>>> idea about the proxy server and its functionalities
>>>
>>>
>>> I figured the proxy server implementation must have mainly two
>>> components. One component for handling all the functionalities regarding
>>> the ​MQTT protocol and the other component which is responsible for
>>> translating messages between RocketMQ message format and MQTT message
>>> format.
>>>
>>> *MQTT Broker*
>>>
>>> I found a lot of existing opensource MQTT Broker implementations. I
>>> found Eclipse Mosquitto easy to work with. In the project I will be able to
>>> use one of these brokers as references and implement the component myself.
>>> Will I be able to reuse some of the code from those broker implementations
>>> ? (If the code licensing permits).
>>>
>>> *Protocol Conversion Component*
>>>
>>> Message format used in MQTT protocol and RocketMQ are slightly
>>> different. This component will convert messages in MQTT format to RocketMQ
>>> component and in the other way too.
>>>
>>> This is my current idea regarding the project and I'm reading more about
>>> Linkerd. Is there anything to be corrected?
>>>
>>> Regards,
>>> Sudaraka Jayathilaka
>>> *Undergraduate*
>>> Department of Computer Science and Engineering
>>> University of Moratuwa
>>>
>>>
>>> On Sat, Mar 17, 2018 at 8:43 AM, Sudaraka Yasindu <
>>> sudarakayasi...@gmail.com> wrote:
>>>
 Hi Yukon,
 I already found the research paper and I'm studying it. Thank you a lot
 for the direction. I will soon come up with a brief design for the project.

 Regards,
 Sudaraka Jayathilaka
 *Undergraduate*
 Department of Computer Science and Engineering
 University of Moratuwa


 On Sat, Mar 17, 2018 at 8:33 AM, yukon  wrote:

> As we are implementing a proxy server, so may Linkerd[1] could give us
> some
> hints.
>
> [1]. https://linkerd.io/
>
> Regards,
> yukon
>
> On Fri, Mar 16, 2018 at 9:38 PM, Sudaraka Yasindu <
> sudarakayasi...@gmail.com
> > wrote:
>
> > Thank you for the clarification Yukon. I am looking into it.
> >
> > Regards,
> > Sudaraka Jayathilaka
> > *Undergraduate*
> > Department of Computer Science and Engineering
> > University of Moratuwa
> >
> >
> > On Fri, Mar 16, 2018 at 6:42 PM, yukon  wrote:
> >
> > > Hi,
> > >
> > > A paper implemented a MQTT push server based on RocketMQ, maybe it
> helps.
> > >
> > > And we don't want to depend on the third-party server, just
> develop a
> > > proxy server that supports MQTT protocol and talk to our rocketmq
> > cluster.
> > >
> > > Regards,
> > > yukon
> > >
> > > 1. Yue, Ma, et al. "A MQTT Protocol Message Push Server Based on
> > > RocketMQ." Intelligent Computation Technology and Automation
> (ICICTA),
> > 2017
> > > 10th International Conference on. IEEE, 2017.
> > >
> > >
> > >
> > > On Fri, Mar 16, 2018 at 8:18 PM, Sudaraka Yasindu <
> > > sudarakayasi...@gmail.com> wrote:
> > >
> > >> ​Hi Yukon & Vongosling,
> > >>

[GitHub] vongosling commented on issue #237: Spinlock bad performance with high race conditions.

[GitBox]

vongosling commented on issue #237: Spinlock bad performance with high race 
conditions.
URL: https://github.com/apache/rocketmq/issues/237#issuecomment-374441988
 
 
   @pifuant Could you comment on our issue question at first?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [GSOC][ROCKETMQ-380] Provide a modern and friendly console for RocketMQ

[yukon]

Hi,

I think it's acceptable, and it's time to draft the proposal, right?

Regards

On Mon, Mar 19, 2018 at 6:23 PM, Ahmed Ifhaam 
wrote:

> hi Gosling,Yukon,
>
> On my understanding even if we implement two different consoles we should
> implement an authentication method because most of these commands may cause
> considerable problems if used without proper understanding. And then we
> have to implement the same already available features in the new console as
> well. so i think its better to implement role based one in the same console
> I had a doubt and i was waiting to clarify from you,Currently
> Authentication is optional, so if we are to do role based one, the idea i
> had was when we are changing to ops tab we can ask for authentication. Is
> it fine or we change the console to request for login every time it
> starts(Mandatory login) ?
>
> Thank you.
>
> On Mon, Mar 19, 2018 at 2:38 PM, Von Gosling 
> wrote:
>
> > Hi,
> >
> > Nice, I would like to recommend using simple ACL according to Roles :-)
> >
> > Best Regards,
> > Von Gosling
> >
> > > 在 2018年3月19日，17:05，yukon  写道：
> > >
> > > Yeah, it's important to include these feature in our console.
> > >
> > > BTW, what's your idea about how to handle user features and operations
> > > features?  Integrate these features in one console with two kinds of
> > > role(user and admin), or provide two independent consoles?
> > >
> > > Regards,
> > > yukon
> > >
> > > On Mon, Mar 19, 2018 at 4:23 PM, Ahmed Ifhaam 
> > > wrote:
> > >
> > >> hi yukon,
> > >>
> > >> I've been working on the requirements. When i listed the features
> > available
> > >> in cli admin tool but not in the console i found the following list. I
> > >> would like some feedback on the list before i start next step.
> > >> 1. brokerConfigurationUpdate
> > >> 2. BrokerConsume Stats
> > >> 3. CleanExpiredCQ
> > >> 4. CleanUnusedTopic
> > >> 5. WipeWritePermissions
> > >> 6. updateOrderConf
> > >> 7. UpdateKvConf
> > >> 8. DeleteKVConf
> > >> 9. CheckMsgSendRT
> > >> 10. clusterRT
> > >> 11. CloneGroupOffset
> > >> 12. ResetOffsetByTimeStamp
> > >>
> > >> This is the list which i think i should implement. But i have seen in
> > the
> > >> system labels differ a bit from the *'adminTool'*. Also though i tried
> > the
> > >> tool i may have missed something. In that case i just want to confirm
> > these
> > >> are not already there in the current console and these are the only
> > things
> > >> that are not in the current console.
> > >>
> > >> Thank you
> > >>
> > >> On Sun, Mar 18, 2018 at 8:43 AM, yukon  wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> Yes, most of the user-related features already exist, but we also
> need
> > an
> > >>> operations console, more details please refer to our admin client:
> > >>> http://rocketmq.apache.org/docs/cli-admin-tool/
> > >>>
> > >>> Regards
> > >>>
> > >>> On Sun, Mar 18, 2018 at 1:03 AM, Ahmed Ifhaam <
> ahmedifha...@gmail.com>
> > >>> wrote:
> > >>>
> >  hi yukon,
> > 
> >  I tried the commercial product. There is not much change in both
> > except
> > >>> the
> >  user interface, most of the features are already there, organizing
> and
> > >>> look
> >  and feel of the commercial one is looking better. Before i draft the
> > >>> design
> >  for my changes, I need to know whether the changes you expect are
> > >> totally
> >  on UI Design ? Or a new feature on analytics kind of thing ?
> > 
> >  Thank you
> > 
> >  On Fri, Mar 16, 2018 at 7:47 AM, yukon  wrote:
> > 
> > > Hi,
> > >
> > > This is a commercial version[1] of apache rocketmq and could be
> your
> > > reference.
> > >
> > > After trying this console, hope you could draft the design ASAP and
> > >>> then
> >  we
> > > can discuss based on i.
> > >
> > >
> > > Regards,
> > > yukon
> > >
> > > [1]. https://www.alibabacloud.com/product/mq
> > >
> > > On Fri, Mar 16, 2018 at 2:41 AM, Ahmed Ifhaam <
> > >> ahmedifha...@gmail.com>
> > > wrote:
> > >
> > >> Hi yukon,
> > >>
> > >> I checked the console and after you asked I have re checked it as
> >  well. I
> > >> used it with the CLI tool in parallel too.
> > >> In the requirement specification there was a reference console
> > >> which
> > >>> I
> > >> mentioned in my earlier mail that I couldn't get it to run. So I'm
> > >>> not
> > >> exactly clear with the requirements. It would be a great help if
> >  someone
> > >> can point me to a place where i can find the requirements. As I
> > >> have
> > >>> to
> > >> prepare the proposal (27th March) please kindly take a look at
> this
> >  ASAP.
> > >>
> > >> Thank you
> > >>
> > >> On Fri, Mar 9, 2018 at 9:05 PM, yukon  wrote:
> > >>
> > >>> Edit the subject!
> > >>>
> > >>> On Fri, Mar 9, 2018 at 10:47 PM, yukon  wrote:
> > >>>
> >  Hi,
> > 
> >  ```
> >  The oth

Re: [GSOC][ROCKETMQ-127]Providing a rocketmq-proxy to support MQTT protocol

[yukon]

Great, you should ensure that the vert.x mqtt server has enough secondary
development capabilities if you want to reuse it. After all, we need the
server react with RocketMQ cluster.

Regards

On Tue, Mar 20, 2018 at 2:45 AM, Sudaraka Yasindu  wrote:

> Hi Yukon and Von,
> I found Vert.x MQTT server[1] provides a nice way of implementing MQTT
> broker functionality. I just played around and created a simple mqtt broker
> with it. The repo is on github[2]  and I have uploaded a short screencast
> to the google drive[3]. I used MQTTLens[4] as the MQTT client here. Thank
> you
>
> [1] http://vertx.io/docs/vertx-mqtt-server/java/
> [2] https://github.com/sudaraka94/mqtt-broker-test
> [3] https://drive.google.com/open?id=1W4QOCRsONYr4Tl7RSDolqQHnNgRwJQUY
> [4] https://chrome.google.com/webstore/detail/mqttlens/hemoj
> aaeigabkbcookmlgmdigohjobjm
>
> Regards,
> Sudaraka Jayathilaka
> *Undergraduate*
> Department of Computer Science and Engineering
> University of Moratuwa
>
>
> On Tue, Mar 20, 2018 at 12:08 AM, Sudaraka Yasindu <
> sudarakayasi...@gmail.com> wrote:
>
>> Hi Yukon and Von,
>> I found Vert.x MQTT server[1] provides a nice way of implementing MQTT
>> broker functionality. I just played around and created a simple mqtt broker
>> with it. The repo is on github[2]  and I have attached a short screen cast
>> with this email. I used MQTTLens[3] as the MQTT client here. Thank you
>>
>> [1] http://vertx.io/docs/vertx-mqtt-server/java/
>> [2] https://github.com/sudaraka94/mqtt-broker-test
>> [3] https://chrome.google.com/webstore/detail/mqttlens/hemoj
>> aaeigabkbcookmlgmdigohjobjm
>>
>> Regards,
>> Sudaraka Jayathilaka
>> *Undergraduate*
>> Department of Computer Science and Engineering
>> University of Moratuwa
>>
>>
>> On Sat, Mar 17, 2018 at 2:27 PM, yukon  wrote:
>>
>>> Cool, looking forward to your design and reuse code is ok if the license
>>> is compatible with ASF license. More details please refer to
>>> https://www.apache.org/legal/resolved.html
>>> 
>>>
>>> Sudaraka Yasindu 于2018年3月17日 周六下午3:53写道：
>>>
 Hi Yukon and Von Gosling,
 I read the research paper you mentioned in the thread and got a brief
 idea about the proxy server and its functionalities


 I figured the proxy server implementation must have mainly two
 components. One component for handling all the functionalities regarding
 the ​MQTT protocol and the other component which is responsible for
 translating messages between RocketMQ message format and MQTT message
 format.

 *MQTT Broker*

 I found a lot of existing opensource MQTT Broker implementations. I
 found Eclipse Mosquitto easy to work with. In the project I will be able to
 use one of these brokers as references and implement the component myself.
 Will I be able to reuse some of the code from those broker implementations
 ? (If the code licensing permits).

 *Protocol Conversion Component*

 Message format used in MQTT protocol and RocketMQ are slightly
 different. This component will convert messages in MQTT format to RocketMQ
 component and in the other way too.

 This is my current idea regarding the project and I'm reading more
 about Linkerd. Is there anything to be corrected?

 Regards,
 Sudaraka Jayathilaka
 *Undergraduate*
 Department of Computer Science and Engineering
 University of Moratuwa


 On Sat, Mar 17, 2018 at 8:43 AM, Sudaraka Yasindu <
 sudarakayasi...@gmail.com> wrote:

> Hi Yukon,
> I already found the research paper and I'm studying it. Thank you a
> lot for the direction. I will soon come up with a brief design for the
> project.
>
> Regards,
> Sudaraka Jayathilaka
> *Undergraduate*
> Department of Computer Science and Engineering
> University of Moratuwa
>
>
> On Sat, Mar 17, 2018 at 8:33 AM, yukon  wrote:
>
>> As we are implementing a proxy server, so may Linkerd[1] could give
>> us some
>> hints.
>>
>> [1]. https://linkerd.io/
>>
>> Regards,
>> yukon
>>
>> On Fri, Mar 16, 2018 at 9:38 PM, Sudaraka Yasindu <
>> sudarakayasi...@gmail.com
>> > wrote:
>>
>> > Thank you for the clarification Yukon. I am looking into it.
>> >
>> > Regards,
>> > Sudaraka Jayathilaka
>> > *Undergraduate*
>> > Department of Computer Science and Engineering
>> > University of Moratuwa
>> >
>> >
>> > On Fri, Mar 16, 2018 at 6:42 PM, yukon  wrote:
>> >
>> > > Hi,
>> > >
>> > > A paper implemented a MQTT push server based on RocketMQ, maybe
>> it helps.
>> > >
>> > > And we don't want to depend on the third-party server, just
>> develop a
>> > > proxy server that supports MQTT protocol and talk to our rocketmq
>> > cluster.
>> > >
>> > > Regards,
>> > > yukon
>> > >
>> >

Re: [GSoC][ROCKETMQ-372] Providing a REST Proxy to Support HTTP/2 Protocol

[yukon]

Hi,

Some concepts in Linkerd are very valuable and can be used as a reference.

But, It's ok if you want to use Linkerd directly for some necessary reasons.

Regards

On Mon, Mar 19, 2018 at 10:59 PM, Menuka Warushavithana <
menuka...@cse.mrt.ac.lk> wrote:

> Hi,
> Thanks for the info. Are we going to use Linkerd [1] directly in
> implementing the proxy server, or is it only to be used as a reference?
>
> [1] https://linkerd.io/
> 
>
> Best Regards,
> Menuka
>
> On 19 March 2018 at 07:13, yukon  >
> wrote:
>
> > Hi, the current protocol is customized, please see:
> >
> >  2Frocketmq%2Ftree%2Fmaster%2Fremoting%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%
> 2Frocketmq%2Fremoting%2Fprotocol/QE9YmLinIw2A3pLINZj4>
> > https://github.com/apache/rock
> >  2Frock/QE9YmLinIw2A3pLINZj4>
> > etmq/tree/master/remoting/src/main/java/org/apache/rocketmq/
> > remoting/protocol
> >
> > On Mon, Mar 19, 2018 at 2:06 AM, Menuka Warushavithana <
> > menuka...@cse.mrt.ac.lk
> >  QE9YmLinIw2A3pLINZj4>>
> > wrote:
> >
> > > Hi Yukon,
> > > It is mentioned in the JIRA issue [1] that, "So far, RocketMQ uses a
> > > customized communication protocol between client and server which is
> > > efficient but limited". However, I could not find the said method in
> the
> > > documentation. It would be appreciated if you could help me understand
> > the
> > > current communication protocol, please.
> > >
> > >
> > > [1]
> >  2Fjira%2Fbrowse%2FROCKETMQ-372/QE9YmLinIw2A3pLINZj4>
> > https://issues.apache.org/jira
> >  2Fjira/QE9YmLinIw2A3pLINZj4>
> > /browse/ROCKETMQ-372
> > > <
> >  2Fjira%2Fbrowse%2FROCKETMQ-372/QItHTjI9X8newkTsyIw0>
> > https://mltrk.io/link/https%3A%2F%2Fissues.apache.org%2Fjir
> > a%2Fbrowse%2FROCKETMQ-372/QItHTjI9X8newkTsyIw0>
> > >
> > > Best Regards,
> > > Menuka
> > >
> > > On 17 March 2018 at 14:19, Menuka Warushavithana <
> > menuka...@cse.mrt.ac.lk
> >  QE9YmLinIw2A3pLINZj4>
> > >
> > > wrote:
> > >
> > >> Hi Yukon,
> > >> I will continue the discussion (which was started on JIRA) here. I
> went
> > >> through all examples described in the docs [1] and I'm currently
> > studying
> > >> Linkerd [2] to get an idea of implementing the proxy server.
> > >>
> > >> In the meantime, I would appreciate your ideas on designing the REST
> > APIs
> > >> to produce/consume messages.
> > >>
> > >>
> > >> [1]
> >  2Fdocs%2Fquick-start%2F/QE9YmLinIw2A3pLINZj4>
> > https://rocketmq.apache.org/do
> >  2Fdo/QE9YmLinIw2A3pLINZj4>
> > cs/quick-start/
> > >> <
> >  2Fdocs%2Fquick-start%2F/lFINZX2DO0vBptcSPse6>
> > https://mltrk.io/link/https%3A%2F%2Frocketmq.apache.org%2Fd
> > ocs%2Fquick-start%2F/lFINZX2DO0vBptcSPse6>
> > >> [2] https://linkerd.io/
> > 
> > >> <
> > 
> > https://mltrk.io/link/https%3A%2F%2Flinkerd.io%2F/lFINZX2DO0vBptcSPse6>
> > >>
> > >> Thank You,
> > >> --
> > >> Menuka Warushavithana
> > >> Final Year Undergraduate
> > >> Department of Computer Science and Engineering
> > >> University of Moratuwa, Sri Lanka.
> > >> LinkedIn:
> >  2Fmenukawarushavithana/QE9YmLinIw2A3pLINZj4>
> > https://www.linkedin.com/in/me
> >  2Fme/QE9YmLinIw2A3pLINZj4>
> > nukawarushavithana
> > >> <
> >  2Fmenukawarushavithana/lFINZX2DO0vBptcSPse6>
> > https://mltrk.io/link/https%3A%2F%2Fwww.linkedin.com%2Fin%2
> > Fmenukawarushavithana/lFINZX2DO0vBptcSPse6>
> > >> GitHub:
> >  QE9YmLinIw2A3pLINZj4>
> > https://www.github.com/menuka9
> >  2Fmenuka9/QE9YmLinIw2A3pLINZj4>
> > 4
> > >> <
> >  lFINZX2DO0vBptcSPse6>
> > https://mltrk.io/link/https%3A%2F%2Fwww.github.com%2Fmenuka
> > 94/lFINZX2DO0vBptcSPse6>
> > >>
> > >>
> > >
> > >
> > > --
> > > Menuka Warushavithana
> > > LinkedIn:
> >  2Fmenukawarushavithana/QE9YmLinIw2A3pLINZj4>
> > https://www.linkedin.com/in/me
> > 

Re: [GSOC|ROCKETMQ-122] Support Global Ordered Messaging

[yukon]

Hi,

Sorry for the late reply.

As for:

```
I'm looking at the BrokerController and MessageStore implementation and
hooks to understand where the merge logic will best fit.
```

how is it going?

Regards

On Sat, Mar 17, 2018 at 11:30 AM, sowmya s  wrote:

> Thank you yukon,
>
> I'm done with my coursework for this semester and have more time now to
> improve my proposal.
> I'm looking at the BrokerController and MessageStore implementation and
> hooks to understand where the merge logic will best fit. So far I've looked
> at the codebase from a Producer and Consumer perspective and looked at the
> DefaultMQProducerImpl and  DefaultMQPushConsumerImpl for understanding the
> link between how Producers send and Consumers receive messages.
>
> thanks,
> Sowmya
>
> On Fri, Mar 16, 2018 at 8:07 PM, yukon  wrote:
>
> > Cool, let's focus on it and see whether is there anything can be
> polished.
> >
> > Regards
> >
> > On Fri, Mar 16, 2018 at 11:54 PM, sowmya s  wrote:
> >
> > > Hey yukon,
> > > I submitted my draft on the summer of code homepage a couple of days
> ago,
> > > also attaching the link here for reference,
> > >
> > > https://docs.google.com/file/d/1nXktUO_TF9-rSHSnGj5z5QZoHzMhosxm/edit?
> > > usp=docslist_api&filetype=msword
> > >
> > > Thanks,
> > > Sowmya
> > >
> > > On Thu, Mar 15, 2018 at 2:08 AM yukon  wrote:
> > >
> > > > Hi,
> > > >
> > > > Of course, we can work together to finetune your design draft.
> > > >
> > > > Regards,
> > > > yukon
> > > >
> > > > On Thu, Mar 15, 2018 at 5:33 AM, sowmya s 
> > wrote:
> > > >
> > > > > Hello, yukon and Von,
> > > > >
> > > > > I've shared my GSOC - 18 draft of the project. I'm looking forward
> to
> > > > > working with all of you to finetune the proposal. I will be
> > allocating
> > > 20
> > > > > hours per week from now to the proposal acceptance phase to address
> > > > > questions and dive deep into any suggestions that you provide.
> > > > > I am really looking forward to work on this project.
> > > > >
> > > > > thanks,
> > > > > Sowmya
> > > > >
> > > > > On Tue, Mar 13, 2018 at 11:47 PM, sowmya s 
> > > wrote:
> > > > >
> > > > > > Hello yukon,
> > > > > >
> > > > > > Thank you for the inputs. I was able to look at the ~/store and
> > kind
> > > of
> > > > > > understand the storage structure. I also looked at the
> > > > > > DefaultMQProducerImpl and DefaultMQPullConsumerImpl, used in the
> > > > > examples.
> > > > > > Now I understand why you proposed a merge sort like approach for
> > > > > > performing global ordering. Since the proposals are open, I am
> > > > finalizing
> > > > > > my draft and will have it up for review very soon.
> > > > > >
> > > > > > thanks,
> > > > > > Sowmya
> > > > > >
> > > > > > On Fri, Mar 9, 2018 at 7:03 AM, yukon  wrote:
> > > > > >
> > > > > >> Hi Sowmya,
> > > > > >>
> > > > > >> ```
> > > > > >> Also, it would be great if you can at a high level, help me
> > > understand
> > > > > >> how the messages in the message queues are stored before the
> > > consumer
> > > > > reads
> > > > > >> them.
> > > > > >> ```
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> As shown in this figure, messages are sent to brokers by
> producer
> > > and
> > > > > >> stored in commit log[1], then messages are dispatched to
> > > ConsumeQueue
> > > > by
> > > > > >> topic, the consumer pulls messages from the queue.
> > > > > >>
> > > > > >> I recommend you run a broker and send/consume some messages,
> then
> > > > check
> > > > > >> out the ~/store directory for details.
> > > > > >>
> > > > > >> Regards,
> > > > > >> yukon
> > > > > >>
> > > > > >> On Thu, Mar 8, 2018 at 12:09 PM, sowmya s  >
> > > > wrote:
> > > > > >>
> > > > > >>> Hello yukon,
> > > > > >>>
> > > > > >>> Currently FIFO can be achieved with a producer sending to one
> > > message
> > > > > >>> queue, and when global ordering is required, multiple producers
> > > have
> > > > to
> > > > > >>> send to a single topic queue.
> > > > > >>>
> > > > > >>> We want to allow multiple producers to send messages on a topic
> > to
> > > > > >>> multiple message queues and still provide ordering guarantees
> to
> > > the
> > > > > >>> consumer, so that all consumers see the same order of data and
> > also
> > > > the
> > > > > >>> data is delivered in an ordered fashion.
> > > > > >>>
> > > > > >>> 1) Your idea of using a merge sort with the assumption that the
> > > first
> > > > > >>> arriving message is treated as the first message to be
> delivered,
> > > > > however,
> > > > > >>> I want to propose an approach where when the producer sends a
> > > message
> > > > > to a
> > > > > >>> message queue, it must be done in a synchronous fashion and the
> > > > > response
> > > > > >>> will be that the message is accepted, which means that the
> > message
> > > > > follows
> > > > > >>> the convention that all messages delivered prior by that
> producer
> > > > have
> > > > > been
> > > > > >>> stored across groups and if not the producer will need to
> resend
> > 

[GitHub] fuyou001 opened a new issue #242: new consumer may consume all message

[GitBox]

fuyou001 opened a new issue #242: new consumer may consume all message
URL: https://github.com/apache/rocketmq/issues/242
 
 
   @The issue tracker is **ONLY** used for bug report and feature request. 
   
   Any question or RocketMQ proposal please use our [mailing 
lists](http://rocketmq.apache.org/about/contact/).
   
   
   **FEATURE REQUEST**
   1. Please describe the feature you are requesting.
   
 assume one MQ Broker cluster,the broker commitLog min offset is zero , a 
new consumer start ,
   the consumer will starting consume  queue's offset zero messages，it's a 
problem。
   
   2. Provide any additional detail on your proposed use case for this feature.
   
   3. Indicate the importance of this issue to you (blocker, must-have, 
should-have, nice-to-have). Are you currently using any workarounds to address 
this issue?
   
   * must-have
   
   4. If there are some sub-tasks using -[] for each subtask and create a 
corresponding issue to map to the sub task:
* 
org.apache.rocketmq.broker.processor.ConsumerManageProcessor#queryConsumerOffset
 method   refactor


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] fuyou001 closed pull request #225: [ROCKETMQ-361] Heartbeat handler use independently thread pool

[GitBox]

fuyou001 closed pull request #225: [ROCKETMQ-361]  Heartbeat handler use  
independently thread pool
URL: https://github.com/apache/rocketmq/pull/225
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/broker/src/main/java/org/apache/rocketmq/broker/client/net/Broker2Client.java 
b/broker/src/main/java/org/apache/rocketmq/broker/client/net/Broker2Client.java
index 65b444e6e..f0f465c49 100644
--- 
a/broker/src/main/java/org/apache/rocketmq/broker/client/net/Broker2Client.java
+++ 
b/broker/src/main/java/org/apache/rocketmq/broker/client/net/Broker2Client.java
@@ -108,7 +108,7 @@ public void notifyConsumerIdsChanged(
 
RemotingCommand.createRequestCommand(RequestCode.NOTIFY_CONSUMER_IDS_CHANGED, 
requestHeader);
 
 try {
-this.brokerController.getRemotingServer().invokeOneway(channel, 
request, 10);
+this.brokerController.getRemotingServer().invokeOneway(channel, 
request, 2);
 } catch (Exception e) {
 log.error("notifyConsumerIdsChanged exception, " + consumerGroup, 
e.getMessage());
 }
diff --git 
a/remoting/src/main/java/org/apache/rocketmq/remoting/netty/NettyServerConfig.java
 
b/remoting/src/main/java/org/apache/rocketmq/remoting/netty/NettyServerConfig.java
index a5e2a232d..9d3332ee6 100644
--- 
a/remoting/src/main/java/org/apache/rocketmq/remoting/netty/NettyServerConfig.java
+++ 
b/remoting/src/main/java/org/apache/rocketmq/remoting/netty/NettyServerConfig.java
@@ -21,8 +21,8 @@
 private int serverWorkerThreads = 8;
 private int serverCallbackExecutorThreads = 0;
 private int serverSelectorThreads = 3;
-private int serverOnewaySemaphoreValue = 256;
-private int serverAsyncSemaphoreValue = 64;
+private int serverOnewaySemaphoreValue = 8096;
+private int serverAsyncSemaphoreValue = 1024;
 private int serverChannelMaxIdleTimeSeconds = 120;
 
 private int serverSocketSndBufSize = NettySystemConfig.socketSndbufSize;


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] pifuant commented on issue #237: Spinlock bad performance with high race conditions.

[GitBox]

pifuant commented on issue #237: Spinlock bad performance with high race 
conditions.
URL: https://github.com/apache/rocketmq/issues/237#issuecomment-374489033
 
 
   @vongosling what do you mean?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services