-
Notifications
You must be signed in to change notification settings - Fork 241
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
Add uses bulkdata argument to paasta spark run #3995
base: master
Are you sure you want to change the base?
Conversation
This makes the change to paasta spark run so that https://github.yelpcorp.com/sysgit/yelpsoa-configs/pull/52010 will work as expected I'm not checking here if the /nail/bulkdata volume is specified in the spark config, e.g `spark.kubernetes.executor.volumes.hostPath.0.mount.path=/nail/bulkdata` - doing this and setting uses_bulkdata set to True would result in multiple docker volumes being set which would cause a failure. This follows on from [this conversation in slack](https://yelp.slack.com/archives/CA8BWU65D/p1729768030212919) and will allow us to complete [this project](https://yelpwiki.yelpcorp.com/display/PRODENG/Project+Incredible+Bulk)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm (and i think it's perfectly fine to not check if there's a spark config for mounting /nail/bulkdata
since it looks like that's not something anyone is currently doing - and i doubt any of our spark users would add such a mount un-prompted)
that said i'll let someone for ml compute ship since they own this file in its entirety :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm. Agree that as Luis mentioned no need to check if the user uses Spark options to mount bulkdata, and I also double checked that no one is doing that
"--uses-bulkdata", | ||
help="Mount /nail/bulkdata in the container", | ||
action="store_true", | ||
default=False, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we not set the default to true for now, then roll out my change to add the flag everywhere, and then set the default to false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point - I thought by default we are getting the /nail/bulkdata mount from the host, but I cant actually see where that is happening - these changes are to configure_and_run_docker_container - which calls run_docker_container which then calls os.execlpe("paasta_docker_wrapper", *docker_run_cmd, merged_env) which is defined here but none of these seem to include system_volumes from /etc/paasta/volumes.json
so i'm actually unsure why spark-run is mounting the bulkdata volume at all currently
@nemacysts / @chi-yelp do you have any ideas where the /nail/bulkdata mount is happening? Or is there any way I can test this like I did with #3893 in the paasta playground
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm I checked using the following command and it seems /nail/bulkdata
isn't mounted:
./.tox/py38-linux/bin/paasta spark-run --aws-profile=dev --cmd bash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so volumes are found from the instance config here which is then passed to spark conf here and then later referenced here
Meaning it is important that I check if /nail/bulkdata
is in the list of volumes before adding it. And the command @chi-yelp shared is not mounting bulkdata because its not specifying a service / instance that uses bulkdata - @chi-yelp was that command run on my branch?
This makes the change to paasta spark run so that
https://github.yelpcorp.com/sysgit/yelpsoa-configs/pull/52010 will work as expected
I'm not checking here if the /nail/bulkdata volume is specified in the spark config, e.g
spark.kubernetes.executor.volumes.hostPath.0.mount.path=/nail/bulkdata
This follows on from this conversation in
slack and will allow us to complete this
project