GitHub user lhotari added a comment to the discussion: Thousands of cluster geo-replication for fan-in aggregation ?
> These c1..cN are pulsar-standalone instances running on a smaller footprint > devices (1core-1GBmem) with very few topics & very small byte rate (kb/sec) > to the cAgg cluster. btw. It's worth considering to use Zookeeper for pulsar-standalone since it defaults to use Rocksdb for metadata storage. Some users have reported stability issues with the Rocksdb metadata storage. More details in https://github.com/apache/pulsar-site/pull/871 . pulsar-standalone hasn't been designed for production use cases, but if it works for this type of use case, I guess that's great. I think that even with low resources, it might be worth considering a docker compose setup or even k3s setup with separate JVMs for broker, zookeeper and bookie. You'd definitely want to tune the JVM options for this type of use cases. GitHub link: https://github.com/apache/pulsar/discussions/22438#discussioncomment-9018919 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
