Hi Mich, No, it is not Google cloud. It is simply Kubernetes deployed over Bare Metal Platform. I am not clear for pros and cons of Shared Volume vs NFS for Read Write Many. As NFS is Network File Server [remote] , so I can figure out that Shared Volume should be more preferable, but don’t know the other sides [drawback].
Regards Ranju From: Mich Talebzadeh <mich.talebza...@gmail.com> Sent: Thursday, March 11, 2021 5:22 PM To: Ranju Jain <ranju.j...@ericsson.com.invalid> Cc: user@spark.apache.org Subject: Re: Spark on Kubernetes | 3.0.1 | Shared Volume or NFS Ok this is on Google Cloud correct? LinkedIn https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw Disclaimer: Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction. On Thu, 11 Mar 2021 at 11:29, Ranju Jain <ranju.j...@ericsson.com.invalid<mailto:ranju.j...@ericsson.com.invalid>> wrote: Hi, I need to write all Executors pods data on some common location which can be accessed and retrieved by driver pod. I was first planning to go with NFS, but I think Shared Volume is equally good. Please suggest Is there any major drawback in using Shared Volume instead of NFS when many pods are writing on the same Volume [ReadWriteMany]. Regards Ranju
