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

Return 429 on ES API when no shards available #5566

Merged
merged 1 commit into from
Nov 28, 2024
Merged

Conversation

rdettai
Copy link
Contributor

@rdettai rdettai commented Nov 27, 2024

Description

Closes #5565

How was this PR tested?

N/A

@rdettai rdettai self-assigned this Nov 27, 2024
@rdettai rdettai requested a review from fulmicoton November 27, 2024 08:20
@rdettai
Copy link
Contributor Author

rdettai commented Nov 28, 2024

429 is required for the JS client to retry, but note that in the Ingest (V2) API the response code is 503 Unavailable

IngestFailureReason::NoShardsAvailable => {
IngestServiceError::Unavailable("no shards available".to_string())
}

@rdettai rdettai enabled auto-merge (squash) November 28, 2024 16:31
@rdettai rdettai merged commit 5329379 into main Nov 28, 2024
4 of 5 checks passed
@rdettai rdettai deleted the no-shard-es-429 branch November 28, 2024 16:41
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

Successfully merging this pull request may close these issues.

Bulk API return document level 500 when new shards are being allocated
2 participants