shibd opened a new pull request, #24100: URL: https://github.com/apache/pulsar/pull/24100
### Motivation The major issue is customer has a thread try to subscribe(create a consumer) to a topic. But the thread get interrupted before getting a response for the consumer creation by their scheduling service. - Thread A - call subscribe() method - Thread A - blocking on waiting for the response of the consumer creation - The user framework interrupted `Thread A` for aborting a job. - Cannot close the consumer since user will get InterruptedException and can't get consumer object ### Modifications - Added a variable named `interruptedBeforeConsumerCreation`. When this variable is true, the consumer needs to be closed. ### Verifying this change - You can run `testInterruptedWhenCreateConsumer ` to reproduce this issue. ### Documentation <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> - [ ] `doc` <!-- Your PR contains doc changes. --> - [ ] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [x] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> ### Matching PR in forked repository PR in forked repository: <!-- ENTER URL HERE --> <!-- After opening this PR, the build in apache/pulsar will fail and instructions will be provided for opening a PR in the PR author's forked repository. apache/pulsar pull requests should be first tested in your own fork since the apache/pulsar CI based on GitHub Actions has constrained resources and quota. GitHub Actions provides separate quota for pull requests that are executed in a forked repository. The tests will be run in the forked repository until all PR review comments have been handled, the tests pass and the PR is approved by a reviewer. --> -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
