You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.
In some cases (for example, log aggregation) it is desirable to have a hostpath volume mounted in the driver and executor pods. With #38 this will be possible, but I am not sure when it will be available.
So, something similar to #397 will be helpful for this case as well.
What I am proposing is an option to specify the hostpath volume and have it mounted in the driver and executor pods.
The text was updated successfully, but these errors were encountered:
I have made changes that support the following configuration for spark-submit command:
--conf spark.kubernetes.driver.hostpath.<hostpath_dir>=<container_mount_path>
If this approach sounds good, I can create a pull request for this change.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In some cases (for example, log aggregation) it is desirable to have a hostpath volume mounted in the driver and executor pods. With #38 this will be possible, but I am not sure when it will be available.
So, something similar to #397 will be helpful for this case as well.
What I am proposing is an option to specify the hostpath volume and have it mounted in the driver and executor pods.
The text was updated successfully, but these errors were encountered: