-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
still consumption blocked after issue #944 #947
Comments
This problem has not been solved?
|
一般的, 有这种日志
表示消息消费消费太慢,本地缓存消息没有被及时消费,引起client的pull线程挂起,这个也可以成为 “背压机制” rocketmq-client-go/consumer/push_consumer.go Lines 715 to 729 in 26142da
建议记录下本地消费耗时,以此来确认下是客户端背压机制有问题, 还是消费慢。 |
@francisoliverlee 没有报错确实没有必要打印出来,或者你设计一个关闭的参数吧,不断打印确实不太好 |
@nelsonkti 这个是客户端的消费被压机制,需要日志来提醒使用者消费太慢,不打日志的话,用户如何去知道自己消费堆积的原因呢? 简单的关闭可能不是一个好选择,当然如果有更好的办法的话,可以直接通过 issue 描述解决 :-D |
I used the commit: f3349bd which says it fixed the push consumer blocked issue #944. But in my experience, consumer is still blocked while rocket mq actually has newest msg produced.
some logs like this:
then, after some minutes, the client continue consumed out new msg.
For short, the client do the loop: consumed some msg ---> blocked for a period of time ----> continue consumed out msg ----> blocked for a period of time ---> continue consumed out msg...
PS:
consumer code like this:
UPDATED:
when produced 1 msg per second, the block issue didn't happen.
when produced 10 msg per second, the block issue always happen.
WHY:
The text was updated successfully, but these errors were encountered: