GCP Dataflow job sitting in "not started"

0
votes

I started 13 dataflow jobs ~ 43 minutes ago and they are all sitting in "not started". There are no logs in stacktracer or GCP logging. Another answer on stack overflow had a googler fix the problem on their end.

I have tried all of the other answers I can find.

My dataflow api is enabled (I was running jobs with no issues 2 days ago, nothing has changed). There are no logs to check, so dead end there. I have checked my quotas and none of them are throttling.

Any help from a googler or someone with other ideas would be greatly appreciated!

1
google-cloud-platformgoogle-cloud-dataflow
Where does the Dataflow job located? If us-central1, you might have been affected by the current internal issue. Mitigation work is continuing by our Engineering Team. - Ronnaver
Workaround: Retry the job in a different region if possible. Note: The '--region' flag must be set explicitly if using the CLI or SDK. Ref: cloud.google.com/dataflow/docs/concepts/… - Ronnaver
@Ronnaver that is probably the issue. I will retry in another region. Side note. I checked the Google Cloud Platform status and "All services normal". But, when I just clicked through to the detailed portion then there was the note about dataflow having issues. Weird. Thank you for the very quick answer! - PeterH

1 Answers

2
votes

Where does the Dataflow job located? If us-central1, you might have been affected by the current internal issue. Mitigation work is continuing by our Engineering Team.

Workaround: Retry the job in a different region if possible. Note: The '--region' flag must be set explicitly if using the CLI or SDK. Ref: https://cloud.google.com/dataflow/docs/concepts/regional-endpoints#using_regional_endpoints

It states now in the Google Cloud Status Dashboard, "Cloud Dataflow service is experiencing an issue with the creation of new Dataflow workflows in us-central1"