[Bug] BatchConsumerPolicy violation

Abierto
  • ¿Algo no está bien?
#617 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, python
Área
stream-processing

Línea de trabajo

The report concerns batch receive on a partitioned Pulsar topic, where a batch policy with max_num_message=400 and timeout=-1 hangs while timeout=50ms does not. Start by reproducing the stall with a partitioned topic and a batch receive loop, then trace how the batch policy's count and timeout conditions are evaluated in the C++ client. Done means batch_receive returns after 400 messages and no longer blocks indefinitely when the timeout is disabled.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Search before asking
  • I searched in the issues and found nothing similar.
Version

OS: Debian GNU/Linux
version 11 (Bullseye)

pulsar version 3.0.13

Minimal reproduce step

Use pulsar-client python library 3.1.0

initialise a BatchConsumerPolicy on n different partitions of the same topic with timeout = -1 , max_num_bytes = -1, max_num_message = 400

and then subscribe to partitions with this policy and begin consuming using batch_receive() method

What did you expect to see?

Expected that the consumption of messages from any partition will happen normally (wait for the max num and then return)

What did you see instead?

It was observed that the batch_receive() method got permanently stuck after a few days. Restarting the python program mitigated the issue. Another python program running a different subscription on the same topic with BatchConsumerPolicy(max_num_message=-1,max_num_bytes=-1,timeout=1second) ran perfectly without any issues and the topic was such that there would be 0 produce at most a few minutes in a couple of days. Whenever the first process got stuck, the second one never got stuck. The first one got stuck at seemingly irregular patterns but definitely eventually.

Another point to note is that this was the only difference between both of them.

Following this observation I changed the BatchConsumerPolicy from BatchConsumerPolicy(max_num_message=400,max_num_bytes=-1,timeout=-1) to BatchConsumerPolicy(max_num_message=-1,max_num_bytes=-1,timeout=50ms) and then that process never got stuck (3 months in now)

Anything else?

I suspect that max_num_messages and max_num_bytes are treated at the same priority as per
https://pulsar.apache.org/api/python/3.0.x/pulsar.ConsumerBatchReceivePolicy.html

but timeout is at a lower priority which might cause some deadlock

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Lenguaje dominante
C++
Estrellas
72
Forks
93
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/pulsar-client-cpp

Todos los issues de apache/pulsar-client-cpp

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.