zilliztech / zilliztech/VectorDBBench
VectorDBBench hung there and no output log
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 438
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 1
Description
I saw an issue that was very similar to my problem:
However, no solution to this problem was mentioned.
During the stress test, there was a long interval between the log message "Start search 30s in concurrency xxx..." and the next one "Syncing all process and start concurrency search, xxx...". Moreover, after "concurrency 95", the log message "Syncing all process and start concurrency search, xxx..." was not output. After reviewing the code, would it be better to add a mechanism to exit after a certain waiting period to avoid getting stuck in a long wait?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the stress-test code around the log messages "Start search 30s in concurrency xxx..." and "Syncing all process and start concurrency search, xxx...". Reproduce the hang near concurrency 95 and identify where the wait occurs. Done means the stress test no longer waits indefinitely and reports the timeout or failure clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100