Adding retries and a dedicated pool for Weaviate Dags to handle connection latency #59198
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vatsrahul1001
approved these changes
Dec 8, 2025
henry3260
pushed a commit
to henry3260/airflow
that referenced
this pull request
Dec 10, 2025
… issues (apache#59198) Co-authored-by: Atul Singh <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We were facing issues with Weaviate connection and recently updated the connection but now we are getting a couple of dag failures due to the high latency on connection.
To handle this, I have updated the dag to include the retries and also, Weaviate dags to use a specific pool with 1 slot so that connection don't get overloaded.