[GitHub] [pulsar] alphashaw edited a comment on issue #5770: Pulsar Broker Sometimes does not return CommandSendReceipt/CommandSendError to prducer send CommandSend

[GitBox <gi...@apache.org>]

alphashaw edited a comment on issue #5770: Pulsar Broker Sometimes does not return CommandSendReceipt/CommandSendError to prducer send CommandSend
URL: https://github.com/apache/pulsar/issues/5770#issuecomment-559899675
 
 
   @jiazhai  Thanks for the swift response. It seems that my last questioned wasn't clear semantically. Let me rephrase it: 
   
   > From the client end, I understand multiple producers (partitioned/not) might be using the same underlying TCP connection. Also I understand the **sequence_id** (for necessary commands)  for each producer using the same connection must be unique. My question is, for these client connection-shared producers, does the broker serially handles their requests? In order words, if **p1** and **p2** represents two arbitrary producers sharing the same client connection and **(req1, res1),(req2, res2)** are at some point represents their request and response pairs respectively, if **req1 < req2** in time order, is it guaranteed that **res1 < res2** ??

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services