-
Notifications
You must be signed in to change notification settings - Fork 3k
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]: [benchmark][standalone] build index raise error: Connection reset by peer #14733
Comments
it looks like the standalone pod is OOM, but don't know why, as it used to be working with 128GB memory. /unassign |
/assign |
minio crashed. |
/unassign |
argo task: benchmark-tag-jd2gd test yaml: server:
client pod: benchmark-tag-jd2gd-2832215959 clieng log:
|
/assign |
QueryNode offline.
|
@xiaocai2333 why is querynode offline affect getIndexState? |
@xiaofan-luan The latest bug pasted by @wangting0128 is because of the search timeout, not the GetIndexState timeout. |
The real reason of timeout is same as #14077 , |
And there is another problem here. The address of the pod does not change after restart, QueryCoord can get the session of previous RootCoord to access the new RootCoord, even if the new RootCoord is not registerd successfully. |
@xiaocai2333 is there any fix need to be done for this issue? |
Maybe this issue can be closed. @wangting0128 |
not reproduced |
Is there an existing issue for this?
Environment
Current Behavior
client pod: benchmark-no-clean-qn4c7-2274554322
client log:
Expected Behavior
argo task: benchmark-no-clean-qn4c7
test yaml:
client-configmap:client-random-locust-100m-ddl-r8-w2
server-configmap:server-single-32c128m
server:
Steps To Reproduce
Anything else?
client-random-locust-100m-ddl-r8-w2:
The text was updated successfully, but these errors were encountered: