报告API 503后端错误 [英] Reports API 503 Backend Error

查看:975
本文介绍了报告API 503后端错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在过去的几周里,我用来从Reports API检索用户使用报告的批处理任务失败,出现以下响应:

  com.google.api.client.googleapis.json.GoogleJsonResponseException:503 OK 
{
code:503,
errors:[{
domain:global,
message:Backend Error,
reason:backendError
}],
message:Backend Error
}

其他人是否看到此错误?看起来像是API上的内部错误。有什么我可以做我的目的,以避免这个问题?谢谢!

解决方案

当我有一个端点查询时,我在后端有一个503。
当你使用谷歌数据存储首先你必须在本地主机上运行它,所以它会创建一个名为datastore-indexes-auto.xml
的文件中的索引,这是自动生成的。

这是一个索引示例


 < ! - 在查询历史记录中使用了1次 - > 
< datastore-index kind =Conferenceancestor =truesource =auto>
< property name =namedirection =asc/>
< / datastore-index>


For the past couple of weeks the batch task I use to retrieve User Usage Reports from the Reports API has been failing with the following response:

com.google.api.client.googleapis.json.GoogleJsonResponseException: 503 OK
{
  "code" : 503,
  "errors" : [ {
    "domain" : "global",
    "message" : "Backend Error",
    "reason" : "backendError"
  }],
  "message" : "Backend Error"
}

Is anyone else seeing this error? Seems like an internal error on the API. Is there anything I can do on my end to avoid this problem? Thanks!

解决方案

I was having a 503 in my backend when i had an endpoint query. when you are using google datastore first you have to run it on localhost so it would create the index in a file called datastore-indexes-auto.xml this is automaticaly generated.

this is an index example

<!-- Used 1 time in query history -->
<datastore-index kind="Conference" ancestor="true" source="auto">
    <property name="name" direction="asc"/>
</datastore-index>

这篇关于报告API 503后端错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆