-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Bug]: Encountered a LoadSegment: stoi
error during the query node restart.
#36255
Closed
1 task done
Labels
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Comments
jaime0815
added
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Sep 13, 2024
sre-ci-robot
pushed a commit
that referenced
this issue
Sep 14, 2024
issue: #36255 Signed-off-by: jaime <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Sep 18, 2024
issue: #36255 pr: #36267 Signed-off-by: jaime <[email protected]>
I also encountered the same error, the error message is as follows. [2024/12/03 13:12:06.370 +08:00] [WARN] [task/executor.go:232] ["failed to load segment"] [taskID=1733197089983] [collectionID=453083736594493726] [replicaID=454347199065882627] [segmentID=454254090268447366] [node=161] [source=segment_checker] [shardLeader=161] [error="The specified key does not exist.: key not found[key=milvus-xxx-56789/delta_log/453083736594493726/453083736594493727/454254090268447366/454254090268866948]"]
[2024/12/03 13:12:06.370 +08:00] [ERROR] [funcutil/parallel.go:88] [loadSegmentFunc] [error="At LoadSegment: stoi"] [errorVerbose="At LoadSegment: stoi\n(1) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus/internal/querynodev2/segments.(*segmentLoader).Load.func4\n | \t/workspace/source/internal/querynodev2/segments/segment_loader.go:708\n | github.com/milvus-io/milvus/pkg/util/funcutil.ProcessFuncParallel.func3\n | \t/workspace/source/pkg/util/funcutil/parallel.go:86\n | runtime.goexit\n | \t/usr/local/go/src/runtime/asm_amd64.s:1650\nWraps: (2) At LoadSegment\nWraps: (3) stoi\nError types: (1) *withstack.withStack (2) *errutil.withPrefix (3) merr.milvusError"] [idx=0] [stack="github.com/milvus-io/milvus/pkg/util/funcutil.ProcessFuncParallel.func3\n\t/workspace/source/pkg/util/funcutil/parallel.go:88"]
[2024/12/03 13:12:06.370 +08:00] [ERROR] [funcutil/parallel.go:88] [loadSegmentFunc] [error="At LoadSegment: stoi"] [errorVerbose="At LoadSegment: stoi\n(1) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus/internal/querynodev2/segments.(*segmentLoader).Load.func4\n | \t/workspace/source/internal/querynodev2/segments/segment_loader.go:708\n | github.com/milvus-io/milvus/pkg/util/funcutil.ProcessFuncParallel.func3\n | \t/workspace/source/pkg/util/funcutil/parallel.go:86\n | runtime.goexit\n | \t/usr/local/go/src/runtime/asm_amd64.s:1650\nWraps: (2) At LoadSegment\nWraps: (3) stoi\nError types: (1) *withstack.withStack (2) *errutil.withPrefix (3) merr.milvusError"] [idx=0] [stack="github.com/milvus-io/milvus/pkg/util/funcutil.ProcessFuncParallel.func3\n\t/workspace/source/pkg/util/funcutil/parallel.go:88"]
|
upgrade to 2.4.20 and you should the actual error message is. The problem is the real error is swallowed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Is there an existing issue for this?
Environment
Current Behavior
An error
at LoadSegment: stoi
occurs during the restart of querynode. Due to the lack of a detailed error message, we cannot identify which numeric string failed to convert.Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: