dongjoon-hyun edited a comment on issue #27364: [SPARK-31394][K8S] Adds support for Kubernetes NFS volume mounts URL: https://github.com/apache/spark/pull/27364#issuecomment-611589706 Thank you, @w4-sjcho . I updated the PR title accordingly. BTW, it's still difficult to understand your use cases. Please see the K8S NFS section again. - https://kubernetes.io/docs/concepts/storage/volumes/#nfs > An nfs volume allows an existing NFS (Network File System) share to be mounted into your Pod. Unlike emptyDir, which is erased when a Pod is removed, the contents of an nfs volume are preserved and the volume is merely unmounted. This means that an NFS volume can be pre-populated with data, and that data can be “handed off” between Pods. NFS can be mounted by multiple writers simultaneously. So, is the following your claim true? > NFS could be used using PVC when we want to use some clean new empty disk space, but in order to use files in existing NFS shares, we need to use NFS volume mounts. I didn't try NFS before. So, theoretically, there is no need to mount like this. So, I have a question on your problem. - Did you use this patch in your cluster with your local NFS? - When you try PVC NFS, is there any issue on the existing data? - If you use this in the cloud, did you try to use AWS EFS? - Is there any issue in that cloud NFS environment?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
