Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: directory confusion between indexnode and querynode for building and loading index #38627

Open
1 task done
zhagnlu opened this issue Dec 20, 2024 · 1 comment
Open
1 task done

[Bug]: directory confusion between indexnode and querynode for building and loading index #38627

zhagnlu opened this issue Dec 20, 2024 · 1 comment
Assignees
@zhagnlu
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@zhagnlu
Copy link
Contributor

zhagnlu commented Dec 20, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: master/2.4
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

when using standalone mode. indexnode and querynode all in one process. but their local chunk managers(different role using different rootpath) all using same root path(next init chunk manager rewrite the last chunk manager). so wrong and mixed.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@zhagnlu zhagnlu 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 Dec 20, 2024
@zhagnlu zhagnlu mentioned this issue Dec 20, 2024
Open
@yanliang567
Copy link
Contributor

/assign @zhagnlu
/unassign

@sre-ci-robot sre-ci-robot assigned zhagnlu and unassigned yanliang567 Dec 24, 2024
@yanliang567 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 Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zhagnlu zhagnlu

Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zhagnlu @yanliang567