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]: [json-inverted] The indexnoe keeps CrashLoopBackOff when createing index for Json data #38823

Open
1 task done
ThreadDao opened this issue Dec 27, 2024 · 2 comments
Open
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@ThreadDao
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: harbor.milvus.io/milvus/milvus:JsDove-optimization_json-72e0417-20241225
- Deployment mode(standalone or cluster): 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

server

cluster with dev-image: harbor.milvus.io/milvus/milvus:JsDove-optimization_json-72e0417-20241225

client

  1. create collection with 3 fields: id(int64 & pk) + vector + json
  2. create HNSW index for vector fields
  3. insert 10million entities -> flush
  4. create index again -> indexNode keeps crashing and restarting
    in_pdsv4.log

image

Expected Behavior

No response

Steps To Reproduce

argo workflow name: zong-json-index-4

Milvus Log

pods:

son-inverted-op-97-1369-milvus-datanode-56b8d4b7bf-g8r2k         1/1     Running                  0               2d7h    10.104.15.251   4am-node20   <none>           <none>
json-inverted-op-97-1369-milvus-indexnode-7dd96c757-pdsv4         0/1     CrashLoopBackOff         50 (75s ago)    2d7h    10.104.15.250   4am-node20   <none>           <none>
json-inverted-op-97-1369-milvus-mixcoord-564c6ffd7c-v8plr         1/1     Running                  0               2d7h    10.104.15.252   4am-node20   <none>           <none>
json-inverted-op-97-1369-milvus-proxy-744995f869-fws7x            1/1     Running                  0               2d7h    10.104.30.218   4am-node38   <none>           <none>
json-inverted-op-97-1369-milvus-querynode-0-f696dfb79-bhml8       1/1     Running                  0               36s     10.104.19.13    4am-node28   <none>           <none>
json-inverted-op-97-1369-milvus-querynode-0-f696dfb79-z89lq       1/1     Running                  0               2d2h    10.104.33.235   4am-node36   <none>           <none>

Anything else?

No response

@ThreadDao ThreadDao 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 27, 2024
@yanliang567
Copy link
Contributor

/assign @JsDove
/unassign

@sre-ci-robot sre-ci-robot assigned JsDove and unassigned yanliang567 Dec 28, 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 28, 2024
@yanliang567 yanliang567 modified the milestones: 2.5.1, 2.5.2 Dec 28, 2024
@ThreadDao
Copy link
Contributor Author

@JsDove upgrade instance's image to new JsDove-optimization_json-1dacbd3-20241230 and the indexNode also crash
in_fmgmq.log
image

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 triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants