Github user lindzh commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/128
+1
Great! This is indeed buggy.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
Github user Jaskey commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/128
@evthoriz please update the jira's discriptions so that the user knows this
bug and determine whether they should upgrade
---
If your project is set up for it, you can reply to this email
Github user evthoriz commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/128
@Jaskey From the aspect of client, every batch request would cause printing
2 warning logs. But the further influence is it may damage the performance in
high throughput scenario where b
Github user Jaskey commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/128
+1.
This is is indeed buggy.
Would you please update the description that how the client behave for this
problem so that we make our users clear about this.
IMO, this
Github user lizhanhui commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/128
+1
Nice catch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled an
Github user dongeforever commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/128
@evthoriz Great catch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enab
Github user evthoriz commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/128
@zhouxinyu JIRA issue attached.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
