-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trino K8S and disk caching #273
Comments
As Ashhar mentioned in the original discussion, StatefulSets are not needed, because the cache does not need to be associated with any specific worker node. You can use whatever volumes you prefer, either emptyDir or other volume types. I'm not sure what's the concern here. Are you having issues with configuring volumes? |
We are using managed k8s in a private cloud. We can only connect additional network-ssd/nvme for cache via PVC. Therefore we wanted to use StatefuleSet with VolumeClaimTemplate for automatic provisioning. With emptyDir we can connect volume only to the root partition of the cluster node. There are mentions in the documentation that you should avoid this configuration. There are a few questions:
If the described options are not acceptable, then we will think how to add local disks to the workernode. In this case StatefulSet will not be necessary. |
The docs you referenced are written for bare metal installations, not containers. The recommendation not to use a root mount point is to avoid using up all the available disk space on the host. AFAIK, regular PVCs used by Deployments can also be dynamically provisioned: https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/#using-dynamic-provisioning If you really need to use StatefulSets, you can fork the chart, and modify it as needed. |
Thanks for the reply! We will set up one of the suggested options and test it. |
Hello there.
Does anybode implement this https://trino.io/docs/current/object-storage/file-system-cache.html in kubernetes? Looks like it's best soluiton for baremetal installation but not for the K8S with Deployemnts. There are workarounds:
Moved from here trinodb/trino#24395
I didn't get this recomendation in detail trinodb/trino#24395 (comment)
The text was updated successfully, but these errors were encountered: