kafkaesque | A simple Kafka Producer | Stream Processing library

This is my first attempt to deploy Pulsar on AKS v1.15.11.

I'm getting a not very verbose error messages from 2 pods that are "unscheduled" :

Firtst pod unscheduled "pulsar-zookeeper-0"

[Pod] [pulsar-zookeeper-0] FailedScheduling: selectedNode annotation value "" not set to scheduled node "aks-agentpool-20916223-vmss000001"

Second Pod unscheduled "pulsar-bookkeeper-0"

[Pod] [pulsar-bookkeeper-0] FailedScheduling: selectedNode annotation value "" not set to scheduled node "aks-pulsar-20916223-vmss000001"

Here's a detailed procedure of what I did. I've used official helm-charts for deployments

I'm investigating a tech for our cluster. Pulsar looks good, but the usage looks more like a queueing system. Of course, queueing system is good to have, but I have a specific requirement: broadcasting.

We would like to use one machine to generate the data and publish it to a Pulsar topic. Then we use a group of servers, forming a replica. Each server consumes the message flow on that topic, and serves clients via WebSocket.

This is different than the Shared subscription, because each server needs to receive all messages, not a fraction of it.

I came to this post: https://kafkaesque.io/subscriptions-multiple-groups-of-consumers-on-pulsar-topic/ , which explains how to do such a job: each server needs create a new exclusive subscription, say use a UUID as its subscription name, from the unique exclusive subscription you can get the full message flow of that topic.

But since our server replica can be dynamic, so once some of the server restart, they will create new UUID subscription again, which will leave many orphan subscriptions on the topic, which eventually would become maintenance headache.

Anyone has the experience to setup a broadcast use case using Pulsar?