pulsar

I would recommend starting by moving the journal disks to SSD first, as they are in the immediate write path. It would also split the writes across 2 different disk controllers.

“Is it critical to move everything to sdd setup where we can mount zk and journal on same disk”  &lt;--- DON’T DO THIS!!  Yes, the each need SSD for performance, but they each need dedicated SSDs

Awesome, thank you so much for the clarification.

Most likely, unless you have a very large ingestion rate. The journal acts as a short-term buffer

I use 2 GB nvme drives for journal and zk disks, and 4 SSDs in a raid configuration for my ledgers in my home lab

not necessarily, I prefer to spread the writes across multiple disks. The storage pool is used across all my k8s applications, not just Pulsar

<https://github.com/david-streamlio/microk8s-install> step 10,

<https://github.com/david-streamlio/microk8s-install/blob/main/configs/ssd-raid-sc.yaml> requires a single mount point, so raiding 4 disks into a single mount point works best :smiley:

Fantastic! Also helpful that nvme is there as an option as well.

Hi <@U9NHC1ETG> I have another quick question. Is zookeeper particular about where it lives in regards to pulsar? For example, we have a pulsar k8s node running with all components, but I'd like to move zookeeper mount path away from it so that the journal can use nvme. Will this cause problems if we allow zookeeper to live on a separate node away from pulsar components?

ZK can run anywhere in the cluster. All that is required is network access between the brokers/bookie and ZK.