BigQuery current and new jobs stuck on RUNNING

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Starting any new Job gets stuck in status RUNNING (1,5 hour 
job_4SZQOEtcxE_N7ztEjcbXFVDjpd0)
2.Data is written to and loaded from Google Storage
3.This proces is started from cron jobs which may have overwritten data present 
in Google Storage during a BigQuery job..?

What is the expected output? What do you see instead?
Expect Job succes or failure within a few minutes for very small imports. 
Instead Jobs are queueing up on status RUNNING.

Please provide any additional information below.
Deleted csv file from Google Storage to force an error on the job. 30 minutes 
after deleting 1 job (job_vWffxWO8yt0MMrpN6LRcL3JjnPQ) gets error state. Still 
12 on RUNNING.

Original issue reported on code.google.com by joc...@wecross.nl on 9 Jul 2015 at 3:21

[GoogleCodeExporter]

I, too, have a load-from-GCS job that's been in the running state for about 40 
minutes now. Typical running time is 3-5 minutes.

Job ID: job_k-S6ugH39E063LsIUuFuxpoHew4

Original comment by ja...@plumgroups.com on 9 Jul 2015 at 3:46

[GoogleCodeExporter]

Thanks for the report.  There's an incident in progress where some projects are 
seeing backlogged load and export jobs stuck in the RUNNING state.  We're 
working to resolve the issue - will provide updates as we know more.

Original comment by dk...@google.com on 9 Jul 2015 at 4:31

• Changed state: Accepted

[GoogleCodeExporter]

The incident has cleared - all jobs previously stuck in the RUNNING state have 
completed, and newly inserted jobs should run as expected.

Original comment by dk...@google.com on 9 Jul 2015 at 6:08

• Changed state: Fixed