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]: Server can not be recovered after docker-compse restart #16117

Closed
1 task done
ATUFO opened this issue Mar 19, 2022 · 7 comments
Closed
1 task done

[Bug]: Server can not be recovered after docker-compse restart #16117

ATUFO opened this issue Mar 19, 2022 · 7 comments
Assignees
@ATUFO
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days

Comments

@ATUFO
Copy link

ATUFO commented Mar 19, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: v2.0.1
- Deployment mode(standalone or cluster): standalone
- SDK version(e.g. pymilvus v2.0.0rc2): Java SDK milvus 2.0.0
- OS(Ubuntu or CentOS): Ubuntu 18.04
- CPU/Memory: Intel Xeon Gold 6133 @ 4x 2.494GHz      4G Memory
- GPU: None
- Others: 腾讯云服务器

Current Behavior

When I create a new service ,I can index and query data. In the tests , I inserted 32 records .It's nothing wrong , but when I restart my server or exec docker-compose restart | docker restart xxxx ( in a word, restart the service), the search didn't work.

see attu dashboard
580512dadc9e5f674bc3ef33aa9c96c

Expected Behavior

Search normally

Steps To Reproduce

1. create a milvus service
2. insert some data ( In my tests,there are only 32 records)
3. restart service ( docker-compose restart |  systemctl restart milvus). I tested docker-compose version and direct install on linux.
4. search . I tested using Attu

Anything else?

No response
@ATUFO ATUFO 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 Mar 19, 2022
@zhuwenxing
Copy link
Contributor

Hi, you can check the status of the Milvus container. Searching may cause querynode panic after the container is restarted, see #15713. But in the latest version, this issue should have been fixed.

@ATUFO
Copy link
Author

ATUFO commented Mar 20, 2022

Hi, you can check the status of the Milvus container. Searching may cause querynode panic after the container is restarted, see #15713. But in the latest version, this issue should have been fixed.

The version I installed is v2.0.1 。 I have seen #15713 .After that , I updated milvus from v2.0.0 to v2.0.1 。But I have the same problem。

there are too few available query nodes to balance means what? No querynods or at least one querynode exists?

[2022/03/20 00:56:45.785 +00:00] [WARN] [query_coord.go:532] ["loadBalanceSegmentLoop: there are too few available query nodes to balance"] [onlineNodeIDs="[27]"] [availableNodeIDs="[27]"]

@xiaofan-luan
Copy link
Contributor

Hi, you can check the status of the Milvus container. Searching may cause querynode panic after the container is restarted, see #15713. But in the latest version, this issue should have been fixed.

The version I installed is v2.0.1 。 I have seen #15713 .After that , I updated milvus from v2.0.0 to v2.0.1 。But I have the same problem。

there are too few available query nodes to balance means what? No querynods or at least one querynode exists?

[2022/03/20 00:56:45.785 +00:00] [WARN] [query_coord.go:532] ["loadBalanceSegmentLoop: there are too few available query nodes to balance"] [onlineNodeIDs="[27]"] [availableNodeIDs="[27]"]

Usually this means:

  1. memory is not enough for the querynode to load data
  2. querynode is not healthy for some reason.

My suggestion is 1) check if you have enough memory to load data 2) if that's not the case, upload your log in querynode/querycoord and we will help you on investigation

@xiaofan-luan xiaofan-luan changed the title [Bug]: [Bug]: Server can be recovered after docker-compse restart Mar 20, 2022
@yanliang567
Copy link
Contributor

@ATUFO you could also try with latest master build.

/assign @ATUFO
/unassign

@sre-ci-robot sre-ci-robot assigned ATUFO and unassigned yanliang567 Mar 21, 2022
@zhuwenxing zhuwenxing changed the title [Bug]: Server can be recovered after docker-compse restart [Bug]: Server can not be recovered after docker-compse restart Mar 22, 2022
@AlviseSembenico
Copy link

Hi, I am having the same problem on K8S after a restart of the service if any collection was already loaded

@xiaofan-luan
Copy link
Contributor

Hi, I am having the same problem on K8S after a restart of the service if any collection was already loaded

Hi Alvise, could you try 2.0.2?

@stale
Copy link

stale bot commented May 4, 2022

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 May 4, 2022
@stale stale bot closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ATUFO ATUFO

Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@zhuwenxing @ATUFO @AlviseSembenico @yanliang567 @xiaofan-luan