Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CosmosDB x-ms-retry-after-ms header access #113

Open
sergsalo opened this issue Oct 18, 2018 · 2 comments
Open

CosmosDB x-ms-retry-after-ms header access #113

sergsalo opened this issue Oct 18, 2018 · 2 comments

Comments

@sergsalo
Copy link

CosmosDB can reject the request with 429 status code. Here is the sample response:

ExceptionType : RequestRateTooLargeException
ExceptionMessage : Message: {"Errors":["Request rate is large"]}

According to documentation:
"When a client attempts to exceed the reserved throughput for an account, there is no performance degradation at the server and no use of throughput capacity beyond the reserved level. The server will preemptively end the request with RequestRateTooLarge (HTTP status code 429) and return the x-ms-retry-after-ms header indicating the amount of time, in milliseconds, that the user must wait before reattempting the request."

Is there a way to access header "x-ms-retry-after-ms" in gremlin execute response to handle the retry properly ?

so, basically I'm running
graph.execute("g.E().count()", {}, (err, results) =>{...})

  • how to get that header from here?

Thanks,

@AbdolrezaMadi
Copy link

I'm looking for the same thing. Is there any update on this issue?

@NoamWe
Copy link

NoamWe commented Oct 6, 2020

Would be happy to hear an update regarding this issue too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants