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]: waitNewTSafe does not wait #10722

Closed
1 task done
congqixia opened this issue Oct 27, 2021 · 0 comments · Fixed by #10724
Closed
1 task done

[Bug]: waitNewTSafe does not wait #10722

congqixia opened this issue Oct 27, 2021 · 0 comments · Fixed by #10724
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

@congqixia
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 555912f
- Deployment mode(standalone or cluster): both
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

waitNewTSafe does not wait a new tsafe update. So querynode log will contain lots of unsolveMsg related infrmation

Expected Behavior

waitNewTSafe waits for ts update so doUnsolvedQueryMsg only operate only when ts updated

Steps To Reproduce

No response

Anything else?

This is caused by not resetting waiting Condition

@congqixia congqixia added kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Oct 27, 2021
@congqixia congqixia added this to the 2.0.0-RC8 milestone Oct 27, 2021
@congqixia congqixia self-assigned this Oct 27, 2021
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

Successfully merging a pull request may close this issue.

1 participant