linlinnn commented on issue #10173:
URL: https://github.com/apache/pulsar/issues/10173#issuecomment-81795
I think another cause is that when exist pending receive, we should response
the head of incomingMessages queue first instead of returning current message.
And then we process the
linlinnn commented on issue #10173:
URL: https://github.com/apache/pulsar/issues/10173#issuecomment-817137335
@MarvinCai Yes, I agree that. I tried as you said before, but still got
wrong order randomly with partitioned topic which have only one partition or
use custom routing that just re
linlinnn commented on issue #10173:
URL: https://github.com/apache/pulsar/issues/10173#issuecomment-816460077
Emm. I was not able to spot any bug yet :( @codelipenghui @eolivelli Please
take a look for this issue.
--
This is an automated message from the Apache Git Service.
To respond to
linlinnn commented on issue #10173:
URL: https://github.com/apache/pulsar/issues/10173#issuecomment-816263982
When I change to non partitioned topic, it works well always. Something
broken the order of the message sequence when consuming partitioned topic.
--
This is an automated message
linlinnn commented on issue #10173:
URL: https://github.com/apache/pulsar/issues/10173#issuecomment-816025121
The cause of this issue is when the key is null and the route is
SinglePartition, the partitioned producer will randomly pick one single
partition.
--
This is an automated messa
