Big Query The job encountered an error during execution

Question

I've had this query in BigQuery that I have been updating every day for the last few months. It's been fine - some occasional errors, but retrying has solved the problem.

Bet last few days I am getting the error: The job encountered an error during execution. Retrying the job may solve the problem.

The error description says that it's an external error, so how can I fix that?

I have been retrying (with rather long pauses in between), but I still get the error. JobID example: bquxjob_152ced5d_169917f0145

Does anyone have any idea what's going on? Is there any data/time limitations I might encounter (but why just the last few days then)?

Answer 1

You can use CGP stackdriver to monitor your BigQuery process using this URL

Interesting information you can find among others are the queryTime heatmap and the Slot usage which might help you understand your problems better

On the subject of the external table usage, you can use Google transfer (See this link for details) to schedule a repeated transfer from CSV to BigQuery table. The below Image show you how to get to the transfer set up page from the webUI

Answer 2

I encountered this dreadfully useless error in a scheduled query. It was working great and then one day it stopped working at all and has been failing ever since without any other explanation. The StackDriver (now "Logs Explorer") showed nothing more enlightening:

jobStatus: {
  errorResult: {
    code: 14
    message: "Error encountered during execution. Retrying may solve the problem."
    }
    errors: [
      0: {
      code: 14
      message: "Error encountered during execution. Retrying may solve the problem."
    }
  ]
  jobState: "DONE"
}

Figuring out the actual issue takes a long time because scheduled queries start slowly since they use BATCH priority. What I found in my case was that the partitioned table and "Partition field" setting in the scheduled query was the culprit. I dropped the table and removed the partition field and voila the thing works again (although far from ideal since I need partitioning).

I hope this helps someone else running up against that useless error but in any case, I hope the good folks working on BigQuery find a better error to bubble up.

Answer 3

I ran into this problem when replacing the contents of a partitioned table. Two retries did not help. When I removed the --range_partitioning from the command the update was processed correctly. The table remained partitioned.

So there seems to be an issue about updates to partitioned tables, and when that is the cause these errors might not benefit from retry. I don't know whether there are other causes of this error.

Answer 4

This kind of issue probably has a lot to do with BigQuery quota errors: https://cloud.google.com/bigquery/docs/troubleshoot-quotas#ts-number-column-partition-quota , as mentionned by other answers, such as the 4000 partitions-by-table quota.