Rockyyost edited a comment on issue #10390:
URL: https://github.com/apache/pulsar/issues/10390#issuecomment-830091399
Sorry @MarvinCai I didn't see your comment before I added another.
I haven't set priorities on the consumer, that I know of. I use the Python
client.
Below is an example of the consumer I created.
self._consumer = self._client.subscribe(TopicName,
subscription_name=sub_name,
consumer_type=_pulsar.ConsumerType.Shared,
receiver_queue_size=0 )
I was able to finally get the expected behavior, at least initially, by
setting the receiver_queue_size to 0. Kubernetes spawn the max number of pods
and all the consumers in the pod subscribed, got messages, and went to work on
those messages. Then, they got more messages until the message queue went down
to 0. After which, the pods were destroyed except for three of them, which is
minimum we keep around.
However, sometime later, we publish another set of 4K messages and none of
the pods, which are still subscribed (as far as I can tell) have received any
of those messages. In fact, Pulsar doesn't seem to want to dispatch them. I've
tried killing all the pods, which cause Kubernetes to re-spawn them, but even
those new pods, after subscribing, get messages.
This leaves Pulsar a bit confusing. Messages are there, new once I created,
but it won't dispatch them.
--
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]
