-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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]: NodeNotFound when trying to load collection after milvus update and bulk insert #33200
Closed
1 task done
Labels
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
zhengbuqian
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
May 20, 2024
yanliang567
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
May 21, 2024
yanliang567
added
the
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
label
May 21, 2024
1 task
weiliu1031
added a commit
to weiliu1031/milvus
that referenced
this issue
May 21, 2024
issue: milvus-io#33200 milvus-io#33207 pr#33104 remove this logic by mistake, which cause the offline node will be kept in replica after qc recover, and request send to offline qn will go a NodeNotFound error. Signed-off-by: Wei Liu <wei.liu@zilliz.com>
This was referenced May 21, 2024
please verify this with latest image |
/assign @zhengbuqian |
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
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
Current Behavior
hello_milvus.py
mentioned below does create collection, insert data, create index and load index. It does not drop index or colelction.bulk pytest
refer tocd tests/python_client/testcases && pytest test_bulk_insert.py::TestBulkInsert::test_bulk_insert_all_field_with_parquet
.Before every test, everything in etcd and minio are dropped to ensure fresh start.
Commit order:
5c6de47 (3 days ago) -> c6e2dd05 (19 hours ago) -> a7f6193bfc (10 hours ago) -> now (0520 9 pm)
Test A:
5c6de47
, runhello_milvus.py
bulk pytest
. all tests passedTest B:
5c6de47
, runhello_milvus.py
a7f6193bfc
bulk pytest
. the test fails withNodeNotFound
error when trying to load the collection<MilvusException: (code=65535, message=NodeNotFound)> (api_request.py:46)
Test C:
5c6de47
, runhello_milvus.py
c6e2dd05
bulk pytest
all tests passedTest D:
a7f6193bfc
, runhello_milvus.py
bulk pytest
. all tests passedFrom the above test results, seems commit
a7f6193bfc
has introduced some kind of compatibility issue, causing collections with segments created by bulk insert fail to load.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: