简体   繁体   English

使用Cosmos DB的gremlin.net:RequestRateTooLarge

[英]gremlin.net with Cosmos DB: RequestRateTooLarge

I get RequestRateTooLarge exception when doing queries that involve around 60 vertices. 当执行涉及约60个顶点的查询时,出现RequestRateTooLarge异常。 The problem seems to be related to the number of vertices and edges involved in the query (it does not happen with "smaller" queries). 该问题似乎与查询中涉及的顶点和边的数量有关(“较小”的查询不会发生此问题)。 Increasing the throughput does not solve the problem, it just happens less frequently. 增加吞吐量并不能解决问题,只是发生频率较低。

Would it be useful to wait some time between retrievals of the results of the query? 在检索查询结果之间等待一段时间会有用吗? Ie doing a Thread.Sleep() between calls to something like query.ExecuteNextAsync() of Graph API. 即在调用Graph API的诸如query.ExecuteNextAsync()之类的操作之间执行Thread.Sleep()。 I could not find an equivalent in gremlin.net so I haven't tried yet. 我在gremlin.net中找不到等效项,所以我还没有尝试过。

If this is not a solution, what can I do? 如果这不是解决方案,我该怎么办?

Introducing a wait period will address the RequestRateTooLarge exception you are experiencing. 引入等待时间将解决您遇到的RequestRateTooLarge异常。

Another option is to increase the reserved throughput for the container. 另一个选择是增加容器的保留吞吐量。 You can find additional information about exceeding the reserved throughput exception here . 您可以在此处找到有关超出保留的吞吐量例外的其他信息。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM