This message was deleted.

why 2.9.4? from the screenshot, the zk-2 is not ready. when zk cluster is not ready, initjob won’t kick off bookie and broker sts. you need to fix the zk situation. It might be a bug of zk in low cpu situation. try 2.10

check if Zookeeper has enough resources as Yu Wei Sung mentioned pls

0/5 nodes are available: 1 node(s) didn’t match pod anti-affinity rules, 3 Insufficient cpu, 4 Insufficient memory. preemption: 0/5 nodes are available: 5 No preemption victims found for incoming pod.”

this error is showing multiple resource issues.

3 Insufficient cpu, 4 Insufficient memory

this means you k8s is not able to schedule the pod since there’s no node that have enough CPU/memory. Possible solutions are: • decrease the desired cpu/mem for each pod - check the “resources” section for each component, e.g. for bookies: https://github.com/apache/pulsar-helm-chart/blob/b3c19fd7fc7067e67940244777dd4241c8295dd4/charts/pulsar/values.yaml#L470-L473 • add more nodes • reduce the replicas for each component @rahul

the above issue almost resolved after increasing the total CPU,fyi🙂 Could anyonre tell me why does pulsar-prometheus-node-exporter is present multiple times and how does this help in our pulsar working.

node exporter is daemonset. 1 pod on each worker node.

i got this error "0/7 nodes are available: 1 node(s) didn't have free ports for the requested pod ports. preemption: 0/7 nodes are available: 7 No preemption victims found for incoming pod" for pulsar-prometheus-node-exporter-mx6f8 . is it due to cpu insufficiency or some node config.(only this is left to run)

are you running this in single machine? using kind?

actually the problem was, some other unrequired pod was running in the requested port, and thus the problem. thank you😄