You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
version: V0.8.1
As the doc from AWS said: your application can achieve at least 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second per partitioned Amazon S3 prefix.
After this error occurred, the Quickwit cluster became very unstable. Kafka consumption kept rebalancing continuously and impossible to perform the merge operation.
How to fix? According to AWS's recommendation, S3 prefixes need to be subdivided to improve performance.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
version: V0.8.1
As the doc from AWS said: your application can achieve at least 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second per partitioned Amazon S3 prefix.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance.html
error log from qw indexer
After this error occurred, the Quickwit cluster became very unstable. Kafka consumption kept rebalancing continuously and impossible to perform the merge operation.
How to fix? According to AWS's recommendation, S3 prefixes need to be subdivided to improve performance.
The text was updated successfully, but these errors were encountered: