apache / apache/pulsar-client-cpp
Shared consumers do not receive messages in C++ and acknowledged messages get redelivered
- Lenguaje dominante
- C++
- Estrellas
- 71
- Forks
- 90
- Merge medio
- 2 h 33 min
- PR fusionados (30 d)
- 3
Descripción
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
Guía de contribución
Línea de trabajo
Comienza con el flujo de shared consumers en C++ descrito en el issue, cubriendo tanto las llamadas síncronas como las asíncronas de receive y acknowledge. Reprodúcelo en un topic persistente no particionado con shared consumers, compáralo con exclusive consumers y verifica que cada mensaje se entregue al menos a un consumer sin que los mensajes confirmados se vuelvan a entregar.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- cpp
- Área
- distributed-systems
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100