duhenglucky closed issue #3579:
URL: https://github.com/apache/rocketmq/issues/3579
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
ShannonDing commented on issue #3579:
URL: https://github.com/apache/rocketmq/issues/3579#issuecomment-1015147171
it's better to add a new method like ”getClientFactory“ and make the
current "getmQClientFactory" deprecated.
--
This is an automated message from the Apache Git Service.
HuismanKwl closed issue #3770:
URL: https://github.com/apache/rocketmq/issues/3770
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
hzh0425 commented on issue #3747:
URL: https://github.com/apache/rocketmq/issues/3747#issuecomment-1015129513
例如对于 raft 的 leader transfer
oldLeader 必须等待 newLeader 追上自己, 才能实现 leader 的切换, 否则的日志会出现丢失的情况
例如:
oldLeader: 1 2 3 4 5 6
newLeader: 1 2 3 4
如果直接实现 NewLeader 切换, 那么 5 6
ShannonDing merged pull request #108:
URL: https://github.com/apache/rocketmq-site/pull/108
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
309791679 commented on issue #771:
URL:
https://github.com/apache/rocketmq-client-go/issues/771#issuecomment-1015101310
The consumption information is not in milliseconds. The test needs to wait
for the second pull to reply, resulting in delayed consumption success
odbozhou opened a new pull request #108:
URL: https://github.com/apache/rocketmq-site/pull/108
Please do not create a Pull Request without creating an issue first.
## What is the purpose of the change
X
## Brief changelog
XX
## Verifying this change
Hello RocketMQ Community,
This is the vote for the 1.0.0-preview release of Apache RocketMQ-Streams.
The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-streams/1.0.0-preview-rc2/
The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1074
+1
On Tue, Jan 18, 2022 at 11:45 AM Ze Ni wrote:
> +1
>
> ShannonDing 于2022年1月18日周二 11:40写道:
>
> > +1
> >
> > 在 2022-01-18 11:13:33,"vongosling" 写道:
> > >+1
> > >
> > >周波 于2022年1月18日周二 10:54写道:
> > >
> > >> +1
> > >>
> > >> jinrongtong 于2022年1月18日周二 10:28写道:
> > >>
> > >> > Hi, RocketMQ
+1
ShannonDing 于2022年1月18日周二 11:40写道:
> +1
>
> 在 2022-01-18 11:13:33,"vongosling" 写道:
> >+1
> >
> >周波 于2022年1月18日周二 10:54写道:
> >
> >> +1
> >>
> >> jinrongtong 于2022年1月18日周二 10:28写道:
> >>
> >> > Hi, RocketMQ Community:
> >> >
> >> >
> >> > As discussed in the previous email, we launched a new
+1
在 2022-01-18 11:13:33,"vongosling" 写道:
>+1
>
>周波 于2022年1月18日周二 10:54写道:
>
>> +1
>>
>> jinrongtong 于2022年1月18日周二 10:28写道:
>>
>> > Hi, RocketMQ Community:
>> >
>> >
>> > As discussed in the previous email, we launched a new RIP to optimize
>> > RocketMQ nameserver. Now the shepherds
duhenglucky closed pull request #1667:
URL: https://github.com/apache/rocketmq/pull/1667
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
+1
周波 于2022年1月18日周二 10:54写道:
> +1
>
> jinrongtong 于2022年1月18日周二 10:28写道:
>
> > Hi, RocketMQ Community:
> >
> >
> > As discussed in the previous email, we launched a new RIP to optimize
> > RocketMQ nameserver. Now the shepherds @duhenglucky and @ShannonDing are
> > willing to support the RIP,
ifplusor commented on issue #293:
URL:
https://github.com/apache/rocketmq-client-cpp/issues/293#issuecomment-1015028659
@ShannonDing
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
+1
jinrongtong 于2022年1月18日周二 10:18写道:
> Hi, RocketMQ Community:
>
> Currently, a RocketMQ process has only one broker. However, the slave
> costs fewer resources than the master. So I want to provide a new
> BrokerContainer mode, in which multiple brokers can be added or removed to
> a
+1
jinrongtong 于2022年1月18日周二 10:28写道:
> Hi, RocketMQ Community:
>
>
> As discussed in the previous email, we launched a new RIP to optimize
> RocketMQ nameserver. Now the shepherds @duhenglucky and @ShannonDing are
> willing to support the RIP, so I think it is time to start an email thread
>
gaoyf edited a comment on issue #293:
URL:
https://github.com/apache/rocketmq-client-cpp/issues/293#issuecomment-1015021342
> > 我也是,日志也一样,@YellowOldOdd @ifplusor @ShannonDing
>
> 你是什么消费模式?
gaoyf commented on issue #293:
URL:
https://github.com/apache/rocketmq-client-cpp/issues/293#issuecomment-1015021342
> > 我也是,日志也一样,@YellowOldOdd @ifplusor @ShannonDing
>
> 你是什么消费模式?
就是PushConsumer,跟@YellowOldOdd的一模一样,我看master代码已经修改了
+1
jinrongtong 于2022年1月18日周二 10:28写道:
> Hi, RocketMQ Community:
>
>
> As discussed in the previous email, we launched a new RIP to optimize
> RocketMQ nameserver. Now the shepherds @duhenglucky and @ShannonDing are
> willing to support the RIP, so I think it is time to start an email thread
>
Hi, RocketMQ Community:
As discussed in the previous email, we launched a new RIP to optimize RocketMQ
nameserver. Now the shepherds @duhenglucky and @ShannonDing are willing to
support the RIP, so I think it is time to start an email thread to enter the
voting process.
The vote will be open
Hi, RocketMQ Community:
Currently, a RocketMQ process has only one broker. However, the slave costs
fewer resources than the master. So I want to provide a new BrokerContainer
mode, in which multiple brokers can be added or removed to a BrokerContainer
process and reuse some resources such as
duhenglucky closed issue #3763:
URL: https://github.com/apache/rocketmq/issues/3763
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
duhenglucky commented on issue #3763:
URL: https://github.com/apache/rocketmq/issues/3763#issuecomment-1014997977
@ztyandjw 现在社区正在讨论API
的优化:https://lists.apache.org/thread/460ttogv9645pkdlnb5q7x8nktdny15r
,在社区达成一致前应该不会删除这个API,如果删除的话肯定会给出推荐:)
--
This is an automated message from the
zhangyulu opened a new issue #293:
URL: https://github.com/apache/rocketmq-client-cpp/issues/293
1. Please describe the issue you observed:
- What did you do (The steps to reproduce)?
let consumer run
- What did you expect to see?
keep consuming messages
- What
ifplusor commented on issue #293:
URL:
https://github.com/apache/rocketmq-client-cpp/issues/293#issuecomment-1014899306
> 我也是,日志也一样,@YellowOldOdd @ifplusor @ShannonDing
你是什么消费模式?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
ifplusor commented on issue #293:
URL:
https://github.com/apache/rocketmq-client-cpp/issues/293#issuecomment-1014898795
> 嗨,你好,我也遇到了一摸一样的问题,版本2.2.0,consumer数量发生变化时,PushConsumer在Rebalance时部分queue卡住
>
> @ifplusor @ShannonDing
你是什么消费模式?
--
This is an automated message from
francisoliverlee merged pull request #1077:
URL: https://github.com/apache/rocketmq/pull/1077
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
francisoliverlee merged pull request #3683:
URL: https://github.com/apache/rocketmq/pull/3683
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
guyinyou commented on issue #3747:
URL: https://github.com/apache/rocketmq/issues/3747#issuecomment-1014601117
The key point is that it may lead to consistency problems, not repeated
consumption. Repeated consumption is allowed in rocketmq
--
This is an automated message from the Apache
309791679 commented on issue #771:
URL:
https://github.com/apache/rocketmq-client-go/issues/771#issuecomment-1014566990
Restart the service within 10 seconds to pull the previously consumed
messages
--
This is an automated message from the Apache Git Service.
To respond to the message,
309791679 opened a new issue #771:
URL: https://github.com/apache/rocketmq-client-go/issues/771
Normal transmission
![image](https://user-images.githubusercontent.com/26238458/149777983-bb0fc968-628f-4072-a544-4f557b0d984b.png)
Normal reception
Cannot mark message
codecov-commenter commented on pull request #3769:
URL: https://github.com/apache/rocketmq/pull/3769#issuecomment-1014508489
#
coveralls commented on pull request #3769:
URL: https://github.com/apache/rocketmq/pull/3769#issuecomment-1014508216
[![Coverage
Status](https://coveralls.io/builds/45681033/badge)](https://coveralls.io/builds/45681033)
Coverage decreased (-0.07%) to 50.986% when pulling
zhongxiongzeng opened a new pull request #3769:
URL: https://github.com/apache/rocketmq/pull/3769
**Make sure set the target branch to `develop`**
for issues #3764
## What is the purpose of the change
X
## Brief changelog
XX
## Verifying this
zhongxiongzeng closed pull request #3766:
URL: https://github.com/apache/rocketmq/pull/3766
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
codecov-commenter commented on pull request #3766:
URL: https://github.com/apache/rocketmq/pull/3766#issuecomment-1014378770
#
coveralls commented on pull request #3766:
URL: https://github.com/apache/rocketmq/pull/3766#issuecomment-1014378622
[![Coverage
Status](https://coveralls.io/builds/45676283/badge)](https://coveralls.io/builds/45676283)
Coverage decreased (-0.01%) to 51.045% when pulling
gaoyf commented on issue #293:
URL:
https://github.com/apache/rocketmq-client-cpp/issues/293#issuecomment-1014326087
我也是,日志也一样,@YellowOldOdd @ifplusor @ShannonDing
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
danolphoenix opened a new issue #3768:
URL: https://github.com/apache/rocketmq/issues/3768
Hi all (*´▽`)ノ, I tried to run a rocketmq cluster with v4.9.2 in K8S pods
with aclEnable=true...and run into some trouble
according to this page:
zhongxiongzeng closed pull request #3767:
URL: https://github.com/apache/rocketmq/pull/3767
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
zhongxiongzeng opened a new pull request #3767:
URL: https://github.com/apache/rocketmq/pull/3767
**Make sure set the target branch to `develop`**
## What is the purpose of the change
X
## Brief changelog
XX
## Verifying this change
zhongxiongzeng opened a new pull request #3766:
URL: https://github.com/apache/rocketmq/pull/3766
**Make sure set the target branch to `develop`**
## What is the purpose of the change
X
## Brief changelog
XX
## Verifying this change
zhongxiongzeng closed pull request #3765:
URL: https://github.com/apache/rocketmq/pull/3765
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
zhongxiongzeng opened a new pull request #3765:
URL: https://github.com/apache/rocketmq/pull/3765
**Make sure set the target branch to `develop`**
for issues #3764
## What is the purpose of the change
X
## Brief changelog
XX
## Verifying this
zhongxiongzeng opened a new issue #3764:
URL: https://github.com/apache/rocketmq/issues/3764
The issue tracker is **ONLY** used for bug report(feature request need to
follow [RIP
process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal)).
Keep in mind, please check
45 matches
Mail list logo