-
Notifications
You must be signed in to change notification settings - Fork 26
Unable to set Vertex runner disk size (but was able to in prefect 1) #158
Comments
I've realized my hack fix works, I was just confused as to how to deploy it. I needed to edit that file in the environment of the prefect agent who was receiving the jobs and sending them to vertex. So, for anyone looking for a work around, you can edit aiplatform.py locally and then also run the agent locally. |
As for a proper fix, would this be the approach?
I am not clear on if you can just add new Fields to infrastructure blocks and if that will bounce through prefect cloud correctly. |
@acgourley you can add things to infrastructure blocks, your local version will be registered with the API when it is saved. You just need the agent to have the same version. I'd be happy to review a pull request that adds the fields as you've described! |
Sure I'll throw a pull request together after I've tested it. Thanks for confirming the approach should work. |
Expectation / Proposal
In prefect v1 we could specify the machine parameters (like boot disk size) of the vertex runner. This functionality seems missing from this v2 version. It's critical for my use case which deals with large data processing.
I am open to any work around which allows me to edit the "workerPoolSpecs" ultimately sent to GCS. I've tried editing my local aiplatform.py to ask for a 500gb disk as follows
But even if I deploy the VertexAICustomTrainingJob with save("name", overwrite=True) and re-rerun the deploy, new jobs on vertex still show this in the run parameters:
"bootDiskSizeGb": 100
so it didn't seem to work.The text was updated successfully, but these errors were encountered: