Skip to content
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

Make sure the client can get response when encounter producer busy exception. #13245

Commits on Dec 12, 2021

  1. Make sure the client can get response when encounter producer busy ex…

    …ception.
    
    When the producer with the same producer ID and same connection,
    Of course this usually doesn't happen. When cherry-picking apache#12846,
    the test using the same producer ID https://github.com/apache/pulsar/pull/12846/files#diff-b73845cd7706e03b89122a21b3e60c36c95ce6a0c7dd4574f8eda3fc67dd02b1R867-R876
    And after we apply the change https://github.com/apache/pulsar/pull/8685/files#diff-1e0e8195fb5ec5a6d79acbc7d859c025a9b711f94e6ab37c94439e99b3202e84R1161
    Only one request can get a response when encounter exceptions.
    
    The fix is make sure the broker don't miss the response to the client,
    we should make sure one request can get one response, otherwise the client
    side might get blocked.
    codelipenghui committed Dec 12, 2021
    Configuration menu
    Copy the full SHA
    9252645 View commit details
    Browse the repository at this point in the history