429 Errors when using Tigris as Storage Backend for Quickwit

Hello, we’re trying to build a log storage backend using Quickwit + Tigris for S3. However, as we have been scaling our searcher nodes, we are getting 429 errors since quickwit searchers send lots of concurrent requests to the bucket.

I assume Fly.io itself is using Tigris for it’s own log storage, so wondering how you are not running into this issue

Any advice?

@chmaltsp Could you please write to us(help@tigrisdata.com) with your bucket name we can also take a look at it

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.