How to solve segment not found error? #42004
Unanswered
hjlee9182
asked this question in
Q&A and General discussion
Replies: 1 comment
-
Usually "segment not found" bug is difficult to investigate. Sometimes it can be solved by upgrading milvus to the latest version. It is better to raise an issue in "issues" and attach the full log so that we can assign it to the proper engineer. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My milvus usage pattern is to use collection with alias.
Create a collection called A, map the value test_alias, and then the server sends query and search requests to test_alias.
At this time, a segment not found error occurs for a moment after creating a collection called B and alter_alias from A to B.
We are loading collection and then upserting the data and then doing alternative alias.
But not loaded segment is related with collection called A.
How should I solve this?
Our milvus version is 2.5.4-gpu.
fail to Query on QueryNode 1188: worker(1189) query failed: segment not found: segment not loaded
Beta Was this translation helpful? Give feedback.
All reactions