You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "poorbarcode (via GitHub)" <gi...@apache.org> on 2023/09/08 08:04:11 UTC
[GitHub] [pulsar] poorbarcode commented on pull request #21144: [fix] [client] fix same producer/consumer use more than one connection per broker
poorbarcode commented on PR #21144:
URL: https://github.com/apache/pulsar/pull/21144#issuecomment-1711250874
> Some how, it looks like related to this change https://github.com/apache/pulsar/pull/12846?
No, the PR https://github.com/apache/pulsar/pull/12846 just added a field `epoch` and renamed `equals` to `isSuccessorTo`.
> Why not just fix the isSuccessorTo method?
In our design, we assume that the io events are sequential. But one producer/consumer can use different connections, making the sequential broken. I think the current solution is better.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org