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.

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]: no idle index node found and failed to build index #35032

Closed
1 task done
kkpssr opened this issue Jul 26, 2024 · 6 comments
Closed
1 task done

[Bug]: no idle index node found and failed to build index #35032

kkpssr opened this issue Jul 26, 2024 · 6 comments
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@kkpssr
Copy link

kkpssr commented Jul 26, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

Uploading 1760F3C5-AF1C-4fe8-8E09-F0C2E3456883.png…

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@kkpssr kkpssr 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 Jul 26, 2024
@kkpssr
Copy link
Author

kkpssr commented Jul 26, 2024

1760F3C5-AF1C-4fe8-8E09-F0C2E3456883

@xiaofan-luan
Copy link
Collaborator

@kkpssr
it seems that you have no alive index node and there are 700+ pending task.

  1. check your config, you should have at least 1 replica of index node (since you have many data to build index on, you should have more data)
  2. check your indexnode, if it's a panic, we need to check the log and understand why.

@kkpssr
Copy link
Author

kkpssr commented Jul 27, 2024

@kkpssr it seems that you have no alive index node and there are 700+ pending task.

  1. check your config, you should have at least 1 replica of index node (since you have many data to build index on, you should have more data)
  2. check your indexnode, if it's a panic, we need to check the log and understand why.

so how to add more indexnode in config? Is the buildParallel option in scheduler?
27b24ab50b3070bb62eb634c22ca190d
and how to check index node log?

@xiaofan-luan
Copy link
Collaborator

it based on what is your deployment.

Is there any indexnodes log alive? cna you share the index log?

@yanliang567
Copy link
Contributor

/assign @kkpssr
/unassign

@sre-ci-robot sre-ci-robot assigned kkpssr and unassigned yanliang567 Aug 5, 2024
@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 5, 2024
Copy link

stale bot commented Sep 7, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Sep 7, 2024
@stale stale bot closed this as completed Sep 15, 2024
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 stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants