-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Description
Search before asking
- I searched in the issues and found nothing similar.
Motivation
C++ client consumers have not implemented memory limits yet.
Solution
There are several key points to achieving this feature.
- Reconstructing the consumer structure.
- [refactor][client c++] Delete PartitionedConsumerImpl, use MultiTopicsConsumerImpl instead pulsar#16969
- Abstract
ConsumerBase, put together some common logic.
- Refactoring single-consumer and MultiTopicConsumer transports type.
- In the current implementation of C++, messages are sent to multi-topic consumers by blocking queue + listener, which is an old historical implementation. If you want to achieve memory limits, you need to do the same as the current java implementation, let
MuiltiTopicConsumertake the initiative to control the message.
- In the current implementation of C++, messages are sent to multi-topic consumers by blocking queue + listener, which is an old historical implementation. If you want to achieve memory limits, you need to do the same as the current java implementation, let
Alternatives
Here's an imperfect draft: apache/pulsar#16933
Anything else?
No response
Are you willing to submit a PR?
- I'm willing to submit a PR!
Metadata
Metadata
Assignees
Labels
No labels