Fix DEADLINE_EXCEEDED gRPC timeout on Zilliz Serverless#291
Open
alfredsgenkins wants to merge 1 commit intozilliztech:masterfrom
Open
Fix DEADLINE_EXCEEDED gRPC timeout on Zilliz Serverless#291alfredsgenkins wants to merge 1 commit intozilliztech:masterfrom
alfredsgenkins wants to merge 1 commit intozilliztech:masterfrom
Conversation
The default MilvusClient gRPC timeout (15s) is too short for Zilliz Serverless clusters, causing DEADLINE_EXCEEDED errors during indexing. Two changes: 1. Set MilvusClient timeout to 60s (configurable via MILVUS_TIMEOUT_MS) 2. Replace expensive dummy collection create/drop in checkCollectionLimit with a lightweight listCollections call Fixes zilliztech#289 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
alfredsgenkins
force-pushed
the
fix/grpc-timeout-deadline-exceeded
branch
from
c739ed2 to
3c28d1f
Compare
|
This fixes the issue for me. Can this be merged? |
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
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.
Problem
When using Zilliz Serverless clusters, indexing fails with:
or during
checkCollectionLimit():The default gRPC timeout of 15s is too short for Zilliz Serverless cold starts, and the dummy collection create/drop used for limit-checking is an expensive operation that reliably exceeds the deadline.
Fixes #289
Changes
1. Configurable gRPC timeout (
MILVUS_TIMEOUT_MS)Sets
MilvusClienttimeout to 60s by default. Configurable viaMILVUS_TIMEOUT_MSenv var.2. Lightweight
checkCollectionLimit()Replaces the dummy collection create → drop approach with a simple
listCollections()call. This is faster, cheaper, and avoids triggering the timeout on serverless clusters. The collection limit is configurable viaMILVUS_MAX_COLLECTIONS(default: 4).Test
Verified against a Zilliz Serverless cluster (
aws-eu-central-1) — indexing now completes successfully without timeout errors.🤖 Generated with Claude Code