xche opened a new pull request #10491:
URL: https://github.com/apache/pulsar/pull/10491
Fixes #8575
Motivation
The reason for this problem is that there is only one PulsarClient in a
functionWorker instance, and the number of externalExecutorProvider thread
pools in PulsarClient is 1, so all consumers share the same listener executor.
Therefore, when one or more tasks stoped, the listener executor will be
blocked, and finally other tasks will stop consuming data.
### Modifications
1. The same subscriber uses the same thread pool
2. Adding “numListenerThreads” configuration parameter in WorkerConfig
3. When PulsarSource is closed then clear queue to prevent listener executor
from being blocked
### Verifying this change
- [ ] Make sure that the change passes the CI checks.
*(Please pick either of the following options)*
This change is a trivial rework / code cleanup without any test coverage.
*(or)*
This change is already covered by existing tests, such as *(please describe
tests)*.
*(or)*
This change added tests and can be verified as follows:
*(example:)*
- *Added integration tests for end-to-end deployment with large payloads
(10MB)*
- *Extended integration test for recovery after broker failure*
### Does this pull request potentially affect one of the following parts:
*If `yes` was chosen, please highlight the changes*
- Dependencies (does it add or upgrade a dependency): (yes / no)
- The public API: (yes / no)
- The schema: (yes / no / don't know)
- The default values of configurations: (yes / no)
- The wire protocol: (yes / no)
- The rest endpoints: (yes / no)
- The admin cli options: (yes / no)
- Anything that affects deployment: (yes / no / don't know)
### Documentation
- Does this pull request introduce a new feature? (yes / no)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs
/ not documented)
- If a feature is not applicable for documentation, explain why?
- If a feature is not documented yet in this PR, please create a followup
issue for adding the documentation
--
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:
[email protected]
