Hi ! is Apache Pinot Server stateless in Kubernetes deployment ? As far as my understanding if server pod is restarted then the segments on that pod will copied to other pods and that metadata should be stored in ZK and whenever new pod comes up it again get's connected with ZK for future operations. Can anyone please correct me if my understanding is wrong. @Mayank @Jackie

Conceptually it can be stateless, but we usually configure it as stateful to avoid re-downloading all segments when server starts

Are your writing you own helmChart or k8s deployment? If you are using current OSS helmChart, then it’s a statefulSet, we recommend to use cloud provided network disk for server storage(e.g. aws ebs), so no matter where the pod starts, the disk will be re-mount to that pod and you don’t have to download data from remote(e.g. s3) again.

@Xiang Fu if you use block storage like that , aren’t you giving up some performance compared to faster local disks like you can get on ec2 i instance types ?

Depends on the use case, for users who want bigger local storage, they usually go with ebs. For critical latency sensitive use cases, we do support i4 those kind of NVMe SSDs, but we can do some stickiness on instance re-assignment to ensure the restart time is minimal