quickwit-oss / quickwit-oss/quickwit
request AWS AssumeRoleWithWebIdentity API
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Describe the bug
A clear and concise description of what the bug is.
Version: v0.8.0
In the last 24 hours, the searcher cluster requested AWS AssumeRoleWithWebIdentity API 34,934,189 times. From what I understand, Quickwit is supposed to store credential temporarily for an hour. However, we've noticed that it's getting bombarded with a huge volume of requests nearly every second. The error log from a quickwit pod.
2024-03-26T08:16:36.417Z ERROR fetch_docs: quickwit_search::fetch_docs: error when fetching docs in splits split_ids=["01HSWWX3VSY1K4C2AAYY6WG898", "01HSWWTHNAMAKHV7ZHH3M9PYZJ"] error=open-index-for-split
Caused by:
0: failed to fetch hotcache and footer from s3://path for split `01HSWWTHNAMAKHV7ZHH3M9PYZJ`
1: storage error(kind=Internal, source=failed to construct request: failed to load credentials from the credentials cache: an error occurred while loading credentials: service error: unhandled error: unhandled error: Error { code: "Throttling", message: "Rate exceeded", aws_request_id: "e08a1aa3-6d6c-487e-a6f2-" } (ConstructionFailure(ConstructionFailure { source: CredentialsStageError { source: ProviderError(ProviderError { source: ServiceError(ServiceError { source: Unhandled(Unhandled { source: ErrorMetadata { code: Some("Throttling"), message: Some("Rate exceeded"), extras: Some({"aws_request_id": "e08a1aa3-6d6c-487e-a6f2-"}) }, meta: ErrorMetadata { code: Some("Throttling"), message: Some("Rate exceeded"), extras: Some({"aws_request_id": "e08a1aa3-6d6c-487e-a6f2-"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {"x-amzn-requestid": "e08a1aa3-6d6c-487e-a6f2-", "content-type": "text/xml", "content-length": "255", "date": "Tue, 26 Mar 2024 08:16:36 GMT", "connection": "close"}, body: SdkBody { inner: Once(Some(b"<ErrorResponse xmlns=\"https://sts.amazonaws.com/doc/2011-06-15/\">\n <Error>\n <Type>Sender</Type>\n <Code>Throttling</Code>\n <Message>Rate exceeded</Message>\n </Error>\n <RequestId>e08a1aa3-6d6c-487e-a6f2-</RequestId>\n</ErrorResponse>\n")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag { contents: ["aws_types::SigningService", "aws_smithy_http::operation::Metadata", "aws_smithy_http::connection::CaptureSmithyConnection", "aws_http::user_agent::AwsUserAgent", "aws_sig_auth::signer::OperationSigningConfig", "aws_sdk_sts::endpoint::Params", "aws_types::region::Region", "aws_smithy_types::endpoint::Endpoint", "aws_credential_types::cache::SharedCredentialsCache", "alloc::vec::Vec<http::version::Version>", "aws_types::region::SigningRegion"] }, poisoned: false, .. }) } }) }) } })))
2: failed to construct request: failed to load credentials from the credentials cache: an error occurred while loading credentials: service error: unhandled error: unhandled error: Error { code: "Throttling", message: "Rate exceeded", aws_request_id: "e08a1aa3-6d6c-487e-a6f2-" } (ConstructionFailure(ConstructionFailure { source: CredentialsStageError { source: ProviderError(ProviderError { source: ServiceError(ServiceError { source: Unhandled(Unhandled { source: ErrorMetadata { code: Some("Throttling"), message: Some("Rate exceeded"), extras: Some({"aws_request_id": "e08a1aa3-6d6c-487e-a6f2-"}) }, meta: ErrorMetadata { code: Some("Throttling"), message: Some("Rate exceeded"), extras: Some({"aws_request_id": "e08a1aa3-6d6c-487e-a6f2-"}) } }), raw: Response { inner: Response { status: 400, version: HTTP/1.1, headers: {"x-amzn-requestid": "e08a1aa3-6d6c-487e-a6f2-", "content-type": "text/xml", "content-length": "255", "date": "Tue, 26 Mar 2024 08:16:36 GMT", "connection": "close"}, body: SdkBody { inner: Once(Some(b"<ErrorResponse xmlns=\"https://sts.amazonaws.com/doc/2011-06-15/\">\n <Error>\n <Type>Sender</Type>\n <Code>Throttling</Code>\n <Message>Rate exceeded</Message>\n </Error>\n <RequestId>e08a1aa3-6d6c-487e-a6f2-</RequestId>\n</ErrorResponse>\n")), retryable: true } }, properties: SharedPropertyBag(Mutex { data: PropertyBag { contents: ["aws_types::SigningService", "aws_smithy_http::operation::Metadata", "aws_smithy_http::connection::CaptureSmithyConnection", "aws_http::user_agent::AwsUserAgent", "aws_sig_auth::signer::OperationSigningConfig", "aws_sdk_sts::endpoint::Params", "aws_types::region::Region", "aws_smithy_types::endpoint::Endpoint", "aws_credential_types::cache::SharedCredentialsCache", "alloc::vec::Vec<http::version::Version>", "aws_types::region::SigningRegion"] }, poisoned: false, .. }) } }) }) } }))
3: failed to fetch slice 8194735750..8199046294 for object: s3://path/01HSWWTHNAMAKHV7ZHH3M9PYZJ.split
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the credential-cache path associated with the reported AWS AssumeRoleWithWebIdentity calls and the S3 split-fetch failure shown in the error log. Determine why requests are repeated despite the expected one-hour temporary credential lifetime, then verify that the failing workload no longer produces throttling at the reported rate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100