Query API returns HTTP 503

[dennis-sig]

Describe the bug
We've been using your API for a while. Since about a week, the API sometimes returns HTTP 503. This seems to be temporary, so it tends to work again if you just query a few times. The end point we're using is https://google.github.io/osv.dev/post-v1-query/.

To Reproduce
You can reproduce the issue by copying the example from https://google.github.io/osv.dev/post-v1-query/#post-v1query verbatim. However, this is tricky to reproduce because it only occurs occasionally.

[another-rex]

Thanks for reporting this! We are currently investigating, we also noticed an uptick in the 503's for about a week or 2.

[MichielCuijpers]

Hi @another-rex is there an update on this issue please?

[another-rex]

We applied a fix which partially resolved this in #3043.

It is still happening occasionally (once a week or so), but as OP said you can just retry in a few minutes and it goes away. Unfortunately we haven't had time to look into this further recently, but we will keep investigating to find the root cause.

[github-actions]

This issue has not had any activity for 60 days and will be automatically closed in two weeks

See https://github.com/google/osv.dev/blob/master/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out.

[github-actions]

This issue has not had any activity for 60 days and will be automatically closed in two weeks

See https://github.com/google/osv.dev/blob/master/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out.

[another-rex]

Related #3528

[github-actions]

This issue has not had any activity for 60 days and will be automatically closed in two weeks

See https://github.com/google/osv.dev/blob/master/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out.

[another-rex]

The issue is with receiving a large spike in queries in a short timespan, which point we could not scale up new instances fast enough to handle the query volume, causing us to drop some queries with 503. We are working on overhauling our database layout to improve performance.