apache / apache/pulsar-client-cpp
Shared consumers do not receive messages in C++ and acknowledged messages get redelivered
- Vorherrschende Sprache
- C++
- Sterne
- 71
- Forks
- 90
- Ø Merge
- 2 Std. 33 Min.
- Gemergte PRs (30 T.)
- 3
Beschreibung
When using shared subscriptions with the C++ client we see the following issues:
* The consumers stop consuming silently after a period of time, without any obvious reasons (e.g. connection failure) or any unusual log messages. The issue seems to happen randomly. Recreating the consumers with the same parameters seems to fix this issue for a while. We are experiencing this issue both using the synchronous and the async APIs. The topic is non-partitioned persistent topic. The server is a standalone server. We only see this problem with shared consumers, it doesn't seem to happen if we change to exclusive.
* Acknowledged messages get redelivered to shared consumers in C++ after subscription. It seems to happen both with synchronous and async acknowledgment. The API docs on acknowledge() states that acknowleded messages should not be redelivered.
**To Reproduce**
Create shared consumers in C++ for a topic and call receive. The problem seems to happen randomly but relatively frequently. It does not occur with exclusive consumers.
**Expected behavior**
* At least one of the shared consumers should receive each message.
* Acknowledged messages should not be redelivered.
**Desktop (please complete the following information):**
- RedHat 7.x
Beitragsleitfaden
Rechercherichtung
Start with the C++ shared-consumer flow described in the issue, covering both synchronous and asynchronous receive and acknowledge calls. Reproduce it on a non-partitioned persistent topic with shared consumers, compare against exclusive consumers, and verify that every message is delivered to at least one consumer without acknowledged messages being redelivered.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- cpp
- Bereich
- distributed-systems
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100