Repository navigation
Update failure store redirect logic to exclude backpressure exceptions - #148154
Conversation
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
|
Hi @jbaiera, I've created a changelog YAML for you. |
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
dakrone
left a comment
There was a problem hiding this comment.
LGTM, I left two comments
…on.java Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com>
elastic#148154) Updates shard-level failure redirection logic for data stream failure stores to exclude cluster block exception and circuit breaker exceptions from being captured in the failure store.
elastic#148154) Updates shard-level failure redirection logic for data stream failure stores to exclude cluster block exception and circuit breaker exceptions from being captured in the failure store.
Updates shard-level failure redirection logic for data stream failure stores to exclude cluster block exception and circuit breaker exceptions from being captured in the failure store. Additionally, any exception that results in an HTTP 429 response is filtered from the redirection logic. These exceptions are indicative of backpressure, which is an important signal for ingestion clients.