Ulysse Petit
03/20/2025, 6:00 PMJake Kaplan
03/20/2025, 6:03 PMUlysse Petit
03/20/2025, 6:06 PMUlysse Petit
03/20/2025, 6:07 PMJake Kaplan
03/20/2025, 6:13 PMUlysse Petit
03/20/2025, 6:33 PMJake Kaplan
03/20/2025, 7:02 PMprefect worker start --name <my_worker>
, is it possible that the cloud run service is scaling multiple containers? If the names are different than each other (and the old names) that would be my next guess.
If it was a restart, that would be a "different worker" but I wouldn't expect them to both be Online
Ulysse Petit
03/20/2025, 8:21 PMgcloud run deploy prefect-worker --image=prefecthq/prefect:3-latest \
--set-env-vars PREFECT_API_URL=$PREFECT_API_URL,PREFECT_API_KEY=$PREFECT_API_KEY \
--service-account <YOUR-SERVICE-ACCOUNT-NAME> \
--no-cpu-throttling \
--min-instances 1 \
--startup-probe httpGet.port=8080,httpGet.path=/health,initialDelaySeconds=100,periodSeconds=20,timeoutSeconds=20 \
--args "prefect","worker","start","--install-policy","always","--with-healthcheck","-p","<WORK-POOL-NAME>","-t","cloud-run"
Jake Kaplan
03/20/2025, 8:26 PM--args
--args "prefect","worker","start", ... , "--name", "my_worker"
Can you try setting that and see if you're still seeing multiple? It may be a clue to what's going on.Ulysse Petit
03/20/2025, 9:49 PMUlysse Petit
03/21/2025, 4:24 PM