Service Outage - Bigquery for import

[GoogleCodeExporter]

I had similar ticket before in StackOverflow.

We just noticed that our imports for Bigquery is failing with following message:

INFO:root:{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "internalError",
    "message": "Unexpected. Please try again."
   }
  ],
  "code": 500,
  "message": "Unexpected. Please try again."
 }
}

INFO:root:{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "backendError",
    "message": "Backend Error"
   }
  ],
  "code": 503,
  "message": "Backend Error"
 }
}

This has been happening now for over 5+ hr. It started at 6:15 am PST April 
1st, 2013. The console is reporting no known issues.

Do we know when the service will be back up.

Here are some of the job example: job_b4c87ef9931b4a75b1869b6e7157725b 
job_369c14f202ca46f3a2a6b931b97ed99d

Original issue reported on code.google.com by Vis...@sweetlabs.com on 1 Apr 2013 at 7:13

[GoogleCodeExporter]

Are you still seeing these errors?

Original comment by manoochehri@google.com on 4 Apr 2013 at 6:59

[GoogleCodeExporter]

Not seeing this anymore. The service came back to normal around 12:45 pm. So we 
had problem for 6 hr 30 min. 

Do we know cause of the problem? Last time we had same issue and was related to 
metadata. See here:
http://stackoverflow.com/questions/14637562/service-outage-bigquery-for-import

Original comment by Vis...@sweetlabs.com on 5 Apr 2013 at 4:10

[GoogleCodeExporter]

We are getting this issue again today April 9th - 9:00 am PST.

"status": {
  "state": "DONE",
  "errorResult": {
   "reason": "backendError",
   "message": "Connection error. Please try again."
  },
  "errors": [
   {
    "reason": "backendError",
    "message": "Connection error. Please try again."
   }
  ]
 },
 "statistics": {
  "startTime": "1365523306588",
  "endTime": "1365523306588"
 }

Original comment by Vis...@sweetlabs.com on 9 Apr 2013 at 4:08

[GoogleCodeExporter]

We saw increased number of import errors last week 5/26 - 5/31. All the errors 
were giving backendError as described above. We found that even though API 
returns above error, the import works fine.

Original comment by Vis...@sweetlabs.com on 3 Jun 2013 at 5:11

[GoogleCodeExporter]

Can you provide some job IDs for the recent failures?

Just to clarify, the import appears to have succeeded (i.e., data appears in 
the table), but the API indicates a backend error on the job?

Original comment by jcon...@google.com on 6 Jun 2013 at 10:19

[GoogleCodeExporter]

>>Just to clarify, the import appears to have succeeded (i.e., data appears in 
the >>table), but the API indicates a backend error on the job?

That is correct.

Here are few jobs:
job_e118fc550cc545eab217778089befc0a
job_20bffbe010ee40cd9caf4232dfcb974f
job_0f3dc09b3d03455b90a04f20d54ea9e0

Original comment by Vis...@sweetlabs.com on 6 Jun 2013 at 11:49

[GoogleCodeExporter]

Closing ticket due to age; if you experience similar issues in the future, 
please provide your project id and relevant job id's.  Thank you!

Original comment by thomasp...@google.com on 25 Apr 2014 at 6:34

• Changed state: Done