NVIDIA / NVIDIA/GenerativeAIExamples
Chain server fail to pull the result
Personne n'a encore pris cette issue.
- Langage dominant
- Jupyter Notebook
- Étoiles
- 4.2k
- Forks
- 1.1k
- Merge moyen
- 10 h 15 min
- PR mergées (30 j)
- 1
Description
2025/01/29 12:35:47.094 +00:00] [WARN] [retry/retry.go:104] ["retry func failed, reach max retry"] [traceID=5ce0d7f04403e4b765eefacedfbf5a5b] [attempt=2]
[2025/01/29 12:35:47.094 +00:00] [WARN] [proxy/task_search.go:581] ["search execute failed"] [traceID=5ce0d7f04403e4b765eefacedfbf5a5b] [nq=1] [error="failed to search/query delegator 2 for channel by-dev-rootcoord-dml_1_454401150931015494v0: fail to search on QueryNode 2: worker(2) query failed: Operator::GetOutput failed for [Operator:, plan node id: 11562] : => failed to search: config={{"ef":10,"k":40,"metric_type":"L2","span_id":"11dd9c06b163fd13","trace_flags":0,"trace_id":"5ce0d7f04403e4b765eefacedfbf5a5b"}} out of range in json: ef(10) should be larger than k(40) at /workspace/source/internal/core/src/index/VectorMemIndex.cpp:411"] [errorVerbose="failed to search/query delegator 2 for channel by-dev-rootcoord-dml_1_454401150931015494v0: fail to search on QueryNode 2: worker(2) query failed: Operator::GetOutput failed for [Operator:, plan node id: 11562] : => failed to search: config={{"ef":10,"k":40,"metric_type":"L2","span_id":"11dd9c06b163fd13","trace_flags":0,"trace_id":"5ce0d7f04403e4b765eefacedfbf5a5b"}} out of range in json: ef(10) should be larger than k(40) at /workspace/source/internal/core/src/index/VectorMemIndex.cpp:411\n(1) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus/internal/proxy.(*LBPolicyImpl).ExecuteWithRetry.func1\n | \t/workspace/source/internal/proxy/lb_policy.go:218\n | [...repeated from below...]\nWraps: (2) failed to search/query delegator 2 for channel by-dev-rootcoord-dml_1_454401150931015494v0\nWraps: (3) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus/internal/proxy.(*searchTask).searchShard\n | \t/workspace/source/internal/proxy/task_search.go:791\n | github.com/milvus-io/milvus/internal/proxy.(*LBPolicyImpl).ExecuteWithRetry.func1\n | \t/workspace/source/internal/proxy/lb_policy.go:210\n | github.com/milvus-io/milvus/pkg/util/retry.Do\n | \t/workspace/source/pkg/util/retry/retry.go:44\n | github.com/milvus-io/milvus/internal/proxy.(*LBPolicyImpl).ExecuteWithRetry\n | \t/workspace/source/internal/proxy/lb_policy.go:179\n | github.com/milvus-io/milvus/internal/proxy.(*LBPolicyImpl).Execute.func1\n | \t/workspace/source/internal/proxy/lb_policy.go:246\n | golang.org/x/sync/errgroup.(*Group).Go.func1\n | \t/go/pkg/mod/golang.org/x/sync@v0.7.0/errgroup/errgroup.go:78\n | runtime.goexit\n | \t/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.0.linux-amd64/src/runtime/asm_amd64.s:1695\nWraps: (4) fail to search on QueryNode 2\nWraps: (5) worker(2) query failed: Operator::GetOutput failed for [Operator:, plan node id: 11562] : => failed to search: config={{"ef":10,"k":40,"metric_type":"L2","span_id":"11dd9c06b163fd13","trace_flags":0,"trace_id":"5ce0d7f04403e4b765eefacedfbf5a5b"}} out of range in json: ef(10) should be larger than k(40) at /workspace/source/internal/core/src/index/VectorMemIndex.cpp:411\nError types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) merr.milvusError"]
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par suivre l’échec signalé depuis internal/proxy/task_search.go:581 à travers internal/proxy/lb_policy.go et pkg/util/retry/retry.go, puis examinez l’erreur de VectorMemIndex.cpp:411 indiquant que ef(10) est inférieur à k(40). Reproduisez la recherche dans le workflow chain-server et déterminez le résultat attendu ; c’est terminé lorsque la requête renvoie son résultat sans l’échec de retry signalé.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- go
- Domaine
- backend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100