I’m using Pulsar for communication between services and I’m experiencing flakiness in a quite simple test of producers and consumers. In JUnit 4 test, I spin up (my own wrappers around) a ZooKeeper server, a BookKeeper bookie, and a PulsarService; the configurations should be quite standard. The test can be summarized in the following steps: build a producer; build a
Tag: apache-pulsar
Pulsar client thread balance
I’m trying to implement a Pulsar client with multiple producers that distributes the load among the threads, but regardless the value passed on ioThreads() and on listenerThreads(), it is always overloading the first thread (> 65% cpu while the other threads are completely idle) I have tried a few things including this “dynamic rebalancing” every hour(last method) but closing it
Apache Beam: Kafka consumer restarted over and over again
I have this very simple Beam Pipeline that reads records from a Kafka Topic and writes them to a Pulsar Topic: From my understanding this should create exactly one Kafka Consumer that pushes it’s values down the Pipeline. Now for some reason the Pipeline seems to restart over and over again creating multiple Kafka Consumers and multiple Pulsar Producers. Here