the zk fsync is taking too long (4+ seconds). what’s in the broker log? in general, you can disable fsync or separate the zk data and datalog (journal) disks to avoid disk io issue.
y
yuki
07/12/2023, 11:07 AM
I’ve got some response in github discussion, the main reason is that helm chart does not support k8s 1.24+ , and someone had already patched it. I’m going the try the latest helm charts. BTW, how to disable fsync with Pulsar?